Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to configure a Windows 2003 server to act as a router, so that the two subnetworks that I'm dealing with can communicate with one another without NAT. I am mostly sure that I have configured Windows 2003 incorrectly, and I'm finding it very difficult to drill down through Google results to something helpful.

I have a network that is my "production" network (in the sense that I'm in trouble if I screw it up) and a network that is my test network. The network is ruled by a gateway whose routing table looks like this (my address redacted): gateway

The Windows 2003 server, "prime," is multihomed. Its network adapters are at, (as seen above),, and I added the Routing and Remote Access role to it, and enabled LAN routing. I do not have it using RIP or other routing protocols. Its current routing table is shown below.

windows 2003 server

To me, it looks like all of the right routes are there for traffic to pass between the network and the network. However, traffic does not pass. The and .12 clients cannot be contacted from the network. When I use traceroute to try to get to them, the trace gets to the Windows 2003 server's address, then produces nothing but "* * *" timeouts. When I try to traceroute to from a client, I get "destination host unreachable." However, I know that the routing is working at least a little, because from the network, I can connect to the Windows server just fine by referring to it as

What static routes would allow me to contact and .12 from the network?

Is it possible to tell the Windows server "since you are a DHCP/DNS server, you already know routes to get to machines that are getting IP addresses from you, please add those to your routing table" ?

Will using RIP or OSPF on the Windows server actually be helpful in this situation?

share|improve this question
up vote 3 down vote accepted

did you enabled routing on windows 2003? check here.

RIP / OSPF are helpful if you have larger network of devices that can handle those protocols.

share|improve this answer
+1 - routing may simply not be enabled yet ;) – TomTom Apr 29 '10 at 7:06
I've been sticking with the GUI tools for now, so I haven't made that registry edit. Trying that now. – Brighid McDonnell Apr 29 '10 at 12:59
Took a while to kick in, but that seems to have worked. Gosh, editing the Registry directly is so much more convenient than a GUI tool or a shell command. – Brighid McDonnell Apr 30 '10 at 1:13

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.