Q
Manage Learn to apply best practices and optimize your operations.

Users not recognized on iSeries when logged in from Windows 2000

The iSeries Navigator properties control how Windows logs into the Windows server. If the user in Windows is not known to the iSeries (i.e does not exist ) you get an error. Change the properties in iSeries Navigator to use another form of user signon can fix the problem and make Windows recognize the user.

We have recently upgraded our iSeries from V5R3 to V5R4. Since this has happened, a problem has developed with iSeries access. Every time a user logs into a PC (Win2K), an error message is displayed:

"Message from [servername] to [windows username] on 07/05/2008 at 9:11:17. CPIB68A: No user profile found for user [windows username]"

My first thought was that the client needed configuring either via the iSeries Navigator or alternatively through the terminal emulator; setting my default id to be my IBM user id rather than my windows id.

This had no effect, so I don't really know where to go from here.

Your Windows will try to connect using Windows server with what the iSeries Navigator properties is set to Use Windows user name, no prompting so that the connection tries to connect using Windows user and password.

If the user in Windows is not known to the iSeries (i.e does not exist ) you get an error. You can change the properties in iSeries Navigator to use another form of user signon (e.g., Default AS/400 user with prompting as needed).

This was last published in July 2008

Dig Deeper on Remote Access to iSeries

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataCenter

Close