How can I configure my Windows 2003 DC machine to act as a router?

Discussion in 'Windows Networking' started by john, Mar 13, 2006.

  1. john

    john Guest

    I have two different networks: network A (10.10.10.0/24) and network B
    (172.16.0.0/12). I would like to configure a DC (Windows 2003 Server) of
    network B as a router.

    There are two network interfaces on Windows 2003 Server. One of them has
    ip=172.16.0.2/12, gateway=172.16.0.1. I defined the other's ip as
    10.10.10.200/24 and gateway as 10.10.10.250 (this one is connected to network
    A).

    I changed the registry value of Windows 2003 Server as:

    HKLM\System\Currentcontrolset\Services\TCPIP\Parameters\Ipenablerouter=1

    I ran routing commands from the command prompt:

    route add -p 10.10.10.0 mask 255.255.255.0 10.10.10.200

    Now I am able to ping Windows 2003 Server from a client machine on network
    A, after running <route add -p 172.16.0.0 mask 255.240.0.0 10.10.10.200>
    command.

    However, I can not ping any other machine on network B from network A. What
    else should I configure? Do I need to reboot Windows 2003 Server?

    Also, do I have to run routing command on all client machines? Is it
    possible just to define two gateways (one is Windows 2003 Server's related
    network interfaces ip adress, the other is the default gateway of the
    network) on one ip on the client machines of both networks?

    Could anyone help me on this subject?
     
    john, Mar 13, 2006
    #1
    1. Advertisements

  2. Try:

    1. Get rid of one of the the default gateways on the Windows Server 2003
    machine. This isn't the cause of your problem, but it may cause others.

    2. Get rid of this route: "route add -p 10.10.10.0 mask 255.255.255.0
    10.10.10.200" - it doesn't serve any purpose.

    3. On subnet A either configure machines with a default gateway of
    10.10.10.200, or:

    route -p add 172.16.0.0 mask 255.240.0.0 10.10.10.200

    3. On subnet B either configure machines with a default gateway of
    172.16.0.2 or:

    route -p add 10.10.10.0 mask 255.255.255.0 172.16.0.2

    Doug Sherman
    MCSE, MCSA, MCP+I, MVP
     
    Doug Sherman [MVP], Mar 13, 2006
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.