Why does this route not work ?

I am managing a Windows 2003 Server with two ethernet interfaces. One is
connected to the Internet (call it 217.218.219.220/25) and is configured with
a default gateway (217.218.219.129). Internet connectivity works fine.

The other interface connects to a private network (10.11.13.0/24). There
are hosts on the private network (10.11.12.0/24) that are on the other side
of a router (10.11.13.1,10.11.12.1). I can connect to 10.11.13.1 just fine
but cannot figure out a way to get to 10.11.12.1.

My routing table starts like this:

<pre>
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 217.218.219.129 217.218.219.220 10
10.11.13.0 255.255.255.0 10.11.13.2 10.11.13.2 10
10.11.13.2 255.255.255.255 127.0.0.1 127.0.0.1 10
10.255.255.255 255.255.255.255 10.11.13.2 10.11.13.2 10
217.218.219.128 255.255.255.128 217.218.219.220 217.218.219.220 10
217.218.219.220 255.255.255.255 127.0.0.1 127.0.0.1 10
64.255.255.255 255.255.255.255 217.218.219.220 217.218.219.220 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 10.11.13.2 10.11.13.2 10
224.0.0.0 240.0.0.0 217.218.219.220 217.218.219.220 10
255.255.255.255 255.255.255.255 10.11.13.2 10.11.13.2 1
255.255.255.255 255.255.255.255 217.218.219.220 217.218.219.220 1
Default Gateway: 217.218.219.129
</pre>

Before adding any static routes, I cannot get to 10.11.12.1:

>tracert -d 10.11.12.1
Tracing route to 10.11.12.1 over a maximum of 30 hops
1 3 ms <1 ms <1 ms 217.218.16.17
2 12.116.103.21 reports: Destination net unreachable.
Trace complete.

The problem is, the traceroute results do not change no matter what route I
add. I have tried the following (one at a time):

route add 10.11.12.0 mask 255.255.255.0 10.11.13.1
route add 10.11.0.0 mask 255.255.0.0 10.11.13.1
route add 10.0.0.0 mask 255.0.0.0 10.11.13.1

Any one of the routes above should work, but the stack does not seem to use
them even though the route command returns with no error and I see the route
listed in "route print" and "netstat -r" ...

Can anyone help me with this ?

"Gifford" <(E-Mail Removed)> wrote in message news:98BB0677-2BFB-4FF1-ACD5-(E-Mail Removed)...
>I am managing a Windows 2003 Server with two ethernet interfaces. One is
> connected to the Internet (call it 217.218.219.220/25) and is configured with
> a default gateway (217.218.219.129). Internet connectivity works fine.
>
> The other interface connects to a private network (10.11.13.0/24). There
> are hosts on the private network (10.11.12.0/24) that are on the other side
> of a router (10.11.13.1,10.11.12.1). I can connect to 10.11.13.1 just fine
> but cannot figure out a way to get to 10.11.12.1.
>
> My routing table starts like this:
>
> <pre>
> Active Routes:
> Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 217.218.219.129 217.218.219.220 10
> 10.11.13.0 255.255.255.0 10.11.13.2 10.11.13.2 10
> 10.11.13.2 255.255.255.255 127.0.0.1 127.0.0.1 10
> 10.255.255.255 255.255.255.255 10.11.13.2 10.11.13.2 10
> 217.218.219.128 255.255.255.128 217.218.219.220 217.218.219.220 10
> 217.218.219.220 255.255.255.255 127.0.0.1 127.0.0.1 10
> 64.255.255.255 255.255.255.255 217.218.219.220 217.218.219.220 10
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 224.0.0.0 240.0.0.0 10.11.13.2 10.11.13.2 10
> 224.0.0.0 240.0.0.0 217.218.219.220 217.218.219.220 10
> 255.255.255.255 255.255.255.255 10.11.13.2 10.11.13.2 1
> 255.255.255.255 255.255.255.255 217.218.219.220 217.218.219.220 1
> Default Gateway: 217.218.219.129
> </pre>
>
> Before adding any static routes, I cannot get to 10.11.12.1:
>
>>tracert -d 10.11.12.1
> Tracing route to 10.11.12.1 over a maximum of 30 hops
> 1 3 ms <1 ms <1 ms 217.218.16.17
> 2 12.116.103.21 reports: Destination net unreachable.
> Trace complete.
>
> The problem is, the traceroute results do not change no matter what route I
> add. I have tried the following (one at a time):
>
> route add 10.11.12.0 mask 255.255.255.0 10.11.13.1
> route add 10.11.0.0 mask 255.255.0.0 10.11.13.1
> route add 10.0.0.0 mask 255.0.0.0 10.11.13.1
>
> Any one of the routes above should work, but the stack does not seem to use
> them even though the route command returns with no error and I see the route
> listed in "route print" and "netstat -r" ...
>
> Can anyone help me with this ?


