Delay mounting network drive at boot?

Anonymous
2010-04-17T12:13:51+00:00

I have a network drive that I have mapped as a drive on my toshiba nb205 notebook.  It works fine with one exception, boot-up time. 

When the notebook is booted it can never connect to the mapped drive, if I manually open the drive it will then connect and be fine.

My theory is that windows is trying to connect to the drive before the network connection is established. 

Is there a way to delay mounting the network attached drive until the network establishment is complete?

Windows for home | Previous Windows versions | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2010-04-17T13:17:11+00:00

Try this:

  1. Click Start, then type the three letters cmd into the Search box and press Enter.
  2. Type these commands and press Enter after each:

    net use /persistent:no

    net use * /del /yes

    notepad "%UserProfile%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\netlogon.bat

  1. Type the following lines:

    @echo off

    set delay=60

    ping localhost -n %delay%

    net use E: "\SomePC\SomeShare"

  1. Save and close the file

From now on your network connection(s) will be made 60 seconds (or whatever delay you set) after you log on. You must, of course, replace "SomePC" and "SomeShare" with actual names. You also need to be careful with your typing. The commands I used will not tolerate many variations.

Was this answer helpful?

70+ people found this answer helpful.
0 comments

45 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-10-24T16:55:43+00:00

    Thank you so much for this!!!

    This one little fix has fixed several issues in our shop floor environment.  The entire shop had been running on dumb terminals, entirely dependent on COBOL programming to process production.  For the last year we have been in the process of implementing a new ERP system and part of the process was upgrading all hardware, wiring, and converting to a Domain with Win7 clients and 2K8R2 servers.  During the transition, I have had to learn how the old COBOL was used as, and make the programs work on the computers on the shop floor computers which were now the Win7 machines... all of these programs relied on a mapped drive from a non domain server.  Simply using UNC paths would not work, as many of these programs called a very specific drive letter.  I've had to write vb scripts that call the batch files on the network, configure the systems to open the programs full screen automatically on boot, and make this as automated as possible.  Every once in a while, the mapped drive doesn't connect quick enough which breaks this, and requires a reboot, along with an after, or before hours call. We've dealt with it until now... but we one that just won't ever connect quick enough, ever.  So I revisited the issue, found this fix, and it solved more than just this.  Now I'm off to figure out how to put this out in a GPO!

    Thanks again! 

    *Bookmarked*

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2013-03-03T08:30:35+00:00

    This solution worked for me on 4 computers:

    Type gpedit.msc  on the search box in the menu bar,

    1.       Select “Windows Settings”, then

    2.       Select  “Security Settings”, then

    3.       Select “Local Policies”, then

    4.       Then highlight “Security Options”, from there look on the right pane

    5.        Then select “Network security: “LAN Manager authentication level and set the drop down menu to “Send LM & NTLM –use NTLMv2 session security if negotiated”.

    Enjoy!

    Life is much easier on Windows with education and experience.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-11-22T14:11:04+00:00

    That is one nasty hack of a solution to what shouldn't be an issue in the first place. Fancy an OS trying to connect network shares before it has established a network connection!

    Windows is just one nasty hack after another these days....

    Was this answer helpful?

    0 comments