tts-winchester
asked on
XP Pro client becomes disconnected from server
I am troubleshooting an XP PRo client connected to W2K Server. If the user leaves the computer on overnight (or doesn't use the machine for many hours during the day) when they try to print or access network data on a network share, it requires them to log in. IE still works so I know the link to the network is OK. They are able to ping the router and the server successfully. When they log off and back on, everything is the way it should be. I have tried the registry setting for autodisconnect related to mapped network drives, but that did not help (although the symptoms listed in the knowledge base specifically listed mapped drives and not printers or file shares).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I use the registry setting. I've found out in the past that for some unknown reason, net config server /autodiscoonect:-1 does not work all the time, in fact, in the article I read, they said that change the registry is a sure-fire way to change it (lanmanserver/parameters).
- info
- info
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have removed the check mark in "Allow computer to turn this device off to conserver power", but the problem continues. What other troubleshooting steps would be helpful?
Did you look atg the two methods I posted?
Oh yeah... have you tried removing the ws from the domain and add it back in? That sometimes resolve a lot of authenticatino problems (could be a SID issue)
- Info
- Info
I am having this exact same issue. The Windows 98 SE machines and a Windows XP Home machine have no trouble maintaining the connection to the network. The only two Windows XP Pro machines on the network have to be logged off and then back on each morning to re-establish the network connection. The internet is sill there but access to mapped drives is not. The error message says: could not connect, the device name is already in use. I tried the suggestions from slink9 but that didn't work.
It appears that the poster didn't look at the two articles I posted. He responded that something else had been tried. I mentioned it again, and no response since.
or perhaps the user account has been set up that way in the domain...