Timeout mapping network drives at windows login

[Rinux55]

Hi there,

This is my situation: I have a virtual machine running, and a network drive which is mapped to that machine.

The problem here is that when I am trying to login on windows, windows is first trying to connect to that mapped network drive - which it cannot because my virtual machine has to start up first. This results in a rather long login-time.

So my question is, is there some (registry) setting which allows me set this connection timeout to 0? Or that it won't automatically reconnect the drive at login?
Of course the setting 'Do not automatically reconnect at login' is too obvious and does not work, because it also removes the whole mapped network drive at system restart - in my situation the drive should be there, just not connected.

Thanks in advance!

 

[braddersz]

Why don't you remove the mapped drive. And just create a logon script to run at start up, to re map the drove each time windows boots. That means windows will boot up first . Then it will run the batch file automatically to map the drive.

 

[Rinux55]

Haven't thought of that, I suppose that could work. I'm going to try it out!

 

[braddersz]

Good luck. Keep me updated

 

[tweakradje]

This might be your solution:

;### 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

;### network drive map timeout in Explorer if connection is lost (def is 60 sec)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters]
"ReconnectTimeout"=dword:00000005

Edit: you may also need to check the NameSpaces of MyComputer:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace

Cheers