New Install Weirdness

[Guest.Visitor]

I've got a client who just set up a new pc (windows nt workstation) with Client Access 3.2.0. Here's the weirdness. If he logs on as himself or as admin, he can create a new connection to the AS400. If he logs on as the user, the new connection fails to verify. Can anyone give me some troubleshooting steps to try to isolate the cause of the problem? thanks, Karen Robinson Advanced Information Solutions, Inc karenr@a-i-s.com

[Guest.Visitor]

I forgot to add, the user CAN connect to the AS400 using Client Access on another pc.

[Guest.Visitor]

Karen, I am not an NT wizz, but I would suspect that the problem lies in the user's rights and access under NT - possibly his rights to use TCP/IP. Does he get network connection logged in under his user profile, and if so can he ping the AS/400 from an MS-DOS box (is the as/400 defined in the HOST file belonging to the user?) Any more than that and I am lost and then leave it to the experts. HTH Russell

[Guest.Visitor]

It is definitly because of NT. We circumvent this problem by installing the software under local administrative rights. After the install/reboot, we log on as the prime pc user to create connection and sessions. Another way is to recreate the connection under the new user after you have created them under admin or other user logon. Or you could give that user local admin rights so they have access, but that would defeat using NT to start with.