![]() |
|
SPONSORED LINKS BY GOOGLE |
|
2
26th April 16:27
External User
Posts: 1
|
Well, a few changes, other than just adding Windows Firewall, went into SP2. So
congrats to you for taking the plunge. A misconfigured or overlooked personal firewall, or other security component, is the most frequent, but not the only, possibility for your problem. <http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html> http://nitecruzr.blogspot.com/2005/1...isibility.html Is NetBT consistently enabled? <http://nitecruzr.blogspot.com/2006/04/netbios-over-tcpip.html> http://nitecruzr.blogspot.com/2006/0...ver-tcpip.html We could look at "browstat status", "ipconfig /all", "net config server", and "net config workstation", from each computer, and diagnose the problem, if you like. Read this article, and linked articles, and follow instructions precisely (download browstat!): <http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp> http://nitecruzr.blogspot.com/2005/0...#AskingForHelp -- Cheers, Chuck, MS-MVP [Windows - Networking] http://nitecruzr.blogspot.com/ Paranoia is not a problem, when it's a normal response from experience. My email is AT DOT actual address pchuck mvps org. |
|
|
4
28th April 09:42
External User
Posts: 1
|
It eliminates a straight connectivity problem. Either a protocol problem, or a
firewall problem, could produce this. Or a workgroup name mismatch. Read thru the articles, and see all of the possibilities yet. Or do some diagnostics. -- Cheers, Chuck, MS-MVP [Windows - Networking] http://nitecruzr.blogspot.com/ Paranoia is not a problem, when it's a normal response from experience. My email is AT DOT actual address pchuck mvps org. |
|
|
SPONSORED LINKS BY GOOGLE |
|
|