+ Post New Thread
Results 1 to 11 of 11
Windows Server 2000/2003 Thread, Network drive issue on Server 2003 in Technical; I am having issues with the S: drive on a Windows server 2003. I've logged onto server and the S: ...
  1. #1
    Guest

    Join Date
    Jun 2009
    Posts
    3,754
    Thank Post
    1,458
    Thanked 487 Times in 375 Posts
    Rep Power
    0

    Network drive issue on Server 2003

    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?

  2. #2

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,390
    Thank Post
    797
    Thanked 1,588 Times in 1,391 Posts
    Blog Entries
    10
    Rep Power
    427
    Try disconnecting it a reconnecting in the command prompt

  3. Thanks to FN-GM from:

    Rawns (28th March 2011)

  4. #3
    Guest

    Join Date
    Jun 2009
    Posts
    3,754
    Thank Post
    1,458
    Thanked 487 Times in 375 Posts
    Rep Power
    0
    Quote Originally Posted by FN-GM View Post
    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.
    Last edited by Rawns; 4th March 2010 at 10:30 AM.

  5. #4

    3s-gtech's Avatar
    Join Date
    Mar 2009
    Location
    Wales
    Posts
    2,485
    Thank Post
    133
    Thanked 488 Times in 436 Posts
    Rep Power
    138
    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.

  6. #5

    glennda's Avatar
    Join Date
    Jun 2009
    Location
    Sussex
    Posts
    7,714
    Thank Post
    269
    Thanked 1,116 Times in 1,012 Posts
    Rep Power
    345
    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.

  7. #6

    Join Date
    Mar 2010
    Location
    Leeds
    Posts
    379
    Thank Post
    71
    Thanked 40 Times in 35 Posts
    Rep Power
    16
    Hi can you remember what the GPO was that you removed? Im having this exact problem.

    Cheers

  8. #7

    Join Date
    Dec 2009
    Posts
    592
    Thank Post
    8
    Thanked 36 Times in 34 Posts
    Rep Power
    16
    using local profiles ?

    Seems like a scripting issue as suggested above

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

  9. #8

    3s-gtech's Avatar
    Join Date
    Mar 2009
    Location
    Wales
    Posts
    2,485
    Thank Post
    133
    Thanked 488 Times in 436 Posts
    Rep Power
    138
    Quote Originally Posted by jonnykewell1 View Post
    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.

  10. #9

    Join Date
    Dec 2009
    Posts
    592
    Thank Post
    8
    Thanked 36 Times in 34 Posts
    Rep Power
    16
    Quote Originally Posted by 3s-gtech View Post
    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

  11. #10

    Join Date
    Mar 2010
    Location
    Leeds
    Posts
    379
    Thank Post
    71
    Thanked 40 Times in 35 Posts
    Rep Power
    16
    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.

  12. #11

    3s-gtech's Avatar
    Join Date
    Mar 2009
    Location
    Wales
    Posts
    2,485
    Thank Post
    133
    Thanked 488 Times in 436 Posts
    Rep Power
    138
    Ha, Bingo!

SHARE:
+ Post New Thread

Similar Threads

  1. how do you give more space to 2003 server c Drive
    By ful56_uk in forum Thin Client and Virtual Machines
    Replies: 5
    Last Post: 14th March 2010, 01:56 PM
  2. Server 2008 AD issue across forest trust with Server 2003 R2 AD
    By dhess1013 in forum Windows Server 2008
    Replies: 5
    Last Post: 11th October 2008, 10:00 AM
  3. 2003 DC server C drive
    By Andi in forum Windows
    Replies: 19
    Last Post: 6th February 2008, 10:08 AM
  4. Server 2003 strange disk space issue.
    By starscream in forum Windows
    Replies: 12
    Last Post: 3rd August 2007, 12:07 AM
  5. Exchange 2003 and Server 2003 SP1 issue.
    By tosca925 in forum Windows
    Replies: 0
    Last Post: 21st August 2005, 10:32 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •