Network drive issue on Server 2003

[Rawns]

I am having issues with the S: drive on a Windows server 2003.

 

I've logged onto server and the S: drive is listed in My Computer as a "disconnected network drive". Double click it and the S: drive can be accessed just fine but it is still listed in My Computer as disconnected.

 

I cannot manually disconnect the drive (Tools | Disconnect Network Drive...) as the S drive is not listed and if I try using the net use command, I get an error saying "The network connection could not be found".

 

I have tried to manually map the S drive but S: is not included in the list. Using net use, I get an error 85 saying the local device name is already in use.

 

I can't reboot the server due to key systems running on it so am a bit stumped what to try next. Any ideas?

[FN-GM]

Try disconnecting it a reconnecting in the command prompt

[Rawns]

Try disconnecting it a reconnecting in the command prompt

 

 

I tried that using net use but I get the same problem...

 

net use s: /del /yes gives me The network connection could not be found.

 

net use s: \\%computername%\simsarea gives me System error 85 has occurred. The local device name is already in use.

Edited March 4, 2010 by Rawns

[3s-gtech]

I had this once with a broken S: drive for SIMS. It turned out to be a faulty script GPO that was applied, I removed it and rebooted and the PC then mapped the drive fine manually.

[glennda]

I see this alot with pc's and the sims drive specifically i think windows drops its connection on that drive instead of constantly talking to it as sims doesn't actually read/write much to the drive once its started apart from the initial connection when it checks updates sims.ini file.

[jonnykewell1]

Hi can you remember what the GPO was that you removed? Im having this exact problem.

 

Cheers

[2097]

using local profiles ?

 

Seems like a scripting issue as suggested above

 

I use one script at logon to remove and readd the drives

[3s-gtech]

Hi can you remember what the GPO was that you removed? Im having this exact problem.

 

Cheers

 

It was an old version of our login scripts - mapped drives were done using a login.bat file with net use S: \\server\sims. I moved to Group Policy Preferences drive mappings, but this script remained under an existing GPO. Took a bit of hunting to find.

[2097]

It was an old version of our login scripts - mapped drives were done using a login.bat file with net use S: \\server\sims. I moved to Group Policy Preferences drive mappings, but this script remained under an existing GPO. Took a bit of hunting to find.

 

A lot of external companys also use this method when mapping drives

Instead of using a VBS under a OU they tend to Put a logon.bat on the individual account

[jonnykewell1]

Just fixed our problem. Someone had created a policy along side Deafult Domain for SIMS. Within this policy was a .bat for startup which had a line mapping drive F for SIMS. This was clashing with our mapped drive script.

[3s-gtech]

Ha, Bingo!