• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 507
  • Last Modified:

I have mapped Drive that disappears the next day - why?

I have a sbs 2003 server  and a ext HD that has it's own IP address. It seems that once I map the ext drive it will give me access and seem to be just fine and then the nexr day I look at the drive and it shows disconnected, and I have no access to it and I can't or don't know how to reconnect it. If I then delete the drive and remap it it works fine again. Any suggestions
3 Solutions
have you tried using the following:

net use \\ip\sharename <drive letter>: /persistent:yes

jploesslAuthor Commented:
no I just used the map network drive from the tools menu. Thanks I will try this  
You could create a batch file and run from the startup folder with the following if the above doesn't work....

net use <drive letter>: /delete
net use <drive letter>: \\ip\sharename

You could also add this to the netlogon at \\YOURSERVERNAME\NETLOGON\SBS_LOGIN_SCRIPT.bat and that will map the drive for all users if you want to.

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

this behavior is the same as SAMBA networking on the MAC -- you can connect to any resource on another system, and it stays for as long as the MAC is running, but when you shut down, the share goes.

In your case, USB devices are only "present" when the system is on.  When the system shuts down it MUST disconnect or unmount any drives on USB channels.  This is to protect the data, it is no different than the warning, Eject your flash card before you remove it, in case you corrupt the files on it.  USB drives are by design supposed to be disconnected before they are removed, and that is what you are seeing.

Perhaps your USB drivers are not up to par?  Perhaps it is SBS that is causing the problem and you need an endless "hot fix" from Microsoft.  If you can make a share in windows explorer one day and see it the next, you know that the USB drivers are working right with the system.  It is then SBS that is the problem
jploesslAuthor Commented:
will be trying to use this this weekend
jploesslAuthor Commented:
thanks for your help

Featured Post

Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now