Win 2K IP networking problem

[claresnyder1]

I just got involved with a small private school networking problem. They have win98 and W2k professional on the network - in a lab and in the staff room. They are purely Peer to Peer. The staff room has only 2 machines, so a crossed cable is used instead of a hub. The 2 machines are both W2K, and have NICs that have been proven to work on W2K on another machine. When installed on these 2 machines, with assigned IPs of 192.168.0.1 and 0.2, the connection is found (cable disconnected error goes away when cable plugged in) but it is impossible to ping either the local or remote IP address. Workgroup and subnets match between machines. I have tried 3 different sets of NICs, to no avail.
What can cause this? How do I fix it?
On a third machine (in the lab) 6 of 7 machines could ping each other - but none could ping the machine with 192.168.123.10, and it could not ping 192.168.123.6 All others could ping 123.6, and each other. 123.10 could ping all but 123.6. I replaced the NIC, and it appears to work.

Any help appreciated!!!!!!!

 

[wolluf]

Is it really a crossover cable between those 2 machines?

 

[claresnyder1]

Definitely a crossover cable. W2k sees the cable connect too - but cannpt ping ITSELF, much less the next machine. @ machines both have the same problem. When cabled direct, or disconnected, the connection dissapears.

 

[wolluf]

Try another cable? Are the NICs compatible speeds? (ie, both support either 10 mbs, 100 mbs or both. If one is 10 and the other 100...). Try netbeui protocol?

 

[claresnyder1]

Checked the cable with cable checker - both cards identical. Netbeui won't cut it as I need to run NATS for internet.
Remember - the problem is the computer CANNOT EVEN PING ITSELF. This USUALLY indicates a malfunctioning NIC, but the NICs all work in another W2K machine

 

[wolluf]

You've confused me now - I thought these two machines were just networked to each other - but now there's an internet connection - so what's the full config?

PS. I presume device manager shows no problems for NICs?

 

[Gersen]

If you can't ping the machine's own IP address, either the NIC is not functioning or TCP/IP is not installed correctly.

Try to ping 127.0.0.1 to test TCP/IP. That address should respond even if your NIC is hosed. If it doesn't, remove TCP/IP, rebooot, reinstall TCP/IP.

Gersen

 

[hchman]

What brand of PC are you using? Just a thought but some PCs have specific slots that NICs will not work in. Try installing the NIC in a different slot.

 

[hchman]

I'm sorry. I meant what brand of mother board are you using. Some motherboards require the NIC be in a certain slot.

 

[claresnyder1]

The motherboards are DFI and at one time the network DID work. The DFI boards do not care where the NIC is - and I sold close to a hundred of these systems - with no network problems on Win 95 and Win98/ The internet connection is a simple dialup - attempting to share it with the ICS supplied with W2K. This is a NAT router - dead simple.

I forgot about the 127.0.0.1 - will need to try that and see if the IP stack is blown. I'm not real familiar with W2K - what is the easy way to replace files - and what do I need to replace. I suspect by removing and reinstalling TCP/IP the stack will be fixed? What about WinSock? Is it a possibility? Wsock32.dll? What else?

 

[wolluf]

If you're using win2k's ICS you shouldn't be assigning IP addresses - when you enable ICS by sharing the internet connection, it sets the IP on that PC to 192.168.0.1 and acts as a simple DHCP server for the rest of the network - so other machine should be set to pick up IP address (& DNS) automatically.

 

[claresnyder1]

I am fully aware that the ICS can be used as a DHCP - but it does not NEED to be. I have one running with fixed IPs of 192.168.123.1 - 254. Regardless, the OS is not talking to the NIC, so at this point in time that is a moot point.
I have used ICS on XP Pro as well as W98. I have also used SyGate on W95 and W98. I only mentioned the ICS because using it, or any NAT requires IP to be fully functional - NetBeui won't cut it.

 

[Gersen]

To remove TCP/IP you go to the properties of your local network connection (Control Panel/Network and Dial-up, right click your local connection, choose Properties) then just highlight TCP/IP and Uninstall. You might want to add NetBEUI first so there's something there for your card to bind to. Then reboot and add TCP back.

Beats me how to replace the Winsock files... I'm away from a Win 2000 box.

Gersen

 

[wolluf]

Clare,

I've been using ICS on Win2k for ages. It didn't work when I tried to use fixed IP addresses - so thought I'd mention it. Also mentioned netbeui cos if you can get that working your network is physically ok - if not, best look at hardware. Oh yes - you can share internet conection using a proxy server with netbeui (

http://www.analogx.com

has one).

Good luck rebuilding your TCP/IP.

 

[claresnyder1]

I DETEST proxy servers. NATS is so much simpler. When I get back to the site I will try replacing IP stack and see if that fixes it. Just had a W95 machine that couldlog onto the ANNEX server at the University and see a few sites, but fail most - had to replace Winsock and IP on that one - works well now. It could ping - but had no NIC, just Dial Up Adapter