Gerhardpet
asked on
Windows XP Pro mapping
I have one customer with 4 Windows XP Pro computer in a workgroup.
One of the customer is hosting a files that everyone else is mapped to with drive mapping.
The mapping connection drops from time to time and I can figure out why. If I reboot the "server workstation" it works again until a user calls to say that they can't connect.
I disabled simply files sharing and now waiting to see if it will happen again.
Does anyone have some other ideas what to look for?
One of the customer is hosting a files that everyone else is mapped to with drive mapping.
The mapping connection drops from time to time and I can figure out why. If I reboot the "server workstation" it works again until a user calls to say that they can't connect.
I disabled simply files sharing and now waiting to see if it will happen again.
Does anyone have some other ideas what to look for?
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
I believe it to be 1 computer = 1 connection, even if there are multiple drive mappings from the same computer. The number goes from 10 to 5 if you are running XP home.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
All computers are Win XP Pro
I will check on the suggestions made here
I will check on the suggestions made here
I regret to inform you this is not possible. This is a limitation by design in desktop operating systems. It also represents connections to the 'server' service, so there is a high possibility that for each computer, depending on the methodology used to connect, 2 of the 10 connections is used.
One from the user itself, and one from the workstation.
Also, there are no known registry hacks or fixes to modify this behavior. If anyone mentions replacing tcpip.sys to pre-SP2 days, this is NOT a fix for the behavior you are describing, it resolves a tcp/ip concurrent connection issue, not a user sharing limit.
One from the user itself, and one from the workstation.
Also, there are no known registry hacks or fixes to modify this behavior. If anyone mentions replacing tcpip.sys to pre-SP2 days, this is NOT a fix for the behavior you are describing, it resolves a tcp/ip concurrent connection issue, not a user sharing limit.
ASKER