Mapped Drive Not Connecting at Startup

[spokes]

Strange how this suddenly started for me, I did wonder it it might be related to a recent patch install, but all the reports point to an older, more widespread, problem. However (keeping fingers crossed), I've had no more problems since mapping the IP address. FWIW I have UAC turned off.

 

[tweakradje]

The solution is this:

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

 

[haydster7]

None of these seemed to work for me

None of these seemed to work for me, all resulted in still having to manually click on the drive before it could be seen by any program. My solution was to run the command "net use F: "\\192.168.x.x\sharename" at startup in a batch file (or through task scheduler) but my particular solution ran it in the startup folder of the start menu.

If this still doesnt work for you, try adding the following check into your batch file above the net use command.

ping -n 1 192.168.x.x | find "TTL=" >nul
if errorlevel 1 (
echo offline
) else (
echo online
)

replace the ip address with the computer with the share on it and instead of echoing set the result to a variable and keep looping until that variable is "online" or until a certain number of retries.