Currently, XP1 and XP3 were installed with SP2, and
both's Windows firewall were truned on.
Please check the following two hints, taken from
http://www.michna.com/kb/WxSP2.htm.
Hans-Georg
Winsock corruption
Service Pack 2 adds a new command to repair the Winsock
corruption problem that can be caused by adware, spyware, or
some other causes.
netsh winsock reset catalog
Using this command should normally not do any harm, so if you
have unsolvable connection problems or spurious disconnections,
try it. It does remove all nonstandard LSP (Layered Service
Provider) entries from the Winsock catalog, which are usually
adware or spyware entries, but if you happen to have a
legitimate one installed, it will also go and have to be
reinstalled.
If you're really curious, you can use the command:
netsh winsock show catalog
before and after resetting the catalog to find out whether any
entries were in fact removed and which ones these were.
Workgroup is not accessible
After installing Service Pack 2 you receive the error message:
[workgroup name] is not accessible. You might not have access to
the Network resource. Contact the administrator of this server
to findout if you have access permissions.
This problem is showing up sporadically in the public newsgroups
and is currently being researched. A solution or workaround is
not yet known. Please check back here over the next few days.
Meanwhile check the following points, which could perhaps cause
this problem.
* Make sure you have only one transport protocol installed,
namely TCP/IP. Remove, disable, or at least unbind other
transport protocols like IPX (NWLink) and NetBEUI.
* If you had other networking clients installed, like certain
Netware clients, you may be in for a long, bumpy ride. Some do
damage that is almost impossible to repair. You may want to try
a repair installation of Windows XP, followed by applying
Service Pack 2 again, or, better, a repair installation with a
slipstream version of Windows XP with Service Pack 2 already
integrated.
* Repair the IP stack with the Repair command or with the
command:
netsh int ip reset
* Repair the Winsock with the command:
netsh winsock reset catalog
* If the loopback feature is enabled in a connected router,
disable it. You may even need a firmware upgrade.
* Change the workgroup name in all computers to a new, simple,
short, perhaps even all upper case one, to make sure there
aren't any problems there. You can later change it back.
* Check whether NetBIOS over TCP/IP is enabled. It should be.
* Check all NetBIOS names for possible duplicates. For example,
if the workgroup name coincides with a user or computer name,
this could cause the problem. Try opening a command line window
and issuing the command: net view
* Then issue the command: net view \\computername, where
computername should be replaced with one of the names displayed
with the simple net view command. Check all names for possible
duplication.
* Check your router's diagnostic and information pages for NAT
information, like which computer has which IP address. Any
duplication here could point to the problem.
* Disable, better uninstall or upgrade, all antivirus software
and third party firewalls.
* Rid the computer of adware and spyware. For example, run
Spybot Search & Destroy.
And, most importantly, if you find that one of these points or
any other procedure solved your problem, please let me know.
