~Not allowed to see MSHOME~

27 Jul 2006 3:36 AM

CmosDriver

I'm running an XP PRO that's connected to a 2WIRE home portal via ethernet. I
have a Win2k PRO that's connected wirelessly to the same 2WIRE portal. Both
have access to the internet and both desktops can ping each other but the XP
can't gain access to the MSHOME workgroup, the 2K has no problem. It sees
itself in MSHOME but not the XP. All I'm getting on the XP when I click "View
network computers" is "MSHOME IS NOT ACCESSIBLE. Blah blah etc etc.

I haven't >home networked< in a very long time and I used to never have this
problem. I've tried some of the things from different websites but can't
figure out what it is that I'm missing.

HELP!!! THANX N ADVANCE
Cmos Driver

27 Jul 2006 4:26 AM

Chuck

On Wed, 26 Jul 2006 20:36:01 -0700, CmosDriver
<CmosDri***@discussions.microsoft.com> wrote:

>I'm running an XP PRO that's connected to a 2WIRE home portal via ethernet. I
>have a Win2k PRO that's connected wirelessly to the same 2WIRE portal. Both
>have access to the internet and both desktops can ping each other but the XP
>can't gain access to the MSHOME workgroup, the 2K has no problem. It sees
>itself in MSHOME but not the XP. All I'm getting on the XP when I click "View
>network computers" is "MSHOME IS NOT ACCESSIBLE. Blah blah etc etc.
>
>I haven't >home networked< in a very long time and I used to never have this
>problem. I've tried some of the things from different websites but can't
>figure out what it is that I'm missing.
>
>HELP!!! THANX N ADVANCE
>Cmos Driver

One of the most common causes of this problem would be a misconfigured or
overlooked personal firewall, or other security component. There are several
other possibilities too, and any might be the cause of your problem. Read this
article with an open mind.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

You could look at "browstat status", "ipconfig /all", "net config server", and
"net config workstation", from each computer, and diagnose the problem. 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/05/troubleshooting-network-neighborhood.html#AskingForHelp

Please let us know if any of these suggestions are of any help. What you learn
may help others in the future, and that's the purpose of these forums.

--
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.