Operations Week Part 1: The Command Line – Your Network Eyes

When a coworker says “The internet is slow” or “I can’t print.” you don’t start by tearing open the walls. You start by opening a terminal. The Command Line Interface (CLI) allows you to “talk” directly to the network stack to see where the communication is breaking down.

Here are the fice essential commands every Network+ student and IT professional must master.

ipconfig (windows) / ifconfig or ip addr (Linux)

The “Where am I?” Command.

This is always step one. Before you can fix the network, you need to know what your computer thinks its own address is.

• What it tells you: Your IP address, Subnet Mask, and Default Gateway.
• The “Pro” Move: Use ipconfig /all to see your MAC address and, most importantly, your DNS Servers.

2. ping

The “Are you there?” Command

Ping uses ICMP (Internet Control Message Protocol) to send a “Request” to another IP and wait for a “reply.”

• What it tells you: Connectivity and Latency.
• Troubleshooting Logic: 1. Ping 127.0.0.1 (Yourself).
• Ping your Gateway (The Router).
• Ping 8.8.8.8 (The Internet).
• If step 2 fails but step 1 works, the problem is your local cable or switch port!

3. tracert (Windows) / traceroute (Linux)

The “Where is the leak?” Command.

If Ping tells you that a connection is failing, Tracert tells you where. It shows every “hop” (router) your packet hits on its way to the destination.

• The Benefit: If the first hop fails, the problem is in your building. If the 5th hop fails, the problem is with your ISP

4. nslookup / dig

The “What’s your name?” Command.

As we discussed in “DNS Week,” it’s almost always a DNS problem. nslookup allows you to test if your DNS server is correctly translating names to IPs.

• The “Pro” Move: You can use nslookup [domain] [DNS Server] to test a specific server. For example: nslookup google.com 8.8.8.8 forces the test through Google’s servers instead of your jobs.

5. netstat

The “Who are you talking to?” Command

This is vital for security and performance. It shows every active connection your computer has.

• What it tells you: Which ports are open and which remote IPs are connected to you.
• Support Tip: If a computer is acting sluggish, run netstat -an. If you see hundreds of outbound connections to an unknown IP, you might be looking at a malware infection or a “botnet” phone-home.

🧪 The “Grind” Reality: Documentation

The secret of being a great Support Associate isn’t just knowing the commands it’s Documenting the results. when you find a fix using these tools, save the output. Next time that coworker has an issue, you’ll have a baseline to compare against.

What’s Next?

Commands tell you what’s happening now, but what if you want to know what happened last night at 2:00 AM? Tomorrow, we dive into Network Monitoring & SNMP. We’ll learn how to keep a 24/7 watch on our jobs “heartbeat”