RRAS routeing

[jrwinterburn]

Hi All,

I managed to achieve this a couple of years ago on another network, but cannot seem to do it now.

I have a network on the 99.99.99.0/24 range (I inherited this network with this illegal range on it).

I want to migrate PC's over to 192.168.0.0/20.

I have a Cisco Pix as the default gateway (99.99.99.245). I have now installed a Windows Server 2003 RRAS server (which happens to also be a DNS/WINS server). This has:

NIC #1: 99.99.99.230
NIC #2: 192.168.0.1

It is configured as a LAN router. The 192.168 NIC has no gateway. Netbios over TCP/IP is disabled for this NIC.

I have added the following static route to the Pix:
route inside 192.168.0.0 255.255.0.0 99.99.99.230

However, if I change the IP of a PC to be on the 192.168 range, it can only ping 99.99.99.230 (the IP of the RRAS) but no other IP's on the 99.x range. Equally, no PC's on the 99.x range can ping the 192.168 range.

What am I missing?

Thanks

Jon

 

[Roadki11]

I think your pix routing is wrong, you are pushing all 192.168 traffic to 99.99.99.230 which is why it is the only address in the 99.99 network that will respond to the pings. Conversely you have no route statement for the 99.99 network which is why no 99.99 pc's can ping the 192.168 network.

RoadKi11

 

[jrwinterburn]

The reason why I am pushing all the 192.168 traffic to 99.99.99.230 is because the Pix (99.99.99.245) cannot route from that subnet, so instead, it pushes the traffic to the RRAS server (99.99.99.230) which should then route between the 2 subnets.