>I admit I like netsh.This thing can show you show much of what you want to see without doing much and that too from the command prompt which is even cooler.
What do you normally do when you want to see which DNS server you are using?
You use nslookup most of the times from command prompt or some other third part applications to do that,right?
Now,what do you do if you want to see which DHCP server you are using when you are having a dynamic IP on a LAN?
…We use netsh of course!
Here is how :
1.Go to command prompt in Windows XP.
2.Type the following – netsh diag show dhcp
I see the following stuff on my box when I do the above steps :
C:>netsh diag show dhcp
DHCP Servers
1. [00000001] AMD PCNET Family PCI Ethernet Adapter
DHCPServer = 10.0.2.2
Apart from the above command,there are other very very useful netsh diag show commands too like the test command which checks the network configuration settings in XP.I ran this command on my XP box and this is what I got :
C:>netsh diag show test
Default Outlook Express Mail (Not Configured)
Default Outlook Express News (Not Configured)
Internet Explorer Web Proxy (Not Configured)
Loopback (127.0.0.1)
Loopback = 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time Reply from 127.0.0.1: bytes=32 time=2ms TTL=2
Reply from 127.0.0.1: bytes=32 time Reply from 127.0.0.1: bytes=32 time Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms
Modems
Network Adapters ([00000001] AMD PCNET Family PCI Ethernet Adapter)
DefaultIPGateway = 10.0.2.2 Same Subnet
Pinging 10.0.2.2 with 32 bytes of data:
Reply from 10.0.2.2: bytes=32 time=2ms TTL=2
Reply from 10.0.2.2: bytes=32 time Reply from 10.0.2.2: bytes=32 time=1ms TTL=1
Reply from 10.0.2.2: bytes=32 time=4ms TTL=4
Ping statistics for 10.0.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 4ms, Average = 1ms
DHCPServer = 10.0.2.2
Pinging 10.0.2.2 with 32 bytes of data:
Reply from 10.0.2.2: bytes=32 time=1ms TTL=1
Reply from 10.0.2.2: bytes=32 time=6ms TTL=6
Reply from 10.0.2.2: bytes=32 time=2ms TTL=2
Reply from 10.0.2.2: bytes=32 time=3ms TTL=3
Ping statistics for 10.0.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 6ms, Average = 3ms
DNSServerSearchOrder = 10.0.2.3
Pinging 10.0.2.3 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.0.2.3:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
IPAddress = 10.0.2.15
Pinging 10.0.2.15 with 32 bytes of data:
Reply from 10.0.2.15: bytes=32 time Reply from 10.0.2.15: bytes=32 time Reply from 10.0.2.15: bytes=32 time=1ms TTL=1
Reply from 10.0.2.15: bytes=32 time Ping statistics for 10.0.2.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
Feel free to test the wonderful world of netsh on your Windows XP machine and you will surely come up with something useful,plus it looks way too cool when you do your thing from command prompt 🙂
Hope this has been an informative post.
Peace.