A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Problem pinging IPs with 3 digits in all octets



 
 
Thread Tools Display Modes
  #1  
Old February 13th 09, 03:11 PM posted to microsoft.public.windowsxp.network_web
Allyn
external usenet poster
 
Posts: 7
Default Problem pinging IPs with 3 digits in all octets

I'm dealing with a vendor that claims his application requires Windows to
handle 3 digits in all octets of the IP address, and consequently this is the
reason his application is not working. I've tried the following on multiple
machines, from Windows 2000 to Windows 2008. They all respond the same.

========
C:\Documents and Settings\ABaskervilleping 192.168.001.025

Pinging 192.168.1.21 with 32 bytes of data:

Reply from 192.168.1.21: bytes=32 time=13ms TTL=59
....
========
C:\Documents and Settings\ABaskervilleping 172.016.002.001

Pinging 172.14.2.1 with 32 bytes of data:

Request timed out.
....
========
C:\Documents and Settings\ABaskervilleping 010.025.100.001

Pinging 8.21.100.1 with 32 bytes of data:
Request timed out.
....
========

I did a packet capture, and the packets are leaving all Windows systems with
the incorrect IP address. That is, the ARP requests are not correct initially.

For whatever reason, the vendor is able to get the systems to ping properly,
but I have access to several networks and none work.

I'm very curious if this is widespread and if anyone has an explanation. I'd
say the leading 0's should not impact anything, so to me I'd rate is as a
noncritical Windows network bug.

Thank you.
Ads
  #2  
Old February 13th 09, 09:02 PM posted to microsoft.public.windowsxp.network_web
Michael W. Ryder
external usenet poster
 
Posts: 265
Default Problem pinging IPs with 3 digits in all octets

Allyn wrote:
I'm dealing with a vendor that claims his application requires Windows to
handle 3 digits in all octets of the IP address, and consequently this is the
reason his application is not working. I've tried the following on multiple
machines, from Windows 2000 to Windows 2008. They all respond the same.

========
C:\Documents and Settings\ABaskervilleping 192.168.001.025

Pinging 192.168.1.21 with 32 bytes of data:

Reply from 192.168.1.21: bytes=32 time=13ms TTL=59
...
========
C:\Documents and Settings\ABaskervilleping 172.016.002.001

Pinging 172.14.2.1 with 32 bytes of data:

Request timed out.
...
========
C:\Documents and Settings\ABaskervilleping 010.025.100.001

Pinging 8.21.100.1 with 32 bytes of data:
Request timed out.
...
========

I did a packet capture, and the packets are leaving all Windows systems with
the incorrect IP address. That is, the ARP requests are not correct initially.

For whatever reason, the vendor is able to get the systems to ping properly,
but I have access to several networks and none work.

I'm very curious if this is widespread and if anyone has an explanation. I'd
say the leading 0's should not impact anything, so to me I'd rate is as a
noncritical Windows network bug.

Thank you.


If you look at the output of the ping command you can see one of your
problems. Putting a leading zero in a number tells ping that the number
is an octal number so 016 is treated as 016 octal or 14 decimal. If you
converted your addresses to octal before entering them in ping this may
fix part of your problem -- i.e. 16 decimal is 020 octal.
  #3  
Old February 13th 09, 09:02 PM posted to microsoft.public.windowsxp.network_web
Michael W. Ryder
external usenet poster
 
Posts: 265
Default Problem pinging IPs with 3 digits in all octets

Allyn wrote:
I'm dealing with a vendor that claims his application requires Windows to
handle 3 digits in all octets of the IP address, and consequently this is the
reason his application is not working. I've tried the following on multiple
machines, from Windows 2000 to Windows 2008. They all respond the same.

========
C:\Documents and Settings\ABaskervilleping 192.168.001.025

Pinging 192.168.1.21 with 32 bytes of data:

Reply from 192.168.1.21: bytes=32 time=13ms TTL=59
...
========
C:\Documents and Settings\ABaskervilleping 172.016.002.001

Pinging 172.14.2.1 with 32 bytes of data:

Request timed out.
...
========
C:\Documents and Settings\ABaskervilleping 010.025.100.001

Pinging 8.21.100.1 with 32 bytes of data:
Request timed out.
...
========

I did a packet capture, and the packets are leaving all Windows systems with
the incorrect IP address. That is, the ARP requests are not correct initially.

For whatever reason, the vendor is able to get the systems to ping properly,
but I have access to several networks and none work.

I'm very curious if this is widespread and if anyone has an explanation. I'd
say the leading 0's should not impact anything, so to me I'd rate is as a
noncritical Windows network bug.

Thank you.


If you look at the output of the ping command you can see one of your
problems. Putting a leading zero in a number tells ping that the number
is an octal number so 016 is treated as 016 octal or 14 decimal. If you
converted your addresses to octal before entering them in ping this may
fix part of your problem -- i.e. 16 decimal is 020 octal.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 04:11 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.