You can't add 0 to the front of an ip and as far as I know you never could. As soon as you add the zero the computer interprets the number wrong.
Main Topics
Browse All TopicsFor a while now I have been noticing that when I use VNC I was getting the wrong computer on my network when I typed an IP address. An example would be 192.168.1.040 would get me 192.168.1.32 instead of the .40 workstation). This also was occurring when pinging from CMD.
This was getting progressively worse and now I notice it is always happening with 2 digit octets. I thought this might be due to something in my cache, my DNS server, host files, router or something of that sort. However I was unable to pin the cause down in any of those.
I have come to find out that whenever you type a .040 it is actually the octal form of that number which is 32.
My question is, when did this happen? I've been typing in 3 digit octets since I can remember. This is due to the fact that a lot of earlier devices "back in the day" required all 3 spaces to be populated by a whole number and was considered incomplete without all 3 digits in that octet. This just became habit for me to use a zero even if it was a 2 digit octet.
I have tried this on Windows PC's with Vista, XP, and 2K, both on my domain and off. See these resolved examples below:
Ping 192.168.1.007 = Pining 192.168.1.7
Ping 192.168.1.008 = Pining 192.168.1.8
Ping 192.168.1.009 = Pining 192.168.1.9
Ping 192.168.1.010 = Pining 192.168.1.8
Ping 192.168.1.011 = Pining 192.168.1.9
etc.....
Again. when did this happen? Did some MS service pack ninja come in at 3 AM and demand that IP addresses be resolved in this manner? Or has it always been like this and perhaps it was autocorrected for me somehow? This really bothers me. I'd hate to think that it's always been like this and it's taken me 12 years to find out that Microsoft has been doing this all along. Then again, I have more pressing issues on my mind. :)
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Well, it does the same thing here, so it must be "normal". Looks like it's interpreting it (logically enough) in octal - i.e., 010=8, 011=0, etc. I have never been in the habit of adding an extra "0" to the last octet, so I can't say I've ever noticed this before. I did find this knowledgebase article on Technet, which seems to apply to every OS since Windows for Workgroups :-)
http://support.microsoft.c
Truthfully, I've never used leading zeroes in an IP address octet before. But seriously . . . who really uses octal anymore?? And if it is deliberately programmed to accept a leading zero as an octal number, then by that logic you should also be able to type C0.A8.01.10 for an IP address, but you can't.
No, I know the difference. What I am saying is that it's just plain stupid to interpret a leading zero as an octal number in a dialog box. First off, nobody uses an octal number in a x.x.x.x field, and second, if they did, how would the dialog differentiate between decimal and octal number if it was 3 digits long (no room for a leading zero)?
It's a bug. Has to be. There'd be no reason to deliberately program a "feature" like that in.
Well, I'm not arguing with you on that - all I said was that it was normal as far as I knew, and I found documentation to support that. I'm not arguing one way or the other as to whether it is or isn't a good thing - that is often in the eye of the beholder anyway, and I don't find such arguments to be productive, since it's not going to change anything or help resolve the question for the OP.
According to Microsoft, this is a part of the OS....see the below page, but it looks like you are seeing this in Vista also?
http://support.microsoft.c
Hypercat was the first to post that KB article, "Ping and FTP Resolve IP Address with Leading Zero as Octal." Not only did it name the term and explain what was happening, as our guy Andrew suspected, an octal translation. It also points out that this has been going on since at least 1993 as the examples are from:
Windows NT 3.1:
and
Windows NT 3.5:
c:\>ping 022.101.31.153
Pinging 18.101.31.153 with 32 bytes of data:
Ping succeeded: 32 bytes time=10ms TTL=32
I'm embarrassed that I have not noticed this in the 10 years I've been doing this.
Just like "from exp" stated, there are a myriad of other servers, web appliances, devices, controllers, wifi products and printers that have always required me to enter that leading zero, and that's just what I got in the habit of doing.
Ive always tended to put PC's in the .100 to .254 range and other devices and routers from .001 to .099. (Thats just a weird preference of mine to assign certain ranges of IPs to devices in order to remember users, extensions, departments and/or locations.) In hindsight I believe that due to my personal preferences, I rarely used remote access for any device under the .100 range. However, recently my network is exploding. Damn near everything is requiring an IP these days I am forced to put many IP's below .100. Now that I am required to remote using a leading zero sub .100 (.001 to .099) PCs more often, I must be just noticing it. Looks like its getting time to move everything to a network class B real soon.
Thanks to everyone that posted.
Business Accounts
Answer for Membership
by: cuziyqPosted on 2008-01-04 at 13:18:42ID: 20586203
Wow . . . what an obscure little bug -- and that's exactly what it is: a bug. .007 and .7 *should* resolve to the same thing, even in binary.