Network troubleshooting commands

Discover essential Network Troubleshooting Commands like ping, tracert, netstat, and ipconfig to diagnose, analyze, and fix connectivity issues efficiently.

Importance of Troubleshooting in Networking 

Troubleshooting is one of the most critical skills in networking. Whether you're a NOC  engineer, system admin, CCNA student, or cloud/network architect, being able to identify,  isolate, and fix network problems ensures reliable connectivity, performance, and security. 

Why Is Troubleshooting Important in Networking? 

1. Ensures Business Continuity 

• Networks connect everything — servers, users, cloud apps, and databases. • A small issue (e.g., switch port down or DNS failure) can halt business operations. Example: If a core switch fails, no one can access the internet, apps, or shared drives. 

2. Reduces Downtime 

• Quick troubleshooting minimizes outage time and maintains SLAs. 

• The faster you find the root cause, the sooner services are restored. Tools like ping, show ip int brief, traceroute, and logs are used immediately when issues arise. 

3. Identifies Root Cause 

• Troubleshooting helps find not just what broke, but why. 

• This prevents repeat incidents and leads to long-term fixes, not just temporary workarounds. 

4. Improves Network Security 

• Detecting unexpected traffic or unreachable devices may indicate: 

o Malware 

o Unauthorized devices

o Configuration changes 

• Troubleshooting is the first step in incident response. 

5. Develops Technical Expertise 

• You learn how protocols behave, how devices interact, and what common failure points look like. 

• Every troubleshooting experience improves your real-world networking knowledge. 

6. Saves Time and Cost 

• Reducing downtime = saving money. 

• Early detection of issues (e.g., congestion, packet drops) avoids expensive escalations or hardware damage. 

7. Boosts Network Performance 

• Troubleshooting helps resolve: 

o Latency 

o Packet loss 

o Bandwidth issues 

• Result: Better user experience and app performance. 

Troubleshooting Process (Simplified) 

Step Action 

1. Identify What's the issue? When did it start? 

2. Isolate Which device, layer, or protocol is affected? 

3. Investigate Use commands/tools to check logs, interfaces, etc. 

4. Resolve Fix configuration, replace cable/device, or restart

Step Action 

5. Verify Test again (ping, traceroute, app access) 

6. Document Log what happened and how you solved it 

Real-World Examples 

Issue Troubleshooting Fix 

PC can't access the internet. Checked ipconfig, gateway unreachable 

VLAN is not communicating. Checked trunk ports, show vlan brief 

Slow app access. Checked ping, found latency onthe  switch 

AWS EC2 unreachable. Checked the security group and route table 

Summary 

Key Benefit Description 

Keeps the Network Running, avoids costly downtime and outages 

Sharpens Skills, Makes you a better engineer 

Helps with Certifications Essential for CCNA, AWS, Azure, etc. 

Critical issues in Real-World Networks always face issues – you must solve them 

Here’s a list of important interview questions on Network Troubleshooting, categorized by skill level, and including sample answers, which were helpful. These are perfect for roles like NOC Engineer,  Network Admin, Support Engineer, or CCNA-level jobs.

Beginner-Level Questions 

1. What is the first step you take when a user reports no internet? 

Answer: I check physical connectivity (cables, link lights), then verify IP settings using ipconfig or ifconfig, followed by a ping to the gateway. 

2. Commands to check basic connectivity 

• ping 

• tracert / traceroute 

• ipconfig / ifconfig 

• nslookup 

• arp -a 

3. How do you check if a PC has a valid IP address? 

Use ipconfig (Windows) or ifconfig (Linux) to verify IP, subnet mask, and default gateway. 

4. What is the use of traceroute? 

It shows the path packets take to reach a destination and helps identify where the connection is failing. 

Intermediate-Level Questions 

5. What could be the cause if ping 127.0.0.1 works but ping default gateway fails? 

The TCP/IP stack is working, but the NIC or local network connection may be faulty. 

6. What are the common causes of high latency or packet loss? 

• Faulty cables or ports 

• Network congestion 

• Routing issues

• Firewall/NAT problems 

• DNS delays 

7. How would you troubleshoot VLAN communication issues?

 Check: 

• show vlan brief to see port assignments 

• show interfaces switchport 

• Trunk configurations 

• Ensure devices are on the same subnet and VLAN 

8. How do you check port reachability? 

Use: 

• telnet <IP> <port> 

• nc -zv <IP> <port> (Linux) 

• nmap 

• Check firewall and ACL rules 

Advanced-Level Questions 

9. How do you troubleshoot routing issues in a multi-router network? 

Use: 

• show ip route 

• traceroute to trace hops 

• ping with source interface 

• debug ip routing (with caution) 

10. A user can ping external sites by IP but not by name — what’s wrong? 

