Windows Networking Commands
Windows Networking Commands
The fault-monitoring system should assist in isolating and diagnosing the fault. Examples
of tests that a fault-monitoring system should have at its command include a
• connectivity test
• data integrity test
• protocol integrity test
• data saturation test
• connection saturation test
• response-time test
• loopback test
• function test
• diagnostic test
Windows has some very useful networking utilities that are accessed
from a command line (cmd console).
The networking commands are mainly used for getting system information and troubleshooting
networking problems.
1. Ping Command
The ping command is one of the most often used networking utilities for detecting devices on a
network and for troubleshooting network problems.
When you ping a device you send that device a short message, which it then sends back (the
echo).
Example
2. ipconfig Command
Another indispensable and frequently used utility that is used for finding network information
about your local machine like IP addresses, DNS addresses etc
ipconfig /all – displays more information about the network setup on your systems including the
MAC address.
A very simple command that displays the host name of your machine. This is much quicker than
going to the control panel>system route.
4. getmac Command
Another very simple command that shows the MAC address of your network interfaces
5. arp Command
This is used for showing the address resolution cache. This command must be used with a
command line switch arp -a is the most common.
6. NSlookup
Used for checking DNS record entries. See Using NSlookup for more details
7. Nbtstat
Diagnostic tool for troubleshooting netBIOS problems. See This technet article.
8 Net Command
Used for managing users,service,shares etc see here
9. Netstat Command
Used for displaying information about tcp and udp connections and ports. See tcp and udp ports
and sockets and how to use the netstat command
View a list of running tasks using the tasklist command and kill them by name or processor ID
using the taskKill command- See this tutorial.