jellybeenz
Technical User
I posted the following in the IBM Servers forum, but perhaps this is a more appropriate place for it. Hopefully all the XP gurus can give me some insight into this problem.
Our net admin is upgrading our NT workstations to WinXP Pro. These machines are currently unable to access the IFS, although they were able to previously. The admin denies changing any settings on the network and I have no way of independently verifying that. I've checked our netserver config on the AS400 and it looks okay. The domain name, WINS servers, etc are all accurate. I can see the AS400 on the network, but when I get the logon prompt it doesn't seem to recognize the user name. I enter just the name and password but when the logon prompt redisplays, it automatically includes the domain name (I seem to think that it did not do that before...). I thought that it may be passing the "domain/user" as the username and the AS/400 was not recognizing it. However, when I try too many times, the profile becomes disabled for netserver access so it must(?) be recognizing the profile. We are running Client Access Express V5.0, although I thought we had been upgraded to 5.1. Is this a case of requiring an upgrade for CAX?
Upon further thought, I wouldn't think that the version of Client Access would have anything to do with it since the purpose of the netserver is to allow Windows machines to access the IFS without needing special software.
I'm at a loss. Anyone here have any ideas? Thanks.
Our net admin is upgrading our NT workstations to WinXP Pro. These machines are currently unable to access the IFS, although they were able to previously. The admin denies changing any settings on the network and I have no way of independently verifying that. I've checked our netserver config on the AS400 and it looks okay. The domain name, WINS servers, etc are all accurate. I can see the AS400 on the network, but when I get the logon prompt it doesn't seem to recognize the user name. I enter just the name and password but when the logon prompt redisplays, it automatically includes the domain name (I seem to think that it did not do that before...). I thought that it may be passing the "domain/user" as the username and the AS/400 was not recognizing it. However, when I try too many times, the profile becomes disabled for netserver access so it must(?) be recognizing the profile. We are running Client Access Express V5.0, although I thought we had been upgraded to 5.1. Is this a case of requiring an upgrade for CAX?
Upon further thought, I wouldn't think that the version of Client Access would have anything to do with it since the purpose of the netserver is to allow Windows machines to access the IFS without needing special software.
I'm at a loss. Anyone here have any ideas? Thanks.