WinXP and Win2k systems can't see each other on network

[ProviaFan]

The problem is that they can not see each other on the network. My celeron can't see the shared printer on my duron system; also, they can not ping each other by either IP or hostname. Read on for details if you want to... and btw, I need to get the network set up so that I can get an ECCp-109 client onto the celeron so it can start cracking ECCp for TA, so please help me.
I'm trying to network my two systems (see them in my systems link in my sig). One is running Windows XP and the other is running Windows 2000. They are connected with an almost-50-foot-but-not-quite crossover cable that the technician at a local computer shop made for me.
My Duron system (running Windows XP) shows a link light on its NIC; the other system has no such indicator LEDs. Both of them have an icon in the system tray (or notification area, or whatever) that says they are connected to local area connection at 100Mbps. They both are also on the same workgroup, and both have individually unique names and IP addresses (192.168.0.100 and 192.168.0.102, respectively). I tried forcing them both to half duplex mode and it doesn't solve anything.
Any help you could offer would be appreciated.

 

[shlznit]

Just a thought, try a brand new crossover cable. Even though this tech may make cables all day long, there still are some exceptions. Also, try setting the mode to "Auto Select" and see if it figures it out by itself.

 

[ProviaFan]

Both systems were set at auto select before, and I'd remembered being told that sometimes a card will need to be forced into half duplex instead of full duplex to work correctly, but I'll try it again to be sure. I guess I just don't want to buy anything before I have exhausted all of the troubleshooting options I have.

 

[ProviaFan]

Well I set them to auto again and it still doesn't work.
Any other ideas aside from getting a new cable?

 

[Iron Woode]

This may sound stupid but time for some basic network stuff.

Since both are on the same workgroup, are they using the same protocol? TCP/IP i hope.

Double check that crossover cable. I bet its the cable. No lights on one nic, but says connected sounds like the cable.

Also you must activate file and print sharing to share the printer. The other pc must map to it. This can take a while to set up correctly.

A great networking site with tips and simple walk throughs is www.practicallynetworked.com

while your at it you can set up ICS and surf with both PCs.

 

[ProviaFan]

Since both are on the same workgroup, are they using the same protocol? TCP/IP i hope.

Yeah, both systems have TCP/IP, File and printer sharing, and something else like Microsoft network client.

Double check that crossover cable. I bet its the cable. No lights on one nic, but says connected sounds like the cable.

Well, the one NIC has no lights (it's a built in SiS 900 one so it's right on the motherboard), and the other NIC (a Dlink DFE-530TX+ iirc) which has lights is showing a Link light on.

Also you must activate file and print sharing to share the printer. The other pc must map to it. This can take a while to set up correctly.

Yes, I set up sharing for the printer (which is on my WinXP system), and I went to the add printer wizard and checked the option to add a network printer. When I entered the correct option (\\Duron\Epson880), it said it couldn't access it (although I can't remember the error message exactly).

A great networking site with tips and simple walk throughs is www.practicallynetworked.com

Thanks, I'll check that out now.

while your at it you can set up ICS and surf with both PCs.

Of course, I'll be doing that

 

[JackMDS]

Setting Network in XP Pro.

Sharing in XP Pro.

 

[ProviaFan]

Thanks for the links, but I can't work on the file sharing and such until I can get the computers to talk to each other

 

[JackMDS]

When XP claims thta it has LAN connection, that means that the OS detected NIC installed, but that does not mean that you have a functional Network.

Pinging is the most basic Test, it supposes to work regardless of sharing, if it does not ping. Your Basic setting, and or hardware are not functional.

Network setting is ?slightly? more then

>>>They both are also on the same workgroup, and both have individually unique names and IP addresses (192.168.0.100 and 192.168.0.102, respectively). <<<

If you are absolutely convinced that your setting is correct then buy spare components, and start to swap.

 

[Iron Woode]

I have another dumb question: Is the built-in NIC turned on in the BIOS?

Getting the basic network set up is not that hard. Binding tcp/ip to each NIC and then seeing if you can ping the pc will tell you a lot.

I have done this identical network before. It only took me 10 mins.

Win2k and winxp will tell you if you are actually connected or not. The icon will display a message like "not connected to local network". You can also check the status of the connection too.

If you want simple ICS with out a lot of nonsense then use the win2k machine as the router. If found XP to be a little difficult to set up ICS on.

 

[Valhalla1]

from what he said, both show icons in the tray as connected, and the one with the link light shows a link, so I think both nic's are just fine and enabled and i dont think the problem is in the duplex settings or the cable

have you tried having the computers ping themselves? try 'ping localhost' and then make sure you try 'ping 192.168.0.100' on that machine and see if it says "network unreachable" or if it succeeds.

if it works, and the other one does too.. and the only protocol you are using is tcp/ip and they are on the same subnet (255.255.255.0 subnet mask) then it might be the hardware or cable..

my network consisting on a win98 laptop, XP workstation and linux samba file server, I notice that after a reboot of one of the windows clients it takes a good 5 minutes for everyone to show up in "network neighborhood"

 

[ProviaFan]

Each one can ping itself, but neither can ping the other. The subnet address is 255.255.255.0 . Both are properly configured (as far as I can tell) for TCP/IP.

 

[ProviaFan]

Well it works fine now. I put in a different crossover cable (bought at the Circuit City), and it works great.