Workgroup inaccessible until connection is reset

[Michael Pardee]

I have a home network with 3 XP Pro computers. The other
2 are upgrades over W2K, but mine is a clean install with
all updates short of SP2. I have LAN connection to the
wireless router, using the VIA on-board port with WHQL
driver. For sharing reasons, I have the XP firewall
disabled and am using a McAfee firewall with the static
DHCP addresses of he other computers (and mine) listed
as "trusted."
The network always works OK - I can ping the other
computers and they can see my computer and use my
printer. But when I try to access "view workgroup
computers" I get the message that the workgroup is
inaccessible. After much fussing I found that disabling
and reenabling the connection restores workgroup access
for all users on my computer until I reboot.
It isn't a big problem and the work-around is trivial,
but I wish I knew what's out of whack... especially while
contemplating SP2.
Thanks!

Mike

 

[Hans-Georg Michna]

I have a home network with 3 XP Pro computers. The other
2 are upgrades over W2K, but mine is a clean install with
all updates short of SP2. I have LAN connection to the
wireless router, using the VIA on-board port with WHQL
driver. For sharing reasons, I have the XP firewall
disabled and am using a McAfee firewall with the static
DHCP addresses of he other computers (and mine) listed
as "trusted."
The network always works OK - I can ping the other
computers and they can see my computer and use my
printer. But when I try to access "view workgroup
computers" I get the message that the workgroup is
inaccessible. After much fussing I found that disabling
and reenabling the connection restores workgroup access
for all users on my computer until I reboot.
It isn't a big problem and the work-around is trivial,
but I wish I knew what's out of whack... especially while
contemplating SP2.

Mike,

I've seen this problem occasionally here in the newsgroup, don't
know the cause and don't have any specific solution, only some
general hints.

Make sure you have only one transport protocol installed, namely
TCP/IP. Remove, disable, or at least unbind (remove all bindings
from) other transport protocols like IPX (NWLink) and NetBEUI.

Uninstall third party client software that can interfere with
the networking settings. Such software could have come with
network adapters or with a router.

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
(Warning: This removes all third party Layered Service
Providers—LSPs. Please see the subchapter on Winsock corruption
above.)

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

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 report back
here.

Hans-Georg

 

[Lance]

Hans-Georg Michna said the following on 9/15/2004 12:04 AM:

Disable, better uninstall or upgrade, all antivirus software and
third party firewalls.

Hans, I don't think you mean to say 'disable' or 'uninstall' antivirus.

Maybe uninstall, then reinstall and upgrade, antivirus?

Lance
*****

 

[Hans-Georg Michna]

Hans-Georg Michna said the following on 9/15/2004 12:04 AM:

Hans, I don't think you mean to say 'disable' or 'uninstall' antivirus.

Maybe uninstall, then reinstall and upgrade, antivirus?

Lance,

sure, I should have added, "for a test". Will try to remember
next time. -)

Hans-Georg

 

[Michael Pardee]

I understand, Hans!

No luck with disabling the other protocols, although
choosing "repair" does indeed have the same good effect
as disable/enable.

Never had any other NOS (or the infamous AOL), and the
installation is only a month or so old.

NetBIOS over TCP/IP is enabled, as is lmhosts lookup. Huh.

Mike

 

[Hans-Georg Michna]

No luck with disabling the other protocols, although
choosing "repair" does indeed have the same good effect
as disable/enable.

Never had any other NOS (or the infamous AOL), and the
installation is only a month or so old.

NetBIOS over TCP/IP is enabled, as is lmhosts lookup. Huh.

Mike,

so this problem remains unsolved for now. You could check
http://www.michna.com/kb/WxNetwork.htm for more ideas.

If you find a solution, some people around here would be
grateful to know.

Hans-Georg