Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

When a network drive (net use) is physically disconnected, Windows Explorer (and other programs) keep trying to enumerate and/or use it for maybe 60 seconds.

Is there some way to reduce this timeout to maybe 5 seconds?

Just to clarify, I'm not asking about network drives that are automatically disconnected by Windows after a certain period of time, or about automatic reconnections during login.

The question is about this:

Connect a network drive to another computer. Then turn that other computer off. Then try to reconnect the network drive, e.g. by double-clicking in Windows Explorer -> very long timeout. How to reduce this timeout?

share|improve this question
2  
You might be looking for this: superuser.com/a/332754/124651 –  deppfx Jul 26 '12 at 8:18
    
@Ƭᴇcʜιᴇ007 Thanks for the bounty. But I think people still misunderstand. I tried to rephrase the question again to make it clearer. –  Andreas Haferburg Dec 16 at 13:07
1  
@AndreasHaferburg No problem, if you've got time to test some of the new answers, that'd be handy. :) –  Ƭᴇcʜιᴇ007 Dec 16 at 13:31

5 Answers 5

In Windows 7 and Vista mapped network drives will disconnect themselves after a time and show a red cross on the drive icon. You will still be able to click on the drive and see/use the contents but applications that require a network drive will see them as disconnected and will not see files. If you try to disconnect the drive, it will still sit there saying 'Disconnected Network Drive' - the only solution is to reboot. This is because there is a default disconnect time for inactive network connections. To correct this and turn the autodisconnect off do the following:

  1. Open the command prompt as Administrator. To do this, either:

    • go to Start → All Programs → Accessories, right-click "Command Prompt" and select "Start as Administrator", or

    • type cmd into the search box and press Ctrl+Shift+Enter

  2. In the command prompty, type the following:

    net config server /autodisconnect:-1
    
  3. Press Enter

  4. Reboot computer

Your mapped network drives should now stay connected - this is a permanent fix.

share|improve this answer
1  
This doesn't answer the OPs actual question, original request was misunderstood, see OP's edit. –  Ƭᴇcʜιᴇ007 Dec 10 at 13:45

I was having the same problem, but initially it was only around 30 seconds. But when it jumped to around 2 minutes (for some unknown reason), it got so annoying, I had to find a way to solve it.

I have created batch script which tests the network by seeing if it can ping the target machine, if it can, it maps the drives (if unmapped), otherwise, it deletes the mapping.

@echo off

set ipaddr=192.168.5.3

set current=neither

:begin

    set state=down

    for /f %%i in ('ping -n 1 %ipaddr% -w 1000 ^| findstr /C:"Received = 1"') do (
        set state=up
    )

    if not %state% == %current% (
        set current=%state%
        if %state% == up (
            net use R: \\%ipaddr%\archive$
        )
        if %state% == down (
            net use R: /delete /y
        )
    )

    sleep 5

goto begin

That script is then called by a scheduled task, which runs the script every 10 minutes, with a maximum task time of 10 minutes. Although the console window then remains open during this time, I am currently investigating the Network Conditions for this in the scheduler settings, which could be set to create the shares when connected to the network I know the share is on (which would set a flag), and a second script, which would run once ever 5 minutes or so, which if the flag was older than at least however long, it would delete the shares, minimizing console window time.

share|improve this answer
3  
Unfortunately I think this kind of solution is about as good as we can expect (still, as of 2014), as least when it comes to logins/Explorer start-up delays caused by the network drives. Have my bounty. Perhaps we can revisit it again in a couple more years. :) –  Ƭᴇcʜιᴇ007 Dec 17 at 16:34

Based on http://blogs.msdn.com/b/openspecification/archive/2013/03/27/smb-2-x-and-smb-3-0-timeouts-in-windows.aspx, look like the Windows share timeout is control by "Request Expiration Timer" registry entry.

\HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\
Value type: Dword  
Value name: SessTimeout
Default:    60 seconds (Windows Vista)

It also mentioned this value reduced to 20s in Windows 8 SMB 3.0 for quick failover.

share|improve this answer
1  
Unfortunately, my testing shows that this setting has no effect on the timeout involved in waiting for unavailable network drives. I set it to 5 seconds and I'm still waiting the same ~30 seconds (Windows 7) I was before I set it (and rebooted). –  Ƭᴇcʜιᴇ007 Dec 17 at 16:16

Your solution is below;

Kill the long "restoring network connections" at logon (defer=ghosted connections)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider]

"RestoreConnection"=dword:00000001 ;(0=no attempt, you must click it)

"RestoreTimeout"=dword:00000005

Ghost the connection if not responding within RestoreTimeout

"DeferConnection"=dword:00000001
share|improve this answer
1  
Any source for where you got this information from, or one that hints at why it might help? –  Ƭᴇcʜιᴇ007 Dec 17 at 16:23
2  
Unfortunately, my testing shows that this setting has no effect on the timeout involved in waiting for unavailable network drives. I created the above keys and set their values, but I'm still waiting the same ~30 seconds (Windows 7) I was before I set it (and rebooted). –  Ƭᴇcʜιᴇ007 Dec 17 at 16:31
    
There is also:[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Par‌​ameters] "ReconnectTimeout"=dword:00000005 found here: sevenforums.com/network-sharing/… Setting this entry plus the ones above all to 1 seems to make a huge difference (after reboot). Now everything is fast as expected again. –  kermit Dec 17 at 17:23

According to this post on Windows7Hacker, fixing this issue on the client side involves a registry edit.

  1. Open the Registry with Regedit.exe
  2. Naviagate to HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
  3. Create a DWORD value named KeepConn and set it to time in seconds to keep the connection alive

For example, I set it to 86400 (one day).

share|improve this answer
    
Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference. –  Ivo Flipse Jul 26 '12 at 9:00
    
Also, as a general reminder: Try to make your answers longer than a sentence and add some context please. Explain how the link actually answers the question – it might not be that obvious. –  slhck Jul 26 '12 at 9:03
    
@IvoFlipse: Sure. Thanks for the suggesstion. –  deppfx Jul 26 '12 at 12:48
    
@slhck: Will keep that in mind. –  deppfx Jul 26 '12 at 12:48
1  
This doesn't answer the OPs actual question, original request was misunderstood, see OP's edit. –  Ƭᴇcʜιᴇ007 Dec 10 at 13:45

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.