We have a Windows XP Pro system in use as a file server.
We're using it both as a file server and as a backup device for 5 computers - so they are mapped as T:, Y:, X:, W:, V:
All of these computers are shut off over the weekends (but not the "server")
After years of working in this relatively unchanged environment, we've suddenly started seeing two problems which may be related:
First, the mapped drives started showing up as "Disconnected Network Drive". Well, maybe they showed that way before but everthing worked nonetheless. Now, at times our backup program has not been able to open them. At other times it appears that they *do* open.
So, I have run as a scheduled batch:
NET USE T: /DELETE /YES
NET USE V: /DELETE /YES
NET USE W: /DELETE /YES
NET USE X: /DELETE /YES
NET USE Y: /DELETE /YES
NET USE T: "\\A1\C\Folder1" /persistent:YES
NET USE V: "\\A2\C\Folder2" /persistent:YES
NET USE W: "\\A3\C\Folder3" /persistent:YES
NET USE X: "\\A4\C\Folder4" /PERSISTENT:YES
NET USE Y: "\\A5\C\Folder5" /persistent:YES
And, I have run:
net config server /autodisconnect:-1
Well, now it seems that the mapped drive/folders (which were really no problem in the past) are working again....
But now when someone wants to access a file on the "server" they get something like:
Access denied, too many users connected, try again later .... something like that.
The accesses aren't web pages so I don't know that IIS has anything at all to do with this.
I know the "10 connection" limitation but don't see how it could be violated unless there are accesses from one computer that persist which are added to by accesses from the same computer later, etc.
I don't know if the mapped drives constitute "connections". Do they? Seems like the connections are going the other way or are they bilateral?
I don't know how to list the connections. How? This might help in debugging this issue.
Going all the way back to the beginning, why should we suddenly have problems with mapped drives not being accessible when they were before? Any ideas there?