When the network isn’t working, the organization isn’t working. In this video, we’ll show you some command line utilities that can help you find any problems that might be lurking in your network. We’ll demonstrate IPCONFIG, NSLOOKUP, PING, TRACERT, PATHPING, NBTSTAT, and NETSTAT. We’ll also give you some best practices for troubleshooting network interfaces, protocols, and firewalls.
2 thoughts on “Troubleshooting Network Connections”
I would like to know how to idendtify any ip addresess that tracert might reveal. ie. who they belong to assuming no that just ip and or mack address is revealed with no names
Jonathan – If an IP address is an internally assigned address from a DHCP server, you can check the DHCP server logs to determine who received the address. If the address is public, you can query the ARIN database to determine who owns the IP address.
Comments are closed.