About troubleshooting in page 151

[hayden]

Page 151 introduce the 4 steps to troubleshoot the networks, i am confused with the step 2:
It is discribed that "If it fails, there is a problem with the NIC. Success here doesn’t mean that a cable is plugged into the NIC, only that the IP protocol stack on the host can communicate to the NIC (via the LAN driver)."
I do try on my WindowsXP, but when i ping my network address, for example, 192.168.1.5, it is timeout, because the cable is not plugged into the NIC.

Hope your reply, thank you!

[vanarnum]

I am experiencing the same symptoms. The Windows XP operating system does not recognize the NIC until there is a valid connection. You can apply an IP address and mask along with the default gateway in the network configuration on the computer, then do a <ipconfig /all> command and you will not see the ip address on the NIC. Now install the LAN cable so that there is a valid connection. Do the <ipconfig /all> command and the IP address/mask and default gateway show up. You can also <ping> at this point. Conclusion,you don't neccessarily have a bad NIC if the ping of the NIC address does not work. Yor should be able to look at the icon in the tray at the bottom of the screen and see if the cable is connected. You can also do the <ipconfig ?all> command and it will tell you that the cable is not connected. If the cable is connected, then you may wnt to consider that the NIC is faulty.