Xp/Me network problem

[Guest]

I've got 2 computers networked.one with Xp home the other
one with ME.Xp can't see its self or the other
computer.and on ME it can see it's self but can not see XP

 

[JeffO]

You need to check several things:
1) Do they each have "Client for Microsoft Networks"
installed on the network adapter?
2) Do they each have TCP/IP installed on the network
adapter?
3) When you click on the instance of TCP/IP and go to
properties, do they each start with the same two octets?
For home networking, you ought to use 10.0.0.1 for one
PC, 10.0.0.2 for the next, and so on.
4) Are they each on the same subnet mask? The "ten-dot"
range I mentioned is the 255.0.0.0 subnet.
5) And a not-too-well-known gotcha: While NT-Win2K-XP all
capitalize your domain or workgroup names as you type
them in, Win9x-WinME don't. The workgroup name is case-
sensitive. Make sure both computers are members of the
same workgroup (all caps).

Unfortunately, there's always been a mystery set of
problems between Win9x and NT. Even when you do things
right, you might still have problems.
Good luck.

 

[Steve Winograd [MVP]]

I've got 2 computers networked.one with Xp home the other
one with ME.Xp can't see its self or the other
computer.and on ME it can see it's self but can not see XP

These tips should help you get everything working:

1. Permanently disable XP's built-in Internet Connection Firewall on
local area network connections -- it's for use only on a direct modem
connection to the Internet. Disable and un-install all other
firewalls while troubleshooting. Details here:

Windows XP Internet Connection Firewall
http://www.practicallynetworked.com/sharing/xp/ic_firewall.htm

2. Use only one protocol for File and Printer Sharing. If the network
needs more than one protocol, unbind File and Printer Sharing from all
but one of them. Details here:

Windows XP Network Protocols
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

3. Make sure that NetBIOS over TCP/IP is enabled on all computers.
Details here:

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/sharing/troubleshoot/netbt.htm
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Steve Winograd [MVP]]

You need to check several things:
1) Do they each have "Client for Microsoft Networks"
installed on the network adapter?

Good suggestion.

2) Do they each have TCP/IP installed on the network
adapter?

Good suggestion.

3) When you click on the instance of TCP/IP and go to
properties, do they each start with the same two octets?
For home networking, you ought to use 10.0.0.1 for one
PC, 10.0.0.2 for the next, and so on.

This isn't completely right. The required number of matching octets
depends on the subnet mask. A mask of 255.255.0.0 requires two
matching octets, but the more common 255.255.255.0 requires three.

4) Are they each on the same subnet mask? The "ten-dot"
range I mentioned is the 255.0.0.0 subnet.

However, the vast majority of Windows networks have addresses in the
192.168.x.x range, which typically uses a subnet mask of
255.255.255.0. That's what every broadband router that I've seen
uses, and also what Internet Connection Sharing uses.

5) And a not-too-well-known gotcha: While NT-Win2K-XP all
capitalize your domain or workgroup names as you type
them in, Win9x-WinME don't. The workgroup name is case-
sensitive. Make sure both computers are members of the
same workgroup (all caps).

I've noticed that some systems force the workgroup name to all capital
letters, but I've never seen it cause a problem. In my experience,
the workgroup name is not case sensitive in any version of Windows.

However, there's no need for computers to be in the same workgroup.
Windows networking supports multiple workgroups, and computers in any
workgroup can access computers in any other workgroup.

Unfortunately, there's always been a mystery set of
problems between Win9x and NT. Even when you do things
right, you might still have problems.
Good luck.

--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com