RE: IFS Problems with Authentication. -- 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: RE: IFS Problems with Authentication.
From: "Fritz Hayes" <fhayes@xxxxxxxxxxxxx>
Date: 29 Jan 2002 07:51:20 -0800
Importance: Normal
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/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>
Organization: Atwater Associates

Often this is because the Windoze user ID and password is different than
the 400 user ID and password.  Is this the case?


Best Regards

Fritz Hayes
Atwater Associates
<snip>
|
|  Here is something curious that I have seen happening
|on our system (V5r1).  What would cause someone to be
|able to login into the 400 side but not be able to
|authenticate when trying to map for instance QDLS off
|of the IFS side?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: IFS Problems with Authentication. , Vance Stanley

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.