Server Access Problems

[irbk]

Background: Server is running w2k with all the latest patches with AD in Native mode. 3 different Client's are having the same issue. 1 is running XP Pro with SP1. The other 2 are running XP Pro with SP2.

Problem: The client logs onto the XP Pro system. Everything seems to log on correctly however, when the client goes to access a networked drive, they recive the following

Windows
An error occured while reconnecting <Drive Letter> to \\<server>\<share>
Microsoft Windows Network: The local device name is already in use.
This connection has not been restored.

To fix the problem, we dissconnect the network drive and then reconnect it. Once we do this they work fine the rest of the day but come the next day, the same issue happens all over again. I'm running into dead ends for ideas to try. I thought I had a hot fix from Microsoft but that was only for XP SP1 (and it didn't fix the issue on the one system running SP1). I've tried changing the authentacation from Kerb to NTLM as well as several other items but with no luck.
Thanks in advance.

 

[Smorgan11]

what is the drive mapping. Win XP uses H as a mapping for its home drive i think

 

[GlenJohnson]

Have you checked the event logs on any of the machines, including the server? This is always the first place I start.

Glen A. Johnson
"I find television very educating. Every time somebody turns on the set, I go into the other room and read a book."
Groucho Marx
Tek-Tips in Chicago IL

 

[spike0724]

Is there a logon script? if not I would create one that removes the mapping and then re-creates it.

net use U: /del
net use P: /del
net use U: \\MY_SERVER\users
net use P: \\MY_other_server\public


So as you can see we get around the problem


S. Mike Harris

"If there we 90 seconds in a minute, I might get everything done in a day" - S. M. Harris

 

[irbk]

There is nothing intresting in any of the logs on either side. There is no logon script. It does not matter what drive letter you map too. Not looking for a "work around" I want to fix it so creating a logon script is not the answer I'm looking for at this moment.