I’m disappointed.  When I typed “ping” I expected it to try 0.0.0.0.


*From:* [email protected] [mailto:
[email protected]] *On Behalf Of *Crawford, Scott
*Sent:* Wednesday, September 17, 2014 4:19 PM
*To:* [email protected]
*Subject:* [NTSysADM] Pinging with less than 3 octets



When pinging, you can leave out the 3rd octet and windows will pad the
address to fill the missing 3rd octet with 0. This also works if you leave
out the 2nd and 3rd. Heck, it even works without the 1st J



I’ve noticed this for quite a while, but have never seen it discussed. Can
anyone tell me why this works? Is it in a spec? Or, just an interesting
anomaly? I use it as a shortcut pretty often and just never bothered to
research it much.



C:\>ping 10.1.1

Pinging 10.1.0.1 with 32 bytes of data:



C:\>ping 10.1

Pinging 10.0.0.1 with 32 bytes of data:



C:\>ping 10

Pinging 0.0.0.10 with 32 bytes of data:

Reply via email to