Strange ping behaviour

Hi all
A somewhat weird one I can't quite put my finger on
We have a heap of stores connected back to my LAN via a managed
service thru our ISP WAN
All these stores connect into the ISP's network on a 10.0.0.0 subnet
The stores use an IP addressing scheme made up of the store number
For example if the store's number is 3130 the IP subnet will be
10.31.30.0
I have some stores like 2108, where the IP subnet is 10.21.8.0
If I ping the server at the store on 10.21.8.100 no problems

ping 10.21.8.100

Pinging 10.21.8.100 with 32 bytes of data:

Reply from 10.21.8.100: bytes=32 time=102ms TTL=57
Reply from 10.21.8.100: bytes=32 time=106ms TTL=57

If I try and ping the store using say 10.21.08.100 (don't ask!!) I get
the following

ping 10.21.08.100

Pinging 10.21.08.100.com.au [82.98.86.180] with 32 bytes of data:

Request timed out.
Request timed out.

As you can see it is trying to resolve it to some outside address

In my LAN I have 2 subnets, 192.168.26.0 which is the W/S's and a
192.168.100.0 which are the servers
From the Domain controller that is the primary DNS server for all W/
S's (DC01) on the 192.168.26.0 subnet I can ping both 10.21.8.100 and
10.21.08.100, from the other DC (DC02) I get the same problems as
above
DC01 has DC02 as the primary DNS server and itself as the second DNS
server
DC02 has DC01 as the primary DNS server and itself as the 2nd
All DNS Zone are AD integrated, secure etc
To me it seems that the problem is related to DC01
From another server (AD/DNS) that uses itself and DC02 as it's DNS
servers no issues
DC01 is the only server set to forward DNS requests to the internet
for net access for the users

Anyone have any ideas?

Scott

That is correct. If you add a leading zero the number will not be
accepted. It is trying to resolve it as if it was a name.

If you had a store 2106 it would probably work. The leading zero is
interpreted as a flag to indicate the number is octal, not decimal. Eight is
not a valid octal number.

http://h71000.www7.hp.com/wizard/wiz_6425.html

"Scooty" <(E-Mail Removed)> wrote in message
news:6b06ae52-0464-4b58-a410-(E-Mail Removed)...
> Hi all
> A somewhat weird one I can't quite put my finger on
> We have a heap of stores connected back to my LAN via a managed
> service thru our ISP WAN
> All these stores connect into the ISP's network on a 10.0.0.0 subnet
> The stores use an IP addressing scheme made up of the store number
> For example if the store's number is 3130 the IP subnet will be
> 10.31.30.0
> I have some stores like 2108, where the IP subnet is 10.21.8.0
> If I ping the server at the store on 10.21.8.100 no problems
>
> ping 10.21.8.100
>
> Pinging 10.21.8.100 with 32 bytes of data:
>
> Reply from 10.21.8.100: bytes=32 time=102ms TTL=57
> Reply from 10.21.8.100: bytes=32 time=106ms TTL=57
>
> If I try and ping the store using say 10.21.08.100 (don't ask!!) I get
> the following
>
> ping 10.21.08.100
>
> Pinging 10.21.08.100.com.au [82.98.86.180] with 32 bytes of data:
>
> Request timed out.
> Request timed out.
>
> As you can see it is trying to resolve it to some outside address
>
> In my LAN I have 2 subnets, 192.168.26.0 which is the W/S's and a
> 192.168.100.0 which are the servers
> From the Domain controller that is the primary DNS server for all W/
> S's (DC01) on the 192.168.26.0 subnet I can ping both 10.21.8.100 and
> 10.21.08.100, from the other DC (DC02) I get the same problems as
> above
> DC01 has DC02 as the primary DNS server and itself as the second DNS
> server
> DC02 has DC01 as the primary DNS server and itself as the 2nd
> All DNS Zone are AD integrated, secure etc
> To me it seems that the problem is related to DC01
> From another server (AD/DNS) that uses itself and DC02 as it's DNS
> servers no issues
> DC01 is the only server set to forward DNS requests to the internet
> for net access for the users
>
> Anyone have any ideas?
>
> Scott