The first one, route add 10.11.12.0 mask 255.255.255.0 10.11.13.1 should work fine, provided the 10.11.13.0/24 side of that subnet is actually 10.11.13.1. Can you ping 10.11.13.1?

Use the -p to make it persistent, as the following shows, then restart the machine:

route add 10.11.12.0 mask 255.255.255.0 10.11.13.1 -p

Also make sure the internal subnet is the first in the binding order (under Network Connections window, Advanced, advanced).


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay

"Gifford" <(E-Mail Removed)> wrote in message news:98BB0677-2BFB-4FF1-ACD5-(E-Mail Removed)...

Also, add a metric to it, such as 10:

route add 10.11.12.0 mask 255.255.255.0 10.11.13.1 metric 10 -p

Ace

not specifying the metric gives it a metric of 1, which makes it as
preferable as it can be ...

"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "Gifford" <(E-Mail Removed)> wrote in message news:98BB0677-2BFB-4FF1-ACD5-(E-Mail Removed)...
>
> Also, add a metric to it, such as 10:
>
> route add 10.11.12.0 mask 255.255.255.0 10.11.13.1 metric 10 -p
>
> Ace
>
>
>

Thanks for the reply !

I agree that the first one (10.11.12.0) should work. Although I can
ping 10.11.13.1, the route that I added does not get used even after making
it persistent and rebooting. The tracert output remains as in my original
post.

I had never seen that binding-order dialog. Thanks for pointing out
something new ! Unfortunately, the adapter bound to the private network was
already at the top of the list.

Again, thanks for the response. The mystery remains, though ...

"Ace Fekay [Microsoft Certified Trainer]" wrote:

> The first one, route add 10.11.12.0 mask 255.255.255.0 10.11.13.1 should work fine, provided the 10.11.13.0/24 side of that subnet is actually 10.11.13.1. Can you ping 10.11.13.1?
>
> Use the -p to make it persistent, as the following shows, then restart the machine:
>
> route add 10.11.12.0 mask 255.255.255.0 10.11.13.1 -p
>
> Also make sure the internal subnet is the first in the binding order (under Network Connections window, Advanced, advanced).
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
> Microsoft Certified Trainer
> (E-Mail Removed)
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> "Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
> http://twitter.com/acefekay
>
>

"Gifford" <(E-Mail Removed)> wrote in message news:5BDA88FC-4BA1-4A3A-8726-(E-Mail Removed)...
> not specifying the metric gives it a metric of 1, which makes it as
> preferable as it can be ...

Curious, the routing table appears to say that the 10.11.13.0 subnet has a gateway of 10.11.13.2. Do both interfaces have a gateway specified? Can you post an unedited ipconfig /all please?

Ace

In news:5BDA88FC-4BA1-4A3A-8726-(E-Mail Removed),
Gifford <(E-Mail Removed)>, posted the following:
>> not specifying the metric gives it a metric of 1, which makes it as
>> preferable as it can be ...
>
> Curious, the routing table appears to say that the 10.11.13.0 subnet
> has a gateway of 10.11.13.2. Do both interfaces have a gateway
> specified? Can you post an unedited ipconfig /all please?
>
> Ace


Looks like there are three interfaces. I overlooked that. The ipconfig /all would be helpful to compare it to the routing table.

"Ace Fekay [Microsoft Certified Trainer]" <(E-Mail Removed)>
wrote in message news:(E-Mail Removed)...
In news:5BDA88FC-4BA1-4A3A-8726-(E-Mail Removed),
Gifford <(E-Mail Removed)>, posted the following:
>> not specifying the metric gives it a metric of 1, which makes it as
>> preferable as it can be ...
>
> Curious, the routing table appears to say that the 10.11.13.0 subnet
> has a gateway of 10.11.13.2. Do both interfaces have a gateway
> specified? Can you post an unedited ipconfig /all please?
>
> Ace


> Looks like there are three interfaces. I overlooked that. The ipconfig
> /all would be
> helpful to compare it to the routing table.

Hi guys,

He can already ping 10.11.13.1,..so the routing from the perspective of the
segment 10.11.12.0 already works. It works because the Router already knows
how to acknoledge the ping since it is a directly connected network (and
interface). However if pings to other devices beyond 10.11.13.1 fails, it
is because the "pinged host" on 10.11.13.0 does not know how to acknowledge
the ping. So you need to look on the 10.11.13.0 segment for routing
problems that are unique to that segment rather then global (global meaning
on the router itself).

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------