NAT'ing to a different subnet

[bluedragon2]

I have the following configuration:

NAT Router with 2 ethernet interfaces:
123.5.5.5
124.5.5.5
I use the NAT Router to translate 123 addresses to 124 addresses which works fine.

I have a router on the 124 subnet that has a serial route to another router that has a 125 subnet.

From servers on the 124 subnet, I can access servers on the 125 subnet.

I put an IP Route on the NAT router as follows:

IP ROUTE 125.5.5.0 124.5.5.50 (which is the ethernet ip of the 124 router)

From the NAT router, I can ping the 125 subnet.

I put in a translation for a 123 address to a 124 address and it works fine.

I put a translation fron the 123 subnet to the 125 subnet and I can not access the NAT'ed address from the 123 subnet.

On the NAT router, I can ping the 125 address but when I try to ping the 123 translated address, I have no success.

The 123 ethernet on the NAT had ip NAT outside in the configuration and the 124 ethernet has ip NAT inside.

Is there something else I need to add for this to work, or can this be done?

Thanks



[Blue]Blue[/Blue] [Dragon]

If I wasn't Blue, I would just be a Dragon...

 

[rudeboy]

Does the router that sits betweend the 124 and 125 subnets have a route back to the 123 subnet? If you are able to ping the 125 subnet from the NAT router using the default ping, then you are pinging from the 124.5.5.5 address. You could try doing an extended ping.

 

[bluedragon2]

The route between the 124 and 125 router is through the serial interface and there is a route statement present. I have servers on the 124 network that can access the servers on the 123 network with no problem. When I ping from the NAT router, I am successful when I ping the 123 subnet, but when I ping the translated 123 address, it does not work. I believe the trouble is within the NAT config (and I am not even sure if you can NAT to two different subnets).

[Blue]Blue[/Blue] [Dragon]

If I wasn't Blue, I would just be a Dragon...