Troubleshooting local network issues:
First, from the computer ping the local loopback 127.0.0.1 this will ensure the NIC is functioning correctly.
Second, ping the Default Gateway for example 192.168.0.1 if this fails try and ping another PC on the same network.
To find the default gateway that is set (normally via DHCP) on a Windows machine Start > Run > Type cmd and enter – in the black box type “ipconfig /all” followed by enter. This will display information relating to IP, DNS, Default Gateway and Subnet mask.
If both pinging the default gateway and another PC fail and you have a working PC – verify the PC that isn’t working is in the same subnet by running an ipconfig /all and compare the IP, subnet mask and default gateway.
Tracert can be handy to see where the packets drop off and may help identify where the fault lies.
Try and ping (if have access) from router to router to test connectivity.
Most issues are configured with an incorrect IP, Subnet mask or default gateway. A good example of this is one I encountered recently. There was a PC that could talk to a printer offsite but not on site on inspecting further the printer had the wrong subnet mask, meaning when the PC was on site, the printer was in a totally different subnet to that of the PC – a quick amendment of the mask and boom it worked. Easily missed.
Always consult with network documentation to ensure IP addressing is correct with VLSM networks. As as last resort use a Subnet calculator such as Bitcricket beware you’re not allowed a calculator on the exam.
- Ping 127.0.0.1
- Ping another PC on same network to verify connectivity
- Ping Default Gateway (cmd> ipconfig all)
- Ping DNS servers
- Ping router to router
- Tracert to see where packets are dropped
- Check cables
- Consult with network documentation, if unsure use a subnet calculator