DNS issue. Try nslookup, check DNS server settings, or try an alternate DNS like 8.8.8.8.

11. What’s the difference between Layer 2 and Layer 3 troubleshooting? 

Layer 2 Layer 3 

Focuses on MAC addresses and VLANs. Focuses on IP addresses, routes. Commands: show mac, show vlan. Commands: ping, traceroute, show ip route 

Here’s a practical OSI Layer-wise Command Reference to help you troubleshoot networks systematically, from Layer 1 (Physical) to Layer 7 (Application) — especially useful in interviews, NOC/SOC roles, and CCNA-level tasks. 

OSI Model Troubleshooting – Layer by Layer with Commands 

OSI Layer Function Troubleshooting Focus Common Commands / Tools 

Layer 1 – Physical 

Cables, ports, power, interfaces 

• Commands: 

o show interfaces (Cisco) — look for line protocol is down, CRC errors o ethtool eth0 (Linux) — check link status 

o Check link lights, cables, and connectors 

o Windows: check NIC in Device Manager 

Use case: Interface down due to unplugged cable or hardware issue 

Layer 2 – Data Link 

MAC addresses, switching, VLANs, ARP 

• Commands: 

o show mac address-table (Cisco Switch)

o show vlan brief 

o arp -a (Windows/Linux) — ARP table 

o show interfaces switchport (Cisco) 

o debug arp (Cisco) 

Use case: Devices in the same VLAN can’t communicate 

Layer 3 – Network 

IP addressing, routing, ping, traceroute 

• Commands: 

o ping <IP> 

o traceroute <IP> / tracert <IP> (Windows) 

o show ip interface brief (Cisco) 

o show ip route 

o ipconfig / ifconfig 

Use case: Routing issue between subnets or incorrect gateway 

Layer 4 – Transport 

TCP/UDP ports, sessions, connections 

• Commands: 

o netstat -an — view open ports and sessions 

o telnet <IP> <port> — check port accessibility 

o nc -zv <IP> <port> — Linux alternative 

o ss -ltn or netstat -tulpn (Linux) 

Use case: App not responding due to blocked port or wrong protocol 

Layer 5 – Session

Session management, login state, timeouts 

• Commands: 

o show users (Cisco) 

o show sessions 

o Check SSH/Telnet login status 

o Look for session timeouts, authentication drops in logs. Use case: Remote sessions keep disconnecting 

Layer 6 – Presentation 

Data format, encryption, compression 

• Commands/Checks: 

o Check SSL/TLS settings 

o Use openssl s_client -connect host:443 (Linux) 

o Browser padlock icon (SSL cert info) 

Use case: HTTPS not working due to cert issue or cipher mismatch 

Layer 7 – Application 

Apps, services, DNS, HTTP, SMTP, FTP 

• Commands: 

o nslookup / dig — DNS resolution 

o curl <URL> — test HTTP/HTTPS 

o telnet smtp.domain.com 25 — check mail server 

o ftp, ssh, wget — test specific protocols 

o show logging or debug (Cisco) — application log analysis Use case: Website not opening, DNS issues, service unreachable.

Frequently Asked Questions (FAQs)

1. What are network troubleshooting commands?

Networking Troubleshooting Commands: These are the tools needed from the command line when troubleshooting is required in computer networks. These tools check the connection, routing, address resolution, and status of the interfaces.

2. Why are network troubleshooting commands useful for network professionals?

These commands are critical because they enable IT experts and network managers to promptly address any issues with unreachable hosts, sluggish network performance, wrongly configured interfaces, and DNS failures.

3. What are the most used commands in network troubleshooting?

Some of the most frequently used commands are ping, which is a connectivity test command, traceroute/tracert, which traces the route of the packets, ipconfig, which gives the details of the interface, netstat, which provides the current connections, and nslookup, which is a DNS lookup command.

4. What role does the ping command play in network troubleshooting?

The ping command is used to transmit packets towards a destination for measuring response time and used as a method for determining whether a host is accessible and whether there is latency on a network connection.

5. What is the function of the traceroute or tracert command?

The traceroute command on Linux or macOS or tracert command on Windows will trace the route that the packet follows to reach the target computer, which will be helpful to detect any delay or problem in the route that the packet follows.

6. How can I use ipconfig or ifconfig for troubleshooting?

The `ipconfig` command in Windows, as well as the `ifconfig` command in Linux/Mac, shows the IP configuration parameters of the network interfaces, such as IP address, subnet mask, and gateway.

7. What is the importance of the netstat command in network troubleshooting?

The netstat command displays active connection to a network, listening ports, routing information, as well as statistics. In Linux systems, this command helps a user verify any activities occurring on a connected network.
 

Do visit our channel to know more: SevenMentor

Author:-

Swati Shewale