Help with Route Add?

[Kooldino]

So I'm having some trouble adding a route here...can anyone tell me why I'm getting the error message that I'm getting when I try to add the route? I included ipconfig info as well as the route table.

C:\>route ADD 192.168.61.0 MASK 255.255.255.0 172.26.75.239
The route addition failed: Either the interface index is wrong or the gateway do
es not lie on the same network as the interface. Check the IP Address Table for
the machine.

-----------------------------------------------------------

C:\>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : CT14_1_Prv.act.faa.gov
IP Address. . . . . . . . . . . . : 172.26.72.68
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.26.72.1

-----------------------------------------------------------

C:\>route print
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 12 3f 57 7b 59 ...... Broadcom NetXtreme 57xx Gigabit Controller - Pac
ket Scheduler Miniport
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.26.72.1 172.26.72.68 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.26.72.0 255.255.255.0 172.26.72.68 172.26.72.68 30
172.26.72.68 255.255.255.255 127.0.0.1 127.0.0.1 30
172.26.75.0 255.255.255.0 172.26.72.1 172.26.72.68 1
172.26.255.255 255.255.255.255 172.26.72.68 172.26.72.68 30
224.0.0.0 240.0.0.0 172.26.72.68 172.26.72.68 30
255.255.255.255 255.255.255.255 172.26.72.68 172.26.72.68 1
Default Gateway: 172.26.72.1
================================================== =========================
Persistent Routes:
None

[Wombat]

Because you can't get to your gateway from your current IP using the subnet mask you've specified.

You're trying to go from A.B.72.* to A.B.75.* with a a 255.255.255.0 mask.

[Jammrock]

Because you can't get to your gateway from your current IP using the subnet mask you've specified.

You're trying to go from A.B.72.* to A.B.75.* with a a 255.255.255.0 mask.

That should only a problem if the router does not support VLSM...or you use static routes.

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/route.mspx

Try using your local gateway instead of a remote one. Possibly build a route to the 172.26.75.0 network first, and then to the 192.168.61.0 network after.

[Wombat]

That should only a problem if the router does not support VLSM...or you use static routes.

I'm not familiar with VLSM, but I read the Wiki, and I can't see why it would be okay to route the way he does. VLSM seems to say that the subnet size can be varied, not violated.

[Kooldino]

Because you can't get to your gateway from your current IP using the subnet mask you've specified.

You're trying to go from A.B.72.* to A.B.75.* with a a 255.255.255.0 mask.

I thought about that and tried a 255.255.0.0, but that didn't take either.

[Kooldino]

Try using your local gateway instead of a remote one. Possibly build a route to the 172.26.75.0 network first, and then to the 192.168.61.0 network after.

I tried that...you can see it in the route table:
172.26.75.0 255.255.255.0 172.26.72.1 172.26.72.68 1

[Jammrock]

didn't catch that. guess I should pay more attention to the route table.

72 = 01001000
75 = 01001011

So in theory the subnet mask should be:

11111111.11111111.11111100.00000000 = 255.255.252.0

...in order to prevent a subnet conflict. Unless there are a significant number of additional subnets in the 172.16.y.z range. But I don't know the structure of your network so ...

Anyway, the thing that bugs me about the route is the 192.168.61.0 part. Is this supposed to be interface that connects to the Internet? Because it's completely different than the rest of the network structure, from what I've seen. Or are you trying to bridge to a different network segement?

[Kooldino]

didn't catch that. guess I should pay more attention to the route table.

72 = 01001000
75 = 01001011

So in theory the subnet mask should be:

11111111.11111111.11111100.00000000 = 255.255.252.0

Ok, I follow your logic here, but wouldn't putting 255.255.0.0 accomplish the same thing (although it's more "open" than your way?)

...in order to prevent a subnet conflict. Unless there are a significant number of additional subnets in the 172.16.y.z range. But I don't know the structure of your network so ...

You and me both.

Anyway, the thing that bugs me about the route is the 192.168.61.0 part. Is this supposed to be interface that connects to the Internet?

No, the 192.168.61.0 network is a stand alone group of computers in another room that I want this machine to access via another machine.

I should note that I'm on the 75.0 network, and the route add command works fine for me.

[Jammrock]

Ok, I follow your logic here, but wouldn't putting 255.255.0.0 accomplish the same thing (although it's more "open" than your way?)

...depends on the network.

No, the 192.168.61.0 network is a stand alone group of computers in another room that I want this machine to access via another machine.

I should note that I'm on the 75.0 network, and the route add command works fine for me.

Run a PATHPING and/or TRACERT, using an IP address of a computer on the network you want to reach, and post the results.

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/pathping.mspx

Jammrock