Hi All, I have a problem that has been driving me insane. Basically I have a server 2003 box on an ip of 10.0.0.10 that I am trying to connect to a different lan segment. I have another server 2003 box running rras acting as a router with 2 network cards. One nic address is 10.0.0.2 and the second nic is 192.168.0.10. There is a netgear router on the 192.168.0.1 address and this provides the wan link for the lan. No matter what I have tried I cannot get the 10.0.0.10 box to connect to the netgear router or any other pc on the 192.168.0 network aside from the rras server. I can ping the external card (192.168.0.10) on the rras server and also the internal card (10.0.0.2) but cannot ping through to the other side. The rras box has connectivity to the internet. I have set the rras to configure the server as a router for lan and enabled rip v2. Have also set static routes for the 192.168.0.0 network aswell as 0.0.0.0 network but this hasnt helped. This is on both servers. Also I only have one gateway configured on the rras box. Any clues? If you need any more info, please do let me know.

So I guess, the server 2003 with 2 NICs, that is also acting as a router between 10.0.0.x and 192.168.0.x, has 2 standard gateways. One of the standard gateways directs to the wan router and the other directs to the 192.168.0.x network. So what should be done, if a client asks for e.g. google.com? Should it be routed to the wan router or to the 192.168.0.x network. The server does not know what to do, because there are 2 standard gateways. What I wonna tell you is, it's always a problem to have 2 standard gateways at the same server. You have to have one standard gateway to the router and a static routing to the 192.168.0.x to get it to run.

Thanks for the reply. In actual fact the server 2003 which is acting as a router only has a single gateway pointing towards the 192.168.0.1 gateway address. If there were two gateways, then there would be routing problems as you are aware. The server running as a router is also configured with DNS so all resolution is being provided for the 10.0.0.0 network within their own segment. In the event it is unable to resolve the dns, it is forwarding on to the ISP's nameservers. As it happens I managed to divine my own solution at around 2am this morning. Just in case this helps anyone else, I needed to put a static route pointing back to the 10.0.0.0 network on the router on the 192.168.0.1 address as the router did not know where to send the traffic back to. All very profound really as I cant understand why pinging the 192.168.0.10 address worked but pinging an address of 192.168.0.100 which was on the same switch did not. I would not have thought the 192.168.0.1 router would have been involved at all. Anyhows, thanks for the response but a solution has been arrived upon!!!