Routing Assistance

I am a bit rusting on my routing tables and could use some assistance please.

I have a Server 2008R with primary interface and default gateway of (NetGear Internet Router). I have just added a second interface (not registering with DNS) with IP of, MS Client and File/Printer sharing are not bound to this interface.

I have created a new DHPC scope for the network. I have connected a Wireless AP for guest access directly connected to this interface. I can connect to the AP, and get an IP Address but I cannot get to the internet, nor can I ping

From the server I tried a ping -S which failed, source address of is successful. Seems to be a routing issue.

I have (RRAS) routing Role installed and enabled.

Here is the routing table from the server.

IPv4 Route Table
Active Routes:Network Destination Netmask Gateway Interface Metric 266 On-link 266 On-link 266 On-link 266 On-link 306 On-link 306 On-link 306 On-link 266 On-link 266 On-link 266 On-link 306 On-link 266 On-link 266 On-link 306 On-link 266 On-link 266
Persistent Routes:Network Address Netmask Gateway Address Metric Default

Thanks for any assistance

Assuming it's a consumer grade Netgear router, I find it hard to believe you could setup these commands. Therefore, the few mouse clicks to enable NAT on the server seemed the easiest way.

What is default gateway on your AP - network?
To be able to ping anything in other networks you need to have reachable default gateway.

I can only guess, but maybe that should be

Clients definitely need to use as the gateway.

In the RRAS NAT config the 2nd NIC needs to be assigned as internal interface and the 1st NIC as the external facing interface (that way, no manual routing needs to be done)

Yes, Using as gateway on AP also set in DHCP scope options for that network.

RRAS NAT config? why do I need to NAT this, prefer to simply route it, primary router ( is firewall/NAT.


As you said, is the GATEWAY and HAS TO HAVE NAT functions enabled to route packets properly from the 10.20.30.x range to and from the internet.
If you think you can fool the systems in 10.20.30.x range that passes traffic through to magically, you're mistaken. NAT is the function to pass it through.
Even if you hacked the system into routing it directly (or even changing the gateway IP on those clients to, the next problem is that the router won't understand one bit of what's going on (WTF do I do with these 10.20.30.x packets?) and traffic doesn't flow back at all.
No matter how you route it, it will break, and you won't get ONE BIT from the internet.
You are confusing the route command (Windows cmd: route add) with the router functions (NAT).

If I understood that you added network directly to server (not to router), then actually, NAT is not needed, but what is really needed is that you show next device in line (routing device) where to send packets for network As long as packets are not intended for internet usually there in no need for NAT.
You need to set that will point to your server as next hop for network (or turn on RIP on ruter and server). At this point packets are coming to default gateway, but default gateway has no idea where network is.
Usually this is done by command
ip route
or you have some graphic tool to add static route (depending on router).
Router only can forward packets to destination that it can find in routing table. Currently the only matching route is probably default route so all packets for are going to internet.

If I did not understand your configuration well, can you post topology? :)

Share this

Related Posts

There was an error in this gadget