Windows 2000 mapped drives stop responding

[doug]

So I have a fully patched/updated machine running Windows 2000 Pro that shares out a couple of drives. It is not joined to a domain, just standalone.

It seems that after a certain amount of data has been exchanged by the machine it will no longer allow other machines to access the mapped drives. The machine is still able to communicate out, at least it can access the internet fine.

Any ideas, I have searched around but not found any relevant issues.

The amount of data transferred before it stops responding seems to be > 1GB and it doesn't matter if that it the machine talking to the internet or other machines accessing it's mapped drives.

 

[doug]

So nobody has any ideas or thoughts on how to diagnose?

Does anyone use mapped drives with a Windows 2000 Pro machine and transfer lots of data?

 

[DrGreen2007]

How many computers are accessing the 2000 box?

Im guessing maybe its hitting the 10 connection limit that workstations have
What happens when a machine tries to connect?
Are there messages in the event logs?

 

[doug]

Only 2 computers accessing the machine.

The machine trying to connect looks as if the computer is not there. Mapped drives say something like drive not available.

 

[doug]

Hmm might have found it, there were a few of these.

The server was unable to allocate a work item number times in the last number seconds.
http://www.microsoft.com/techn...sgs/4298.mspx?mfr=true

The solution suggested is:

Increasing the number of system pages for the server in the registry. Open the Registry Editor. Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management select SystemPages. From the Edit menu select DWORD. For Data enter 10000. Click OK and exit the Registry Editor. Shut down and restart Windows 2000.

 

[Smilin]

Are you getting any event id 2020 or 2021s in your system event logs? Any errors from the server service?

What is the exact text of the error message the client sees?

 

[doug]

The error from the client is
80070035 The network path was not found

This error comes from a VBscript so the source is WSHNetwork.MapNetWorkDrive
It also fails if you try to manually map the drives. If you try to use a drive you had previously mapped then it doesn't respond.

I think the above solution fixed it.