Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Currently, there is a 40 second delay when accessing an unavailable UNC network share on Windows 7.

Is there a method to reduce this delay to something less painful, like 20 seconds?

share|improve this question

3 Answers 3

I believe the underlying protocol for UNC shares is Server Message Block (SMB) (SMB2 in Win Vista and later). Take a look at the SESSTIMEOUT registry setting. It sounds related and defaults to 45 seconds,

Microsoft Support - SESSTIMEOUT Information

I'm having trouble reproducing this issue to test modifying this value. Can you add additional information about how to reproduce this problem? How do you make a UNC share unavailable? Remove the system from the network? I've tried an unknown host and an unknown share name, but both requests fail fairly quickly in Windows Explorer.

share|improve this answer
1  
a) In my case "unavailable simply means" target computer of UNC path switched off b) timeout of 45s +/- could be (fits round about) c) SESSTIMEOUT is not in the registry and d) does not show any effect in my particular case when added –  Horst Walter Sep 11 '12 at 22:06

Is this any good ? A shot in the dark but nonetheless: MS Support

share|improve this answer
    
Not quite. This page covers the "disconnection timeout" which is the time (usually 10 minutes) that it takes before unused network shares are disconnected. I'm looking for the timeout period that blocks explorer from responding when its trying to connect to a network share that does not exist. –  Contango Apr 1 '11 at 8:54
up vote -2 down vote accepted

There are two ways to fix the problem with an unavailable UNC network share:

  • Eliminate the source of the unavailable UNC network share.
  • Improve the timeout on Windows so that the missing network share does not negatively effect performance.

The first method (eliminate the source of the unavailable UNC network share) is always going to be the most efficient, as it guarantees an extremely quick response time.

Thus, to fix this problem, I identified the source of the 30-second timeouts that were freezing my system: my NAS (Network Attached Storage) device.

Never buy a cheap Netgear Stora NAS. For about two months, your computer will freeze randomly for 30 seconds. This will inevitably result in you telling the problem to your mates, followed by uncontrollable sobbing into your beer with frustration.

share|improve this answer
1  
You didn't address your second bullet point, which is the actual question. You cannot guarentee a share will always be available. The server could be temporarily unavailable for any number of reasons: it's rebooting, it's off, network issues... The gross timeout in Windows is insane for local fileshares, and intolerable because it's done single-threaded, blocking all response from the instance of explorer once it starts trying to connect. –  djs Jul 13 '11 at 17:34
    
@djs I asked the original question - and I posted the answer that worked for me. I didn't address the second bullet point because that wasn't the best solution in my case. Why the vote down? –  Contango Feb 28 '12 at 11:57
2  
Did not realize you had answered your own question. The question is actually quite a good one, but you didn't answer it. There may not be an answer, but you can't guarantee a network (device) won't misbehave, so it's always possible that explorer will hang for a long time... –  djs Mar 4 '12 at 9:33

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.