Rıza KorkusuzTechnical Support

Network Troubleshooting at the Desk: A Bottom-Up Routine

Using ipconfig, ping, nslookup, and tracert to sort out DHCP, DNS, and Wi-Fi vs. wired problems

5 min readUpdated 2026-10-16Original notes

"The internet is down" is one of the most common things a support technician hears, and one of the vaguest. It could mean a loose cable, a bad Wi-Fi connection, a DHCP problem, a DNS failure, a firewall rule, or one website having a bad day.

These are the study notes I use to practice a consistent routine: start at the bottom of the stack and work up, using the built-in Windows tools. The goal at the desk usually isn't to fix the network. It's to figure out quickly whether the problem is this device, this connection, or something bigger, and then either fix it or escalate it with useful information.

Step 1: Ask a few questions first

If the whole floor is down, the problem isn't on this PC, and it's time to escalate.

Step 2: Check the physical layer (and the obvious)

netsh wlan show interfaces shows the connected SSID, signal strength, radio type, and channel, which helps when someone is on the edge of coverage.

Step 3: ipconfig, the first real data point

Run ipconfig /all and look at the active adapter [1]:

Common follow-ups [1]:

Step 4: ping, working outward

ping sends ICMP echo requests [3]. I like to work outward:

  1. ping 127.0.0.1 checks that the local TCP/IP stack responds.
  2. ping <default gateway> checks the local network segment.
  3. ping <a known internal server> checks the path inside the organization.
  4. ping <an external host> checks the path out to the internet.

Note where it fails. One caveat: many devices and firewalls block ICMP on purpose, so a failed ping on its own doesn't prove a host is down. I treat it as one clue among several.

Step 5: nslookup, separating DNS from everything else

If pinging an IP address works but the name doesn't resolve, DNS is the prime suspect. nslookup queries DNS directly [4]:

If one server resolves the name and another doesn't, that's very useful to put in an escalation ticket. If nothing resolves at all, go back and check the DNS servers listed in ipconfig /all.

Step 6: tracert, finding where the path stops

tracert shows each hop between the device and a destination [5]. It can help show whether traffic stops inside the building, at the edge of the network, or farther out. Hops that show * * * aren't always a problem, because many routers don't answer these probes. What matters most is whether the trace eventually reaches the destination.

For a specific service, PowerShell's Test-NetConnection can check a TCP port, for example Test-NetConnection server.example.org -Port 443 [6]. This helps when ping is blocked but you need to know whether a web service is reachable.

Wi-Fi vs. wired: a quick comparison

One of the fastest ways to narrow things down is to test the other connection type:

What to put in the ticket

If I need to escalate to the network team, I'd include:

A clear escalation saves the next person from repeating the same tests, and it usually gets the problem fixed faster.


Sources

  1. Microsoft Learn, "ipconfig": https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/ipconfig
  2. IETF RFC 3927, "Dynamic Configuration of IPv4 Link-Local Addresses": https://www.rfc-editor.org/rfc/rfc3927
  3. Microsoft Learn, "ping": https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/ping
  4. Microsoft Learn, "nslookup": https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/nslookup
  5. Microsoft Learn, "tracert": https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/tracert
  6. Microsoft Learn, "Test-NetConnection": https://learn.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection

I'm Rıza Korkusuz, an IT support professional in San Diego. I write these notes to organize what I'm learning about desktop and service desk work. More at rizakorkusuz.com/it-support and github.com/rizakorkusuz.