Top Basic Command Prompts Every IT Professional Should Know


Computer screen displaying Windows Command Prompt with common IT troubleshooting commands like ping and tracert

Introduction

In the field of IT, mastering the Command Prompt (CMD) is a must. It’s a lightweight, powerful tool for diagnosing network issues, managing processes, and executing system-level tasks. This guide covers the most essential command prompt commands every IT support professional or network admin should know—with IP address examples included for clarity.

🔗 Related Post: How to Troubleshoot Network Issues in HotelsTop 5 Windows Problems in Hotels & Easy Fixes (2025 Guide)


1. ipconfig Check IP Address and Network Info

Usage:

ipconfig

Example Output:

IPv4 Address. . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0  
Default Gateway . . . . . . . . . : 192.168.1.1

Why it’s useful:
Shows your PC’s current IP configuration, helping you verify network setup or resolve connectivity issues.

📘 Learn more: Microsoft Official Docs – ipconfig


2. ping – Test Network Connection

Usage:

ping 8.8.8.8

Why it’s useful:
Tests if your system can reach another device or server.
In this example, 8.8.8.8 is Google’s public DNS server, commonly used for connectivity testing.

Sample Output:

Reply from 8.8.8.8: bytes=32 time=15ms TTL=117

3. tracert – Trace Route to Destination

Usage:

tracert 8.8.8.8

Why it’s useful:
Displays each hop (router) your packet travels through to reach the destination IP. Useful to diagnose where delays occur.

Sample Output:

1    <1 ms    <1 ms    <1 ms  192.168.1.1  
2     5 ms     6 ms     5 ms  100.64.0.1  
3    10 ms    10 ms    11 ms  8.8.8.8

4. netstat – View Network Connections

Usage:

netstat -an

Why it’s useful:
Shows active network connections and listening ports.

Sample Output:

TCP    192.168.1.101:56789   93.184.216.34:443   ESTABLISHED
TCP    192.168.1.101:56790   8.8.8.8:53          TIME_WAIT

Here, 192.168.1.101 is your local IP, and 8.8.8.8 or 93.184.216.34 are remote hosts.


5. tasklist – List Running Processes

Usage:

tasklist

Why it’s useful:
Displays all running processes. While no IPS are involved directly, it helps identify resource heavy or suspicious tasks tied to network activity.


6. taskkill – Terminate a Process

Usage:

taskkill /IM chrome.exe /F

Why it’s useful:
Closes unresponsive applications. Useful when a process is stuck during a remote support session—especially if it’s using an open network connection like a browser.


7. chkdsk – Check Disk Health

Usage:

chkdsk C:

Why it’s useful:
Scans the drive for file system errors—while not related to IP, it’s crucial for maintaining systems that host network services.


8. sfc /scannow – Scan and Fix System Files

Usage:

sfc /scannow

Why it’s useful:
Fixes corrupt system files that may be causing network or application crashes. Again, no direct IP use, but very useful in broader IT health checks.


9. shutdown – Restart or Shut Down a Remote Computer

Usage (local):

shutdown /r /t 0

Usage (remote with IP):

shutdown /m \\192.168.1.105 /r /t 0

Why it’s useful:
Allows you to remotely restart a system via IP. Replace 192.168.1.105 with the actual IP of the target computer on your network.


10. cls – Clear the Screen

Usage:

cls

Why it’s useful:
Clears the clutter from the command window—useful during step-by-step troubleshooting or training sessions.


Conclusion

These basic command prompt commands—enhanced with real IP examples—are powerful tools in an IT professional’s arsenal. Whether you’re managing a single machine or an enterprise network, mastering CMD improves speed, efficiency, and control over IT environments.




Comments

Leave a Reply

Your email address will not be published. Required fields are marked *