Probably and Easy Fix: Why Can't This Computer Connect to the Network?

[Arsynic]

I'm about to pull my hair out!! My computer absolutely cannot connect to the network. I've tried everything I know, and still no solution! All cables are plugged in. One to the wall and one in the actual NIC. The LINK led on the NIC lights up and the ACT led blinks like it's supposed to. I checked the hardware settings and Windows doesn't seem to indicate that anything's wrong with the card. Two other computers on the same side work just fine. However this one simply cannot connect. I checked the hub and everything's lit, however the stupid computer cannot log in to the Novell/Windows network. I'm suspecting either corrupted drivers (which Windows doesn't indicate) or a bad Network card. Any suggestions?

 

[deeno]

My first guess with the information provided would be that there’s a problem with the TCP/IP settings on the machine. First off, can you ping the address 127.0.0.1? If you can, than can you ping the IP addresses of the other 2 machines? If not, than it’s probably a problem with the IP Address and Subnet Mask or a problem with the hub/switch itself.

Less likely, though still possible, is a corrupt driver problem. If you can’t ping 127.0.0.1, try to uninstall the network card and the TCP/IP protocol on the computer then reinstall them both. If you still can’t ping that 127 address, than you may try a different network card.

Good luck!

-deeno

 

[pinku1971]

After checking whether it can ping the local host or not, you also ping the designated IP address of the defective machine.
1) Reload the TCP component
2) DOes it connect to other computers say with NetBuei?
3) If the problem persists, you may have to open the computer and change the slot of the card and reconfigure the card.
4) CHnage the NIC.

 

[Arsynic]

Well, I found the solution. It was an IP issue, but I didn't have to do anything. The Primary Domain Controller went offline for repairs and so the IP settings were all screwed up. However, the authenticating server is a Netware 5.1 server and the other Windows 98 boxes didn't have a problem logging into the Novell network. So after I installed the PDC and set the IP configuration, the Novell Client login dialog came up like it did before and I was able to log in. I guess the confusion is how Win98 and Windows 2000 computers respond to the absense of a PDC.

I had the same problem the previous week at another site with a PDC that was down, but the Windows 2000 workstations at the other sites had no problem logging in (albeit extremely slow because of having to use a remote PDC for authentication). It seemed as if the Win2K machines found that their PDC was down and just went across the WAN to look for another PDC for authentication. I would have never guessed it was the problem because there was another Windows 98 machine right next to it that had no problem logging in. The Novell Client box came up and it logged in just fine. However on the other machine no box came up until I reinstalled the PDC. Weird!