Link to home
Start Free TrialLog in
Avatar of fixitben
fixitben

asked on

Mapped Network Drive Time out Value

Hi,

What I am looking for is the registry value to speed up the time out time of a network drive.  When the network drive doesn't exist because the user is off network I want the time out time it looks for the drive to be less.  Does anybody know where this value is?  

Basically if you go to my computer it hangs for 20 sec looking for the drive that doesn't exist.  I want a way to speed this up.


Thanks
Fixitben
Avatar of USAF_The_One
USAF_The_One
Flag of United States of America image

http://support.microsoft.com/kb/297684

Shows how you can change the default timeout period for network drive access. Let me know if you have any questions. Thanks.
Avatar of fixitben
fixitben

ASKER

No my problem is the oppsite of this I want it to fail quicker.  

Say you disconnect you network cable and then go to my computer.  It stalls for 30sec looking for the mapped drives then fails and shows them not connected.  Well it does this everytime you click my computer.  Which can waste alot of time.  What I want to do is speed up the failure, so you don't have to wait so long.  

The only way to stop this is to disconnect the drive, but that really isn't option.

I hope this makes sense.  

thanks
Fixitben
So let me understand this correctly. You have drives mapped to all your users (not all of which are connected or online) and you want your users to keep these drives mapped and speed up the process it takes to discover these connections without disconnecting the mapped drive?

I can't seem to find anything that exists within the registry that speeds up the timeout setting but I did find something that may disable the error message all together. Take a look at this and see if this is more what you are looking to accomplish.

http://www.pctools.com/guides/registry/detail/927/

ASKER CERTIFIED SOLUTION
Avatar of Dhiraj Mutha
Dhiraj Mutha
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I tried both of those tricks neither changed anything.

Any other ideas.

Thanks
Fixitben
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I tried that and it didn't change anything either.  It still does the same thing.  I know there has to be something out there for this.  I have seen many posts asking the same question, but no one replys.

Thanks
Fixitben
None of these really helped.  But the 'Windows Image Acquisition'  did speed up the time on the end users machine to the 7 secs wait from 30sec.

Thanks
Fixitben
Fixitben. I have the same issue. I found an interesting solution on another EE thread,
I have a BAT file that issues NET USE commands to connect my PC to several hard drives on other PCs on my LAN. When a PC is down, the NET USE command takes around 30 seconds to time out.
On this other thread, the suggestion is made for the BAT file to issue a PING and then skip the NET USE command if the ping times out. You can use the -w switch to set PING's timeout to however many milliseconds you want, and you can use the -n switch to limit the ping to just one attempt.
Here's the link: https://www.experts-exchange.com/questions/23518382/Net-Use-Command-Is-there-anyway-to-have-it-timeout-and-Go-To-the-next-line-in-Batch-file.html
IHTH, dbcole
I wish "helpers" that respond to a question would please READ THE WHOLE REQUEST -- the replies to this question kept going off on a tangent - even AFTER the poster said that it was NOT the right answer !!!!!!!!