Not Authorized To Workstation -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Not Authorized To Workstation
From: Rich Loeber <rich@xxxxxxxxx>
Date: Fri, 16 Jun 2017 16:46:19 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I have my new 41A tower system up and running after flailing around with
the console setup for a while. Before I disconnect the console, I want to
get remote 5250 connectivity established. I can bring up a session from
another system using ACS, but every time I try to sign on, I get a "Not
authorized to workstation" error, even when signing in with QSECOFR. I
checked the device descriptions and they are set to *PUBLIC *CHANGE.

What am I missing?

Rich

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Not Authorized To Workstation , Glenn Gundermann

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.