× 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.



> Vance:
>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?

It's possible for a user to disable Netserver login without disabling 5250
login.  You should see message CPIB682 in QSYSOPR and QHST:

User profile xxxxxxx disabled for AS/400 Support for Windows Network
  Neighborhood access.

When you try to connect to an IFS drive the PC will automatically try to
authenticate using the network i.d. and password you used when you booted or
logged in the PC.  If the password is different than the AS/400 password it
will disable the Netserver login.  NT lets you prompt for user name and
password, but Windows 9x requires that your network and AS/400 i.d. and
password match.

If you change the network password to match the AS/400, you can re-enable
the user by performing a CHGUSRPRF USRPRF(xxxxxxx), without specifying any
parameter changes.

-Jim

James P. Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@dollargeneral.com>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.