Network drive disconnects and can't reconnect (without server reboot)

[rogerval]

Good afternoon all,
I'm having the following problem with some PCs on a domain at work (and the "official" admin is a bit puzzled too, let alone me, the "unofficial" local admin ).
The scenario: there are a few PCs (with either Windows 7 Pro or XP Pro) with networked drives which point to a Windows 7 Pro PC acting as a server.
We can get these networked drives working nicely, then without warning, the "client" machine drops it's connection, and we can't reconnect the network drive without rebooting the "server". (A message comes up something like "the network drive is already in use".)
The admin is puzzled because Windows 7 Pro can support 20 concurrent network connections (or so we believe) and when we run "netstat" on the "server" there aren't anything like 20 connections; 12 maybe, but not 20.
Has anyone got any ideas I can try?
Thanks in advance,
Roger V.

 

[rogerval]

Any ideas? This is driving me a bit nuts.
Thanks in advance,
Roger V

 

[phantomofrussia]

My first question would be why are you guys using a client machine for sharing when you are in a domain environment?

But here is a thread I found that might solve your problem: http://www.sevenforums.com/network-sharing/71137-windows-7-stops-sharing-files.html

This is what solved that users problem with network sharing:

On the server i found err id 2017 with source serv.

I googled on this errcode and found it can be solved by modifying registry.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\size was on 1 and had to be changed to 3.

It looks like it is working now.

Thanks for all your help.

 

[rogerval]

Thanks very much for the suggestion; I shall look at the machine today and see if that error applies to our "server" too.
Kind regards,
Roger V.

(Edit: after checking my work emails, I discovered that our sys admin had found errors 2017 at least once on the "server" machine's event log, and made an appropriate registry change to try and fix the problem. I restarted the machine yesterday. I wasn't sure earlier, but it looks like you and he came up with the same solution independently. I'll post back later on how our "server" is going. Thanks again, Roger V.)

 

[phantomofrussia]

Cool. Hope it is working now.