Windows Command Line Basics for Help Desk Beginners

The Windows command line helps support technicians gather information quickly. You do not need to know every command to start. Learn a few safe commands and understand when to use them.

ipconfig

Use ipconfig to check IP address, subnet mask, and default gateway.

Use ipconfig /all when you need more detail, such as DNS servers, DHCP status, and adapter information.

ping

Use ping to test whether a device responds over the network.

Examples:

• Ping the default gateway to test local network reachability.
• Ping a known internal server if your workplace allows it.
• Ping a public IP only if that is acceptable in your environment.

Ping can be blocked by firewalls, so a failed ping is a clue, not final proof.

tracert

Use tracert to see the path traffic takes to a destination. It can help show where traffic stops.

This is useful for network troubleshooting, but beginners should avoid over-reading it. Some routers do not respond to trace requests.

nslookup

Use nslookup to test DNS name resolution.

If you can ping an IP address but websites do not load by name, nslookup can help confirm whether DNS is part of the issue.

sfc /scannow

Use sfc /scannow to scan protected Windows system files and attempt repairs.

This can help when Windows components behave strangely, but it is not a magic fix for every issue. Run it from an elevated command prompt when appropriate.

chkdsk

Use chkdsk to check a disk for file system errors.

Be careful with repair options on systems with possible drive failure. Confirm backup status and follow workplace policy before running commands that can modify disk data.

shutdown commands

The shutdown command can restart or shut down Windows from the command line.

Examples:

• shutdown /r /t 0 restarts immediately.
• shutdown /s /t 0 shuts down immediately.
• shutdown /a cancels a pending shutdown if there is time.

Use these only when the user is ready. Restarting without warning can cause lost work.

When to use each command safely

Use information-gathering commands first: ipconfig, ping, tracert, and nslookup.

Use repair or restart commands more carefully: sfc /scannow, chkdsk, and shutdown.

Beginner-friendly rule: commands that only show information are safer than commands that change the system. Cantonese-friendly: “先睇資料，唔好一開始就改設定.”

Beginner Note

Write down what you ran and what result you got. Good command-line troubleshooting is not just typing commands. It is documenting evidence.

Common Mistake

A common mistake is running commands without understanding the goal. Before typing, ask: what am I testing?

Help desk example

A user says the internet is down. You run ipconfig, see a valid IP and gateway, ping the gateway successfully, then use nslookup and find DNS is failing. That gives you a much clearer ticket note.

FAQ

Do I need Command Prompt or PowerShell?

Many basic commands work in both. Beginners can start with Command Prompt and learn PowerShell over time.

Should I run every command as administrator?

No. Only use elevated permissions when needed. Higher permissions can make bigger changes.

Is ping always reliable?

No. Firewalls can block ping. Use it as one clue among several.

Can chkdsk cause problems?

Repair options can modify disk data. Confirm backups and follow policy before running repair commands on important systems.