Thanks for viewing my question.
I am responsible for a P2P network made up of 5 Windows XP Pro computers, all SP2 with all updates and current Antivirus software, and known to be virus and spyware free. One of the PCs is used as a file server for the other PC users data. There is a user at the "file server" as well. We are aware of the limit of 10 peer connections in XP Pro.
This morning, 3 PCs were running, including the "file server" PC, when a fourth user arrived and logged into their PC. When attempting to open a network drive mapped to the file server PC, this message resulted:
"No more connections can be made to this remote computer because there are already as many connections as the computer can accept."
Well this didn't make sense, so I went to the "file server" PC and ran the Computer Management snap-in. It showed 4 connections. It also show one of the PCs had 9 files open. I called this user and asked her to close some of her files, which she did. After this the fourth user was able to access her network drives.
The user that had 9 files open had several files copying from one of her network drives to another simultaneously.
I have several questions about the nature of what happened to cause this error message:
What exactly contributes to what XP considers a connection that counts toward the limit? Each PC has 2 drives mapped to the file server. Does that count as 1 connection (per PC or user) or 2 connections (per map)?
In the Management snap-in, is the Connections window not showing everything that XP considers a connection that counts toward the limit of 10?
Does a file that is open over a drive mapped to the server count? That seems unlikely as we would exceed the limit multiple times each hour.
When I remote in to the file server or a peer PC, does that somehow affect the number of connections differently than if I was sitting at the console?
All help understanding this issue is appreciated. Thanks,