"MSHOME is not accessible" message on a new wireless network

Archived from groups: alt.internet.wireless (More info?)

I am a new network users with Windows XP home and Linksys Wireless-G router
and Verizon DSL installed.

I can access the internet via DSL thru the router on the desktop and also
from the laptop computer with a Centrino wireless chip. However, when I
view workgroup computers from the desktop computer it only list the desktop
resources. When I do the same thing from the laptop(both are defined with
MSHOME workgroup), I get a "MSHOME is not accessible" error message. Both
computer's are logged on as Administrators.

I have checked the workgroup names on both computer and they are spelled the
same. Does anyone have any idea

Archived from groups: alt.internet.wireless (More info?)

"Jeff Liebermann" <jeffl@comix.santa-cruz.ca.us> wrote in message
news:1odtm054i3veaja86ob7jm3tt1i7scc6r9@4ax.com...
> On Thu, 14 Oct 2004 15:44:53 GMT, "NORMAN NAYLOR"
> <budnelle@verizon.net> wrote:
>
>>I am a new network users with Windows XP home and Linksys Wireless-G
>>router
>>and Verizon DSL installed.
>>
>>I can access the internet via DSL thru the router on the desktop and also
>>from the laptop computer with a Centrino wireless chip. However, when I
>>view workgroup computers from the desktop computer it only list the
>>desktop
>>resources. When I do the same thing from the laptop(both are defined with
>>MSHOME workgroup), I get a "MSHOME is not accessible" error message. Both
>>computer's are logged on as Administrators.
>>
>>I have checked the workgroup names on both computer and they are spelled
>>the
>>same. Does anyone have any idea
>
> Let me guess. You installed XP SP2 and now you don't have local area
> networking because the firewall isn't configured? Go into the
> configuration pages for the firewall and enable something like
> "Windoze Networking and Sharing" or whatever MS called it.
>
> Just for fun, let's see if you have connectivity.
> Start -> Run -> cmd -> ipconfig
> Do this on both computahs. Scribble down the IP address of the two
> computahs. It should be something like 192.168.xxx.xxx. Now, try to
> ping the *OTHER* computah with:
> Start -> Run -> cmd ->
> ping 192.168.xxx.xxx
> If successful, you have connectivity. If you have 100% packet loss,
> there's something screwed up with the LAN. One nice thing about the
> Windoze firewall is that it doesn't seem to totally block useful
> services like ping.
>
> Anyway, if you have connectivity between the two computahs, it's
> probably the firewall. If you don't have the Windoze firewall
> installed, look for other "personal firewall" products such as Norton
> Firewall, McAffee Firewall, ZoneAlarm, Kerio, Black Ice Defender, etc.
>
>
> --
> Jeff Liebermann jeffl@comix.santa-cruz.ca.us
> 150 Felker St #D http://www.LearnByDestroying.com
> Santa Cruz CA 95060 AE6KS 831-336-2558

You were right on. The problem was with the firewalls. I had both XP's and
McAfee's firewalls blocking traffic. After removing the blocks, the "view
workgroup computer" options worked. Thank you.