I can see yours, but you can't see mine

[Paul Lautman]

I have a wireless network at home and my wife and I both have laptops.

Her laptop is set to be in a workgroup called REL (which she uses at work)
whilst mine is in MSHOME.

I just brought her one back from hibernation and asked it to look at the
entire windows network, but it could only see the REL workgroup. I then went
to my PC and it could see both REL & MSHOME. I suspect that after a while,
her machine would see my machine too, but is there any way that I can force
XP to find the other workgroups on the network? And why does one machine
discover them, when another does not?

TIA
Regards
Paul

 

[Guest]

Sometimes WXP delay a little bit on recognize a workgroup, but if you need to
see a particular PC just use the F3 key to search the PC, u can use the pc's
name or it's IP.

 

[Ron Martell]

I have a wireless network at home and my wife and I both have laptops.

Her laptop is set to be in a workgroup called REL (which she uses at work)
whilst mine is in MSHOME.

I just brought her one back from hibernation and asked it to look at the
entire windows network, but it could only see the REL workgroup. I then went
to my PC and it could see both REL & MSHOME. I suspect that after a while,
her machine would see my machine too, but is there any way that I can force
XP to find the other workgroups on the network? And why does one machine
discover them, when another does not?

TIA
Regards
Paul

Try changing your Workgroup setting to REL using Control Panel -
System - Computer Name and click on the Change button.

That will make things much simpler.

Good luck

Ron Martell Duncan B.C. Canada

 

[Chuck]

I have a wireless network at home and my wife and I both have laptops.

Her laptop is set to be in a workgroup called REL (which she uses at work)
whilst mine is in MSHOME.

I just brought her one back from hibernation and asked it to look at the
entire windows network, but it could only see the REL workgroup. I then went
to my PC and it could see both REL & MSHOME. I suspect that after a while,
her machine would see my machine too, but is there any way that I can force
XP to find the other workgroups on the network? And why does one machine
discover them, when another does not?

TIA
Regards
Paul

Paul,

Having both computers in the same workgroup does simplify things, but it may not
be the only setting you need to make. A common problem, when you have
asymmetrical visibility like yours, is a misconfigured or overlooked personal
firewall.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

If no help, provide "browstat status" and "ipconfig /all" from each computer, so
we can diagnose the problem. Read this article, and linked articles, and follow
instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

 

[Paul Lautman]

Try changing your Workgroup setting to REL using Control Panel -
System - Computer Name and click on the Change button.

That will make things much simpler.

Good luck

Ron Martell Duncan B.C. Canada

But I also use the other workgroup. It's one of the things that IBM Access
Connections doesn't change when it detects a connection.

 

[Paul Lautman]

Paul,

Having both computers in the same workgroup does simplify things, but
it may not be the only setting you need to make. A common problem,
when you have asymmetrical visibility like yours, is a misconfigured
or overlooked personal firewall.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

If no help, provide "browstat status" and "ipconfig /all" from each
computer, so we can diagnose the problem. Read this article, and
linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

I'll give it a go when the othermachine next comes home