Can't see my PCs

[Warren]

I have A BT Voyager 2100 router hard-wired to my PC's
ethernet card (running XP home). My 2nd PC (running XP
pro) has a network adaptor card connected wirelessly to
the said router. Both PC's access the internet
effortlessly. I ran the 'set up a small home or small
office network' on both pcs following the instructions to
the letter with the workgroup name MSHOME. unfortunately,
neither PC sees each other. When I click 'view workgroup
computers' I get the message: mshome is not accessible.
You may not have permission to use this network resource.
Contact the administrator of this server to find out if
you have access permissions. The list of servers is not
currently available. Please help, I'm stumped.

 

[Hans-Georg Michna]

I have A BT Voyager 2100 router hard-wired to my PC's
ethernet card (running XP home). My 2nd PC (running XP
pro) has a network adaptor card connected wirelessly to
the said router. Both PC's access the internet
effortlessly. I ran the 'set up a small home or small
office network' on both pcs following the instructions to
the letter with the workgroup name MSHOME. unfortunately,
neither PC sees each other. When I click 'view workgroup
computers' I get the message: mshome is not accessible.
You may not have permission to use this network resource.
Contact the administrator of this server to find out if
you have access permissions. The list of servers is not
currently available. Please help, I'm stumped.

Warren,

please have a look at http://www.michna.com/kb/wxnet.htm.

Hans-Georg

 

[Chuck]

I have A BT Voyager 2100 router hard-wired to my PC's
ethernet card (running XP home). My 2nd PC (running XP
pro) has a network adaptor card connected wirelessly to
the said router. Both PC's access the internet
effortlessly. I ran the 'set up a small home or small
office network' on both pcs following the instructions to
the letter with the workgroup name MSHOME. unfortunately,
neither PC sees each other. When I click 'view workgroup
computers' I get the message: mshome is not accessible.
You may not have permission to use this network resource.
Contact the administrator of this server to find out if
you have access permissions. The list of servers is not
currently available. Please help, I'm stumped.

Warren,

Are you running both Client for Microsoft Networks, and File and Printer Sharing
for Microsoft Networks (Local Area Connection - Properties), on each computer?
Do you have shares setup on each?

Are you running NetBIOS Over TCP/IP (Local Area Connection - Properties - TCP/IP
- Properties - Advanced - WINS) on each computer?

Make sure the browser service is running on each computer. Control Panel -
Administrative Tools - Services. Verify that the Computer Browser, and the
TCP/IP NetBIOS Helper, services both show with Status = Started.

On any XP Pro computer, check to see if Simple File Sharing (Control Panel -
Folder Options - View - Advanced settings) is enabled or disabled. With XP Home
and Pro on the LAN together, you need to have SFS enabled.

For XP Home, and for XP Pro with Simple File Sharing enabled, make sure that the
Guest account is enabled, on each computer. Enable Guest with Start - Run -
"cmd" - type "net user guest /active:yes" in the command window.

Do any of the computers have a software firewall (ICF / WF, or third party)? If
so, you need to configure them for file sharing, by opening ports TCP 139, 445
and UDP 137, 138, 445, by enabling the File and Printer Sharing exception, and /
or by identifying the other computers as present in the Local (Trusted) zone.
Firewall configurations are a very common cause of (network) browser, and file
sharing, problems.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[Guest]

Hi try this site to install Netbuei
http://www.wown.com/articles_tutorials/winxpnet.html

 

[Hans-Georg Michna]

Hi try this site to install Netbuei
http://www.wown.com/articles_tutorials/winxpnet.html

Gordon,

that's not a good idea. Normally you don't want to build a
second road only because there's some dirt on the first one.

Having more than one transport protocol creates its own problems
as well, so one wants to avoid that, unless there's a really
good reason to run a second protocol.

Hans-Georg