R
Robb
Guest
**** "system error 71 has occurred" - An undocumented solution ****
"operating system error 71" or "system error 71 has occurred"
No more connections can be made to this remote computer at this time
because there are already as many connections as the computer can
accept.
Condition: The workstation is receiving the above error when using the
NET VIEW command. The NBTSTAT -s command or NBTSTAT -S command on the
workstation shows a connected session, however that session does not
appear in the NET SESSIONS display nor in the NETSTAT display.
Solution: Restart the Workstation service on the client displaying the
error. In Windows XP Professional, the command NET STOP WORKSTATION
followed by NET START WORKSTATION should accomplish the task.
Rebooting is another alternative.
Information:
No assistance is needed. This post is simply for future reference to
help others.
I was receiving the above error running the NET VIEW command on a
Windows XP Professional SP2 Tablet PC system named TOPOL009. I am in
a Peer-to-Peer Windows Network. The master browser is TOPOL010.
Earlier, TOPOL010 appeared on the network as 192.168.177.229
(wireless) as well as 192.168.177.110 (wired). A session was
established to \\192.168.177.229\J$ during that time. Later, the
wireless card received a new DHCP address upon renewal. This seemed
to cause the orphaned session listing on TOPOL009 which pointed to the
old IP address.
TOPOL010 is a multi-homed browser, which is problematic as described
in http://support.microsoft.com/kb/191611/, however this specific
symptom is not mentioned and this problem may or may not be connected
to the multihomed-ness of the browser (I did not investigate it). I
did not change TOPOL010 to resolve the problem on TOPOL009.
None of the solutions returned in an Internet search for the error
message seemed to apply, or the solutions provided did not resolve the
problem. http://support.microsoft.com/kb/328459 is written
specifically for the condition in this error message, but again either
the circumstances did not fit or the suggested fixes did not apply.
In short: I should have rebooted.
That should always be early in
troubleshooting!
Hope this helps someone in the future.
"operating system error 71" or "system error 71 has occurred"
No more connections can be made to this remote computer at this time
because there are already as many connections as the computer can
accept.
Condition: The workstation is receiving the above error when using the
NET VIEW command. The NBTSTAT -s command or NBTSTAT -S command on the
workstation shows a connected session, however that session does not
appear in the NET SESSIONS display nor in the NETSTAT display.
Solution: Restart the Workstation service on the client displaying the
error. In Windows XP Professional, the command NET STOP WORKSTATION
followed by NET START WORKSTATION should accomplish the task.
Rebooting is another alternative.
Information:
No assistance is needed. This post is simply for future reference to
help others.
I was receiving the above error running the NET VIEW command on a
Windows XP Professional SP2 Tablet PC system named TOPOL009. I am in
a Peer-to-Peer Windows Network. The master browser is TOPOL010.
Earlier, TOPOL010 appeared on the network as 192.168.177.229
(wireless) as well as 192.168.177.110 (wired). A session was
established to \\192.168.177.229\J$ during that time. Later, the
wireless card received a new DHCP address upon renewal. This seemed
to cause the orphaned session listing on TOPOL009 which pointed to the
old IP address.
TOPOL010 is a multi-homed browser, which is problematic as described
in http://support.microsoft.com/kb/191611/, however this specific
symptom is not mentioned and this problem may or may not be connected
to the multihomed-ness of the browser (I did not investigate it). I
did not change TOPOL010 to resolve the problem on TOPOL009.
None of the solutions returned in an Internet search for the error
message seemed to apply, or the solutions provided did not resolve the
problem. http://support.microsoft.com/kb/328459 is written
specifically for the condition in this error message, but again either
the circumstances did not fit or the suggested fixes did not apply.
In short: I should have rebooted.
That should always be early introubleshooting!
Hope this helps someone in the future.