Network drives cause Explorer to hang and crash

[loekf]

Maybe I'm mistaken here.

Some observations:

- I have two QNAP NAS servers, which put the drives after 30 mins idle in sleep mode.
- Windows 7 network discovery sees the two NAS servers all the time.
- When you make drive mappings to shares on the NAS servers, (it seems) at random times Explorer hangs (goes into stall) when trying to browse/access files or directories. Only a reboot helps.
- I'm accessing the drives via regular SMB, no HomeGroup, no AD etc.
- When you map the drives initiallially it asks for a password. Storing that account info into the credentials manager doesn't help.
- I tried to open ports 137-139 and 445 in the firewall, but that doesn't help.

My theory is that Windows breaks by default the connection with the NAS after 15 mins of idling. That's standard behaviour. What puzzles me is that Visita didn't have this issue and Windows 7 has.

Do more people have issues with SMB shares ?

 

[H2SO4]

Does the same issue occur if you test in [safe mode + net]?

As a separate test, does it still happen after you uninstall (disabling is not a valid test) all anti-virus and 3rd-party firewall utilities?

 

[oldman1881]

I have the same issue during networking access, a normal file server.
i am using win7 pro.

 

[darkwingz24]

I see that this is an older post but I have recently got a new computer for our shop and is running Win 7x64. I am having problems with the mapped network drives causing windows explorer to hang.

I was running Windows 7 RC 32bit on my laptop with the same network and had no problems with the network.

With this new computer we mapped a network share to M:\ and at first we noticed a lot of prblems shutting down windows where it would hang in the "logging off" window but didn't know what was causing it. So we just put up with that and just tried to limit the reboots. But as we used the computer more we noticed that if the computer was idle for a period of time and we tried to access the mapped drive windows explorer would hang, bad. The computer was unresponsive requiring a hard boot.

It was determined that the file server was doing it's ob and auto disconnecting sessions that were idle. It seems that Windows 7x64 doesn't like that and when it tried to access the mapped drive after the disconnect it wouldn't re-establish a connections and wouldn't time out either.

So we changed the autodisconnect time on the server to never with the command:

net config server /autodisconnect:-1

Ever since doing that we have not had the Windows 7x64 machine hang on logout and accessing mapped drives is no longer an issue. While this fixes the problem with the machine becoming unusable I would like to find a fix for the Win7x64 machine so I can turn on autodisconnect on the file server so it can actually manage connections like it's supposed to.

Cheers