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

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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

"john" <john@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:300AC404-8A86-4529-91F4-AF85BB5DBA9A@xxxxxxxxxxxxxxxx
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?


.

Relevant Pages

  • Re: Windows XP; Windows 98 & Windows NT 4.0 compatability
    ... >3) ICF is DISABLED on the XP Machines ... >4) I'm not quite sure what you mean on file sharing. ... >obviously I can see the XP machines on the 98 Network ... Windows XP is the latest attempt to merge the Windows 9x product line ...
    (microsoft.public.windowsxp.network_web)
  • Re: Is a Windows 98se computer more, or less, of a security threat with IE 5.5 (unused) & Firefo
    ... We aren't using any Windows ME machines at all. ... That might be a better solution, however Windows 98 does not support ... He's very knowledgable about network security, ...
    (microsoft.public.windowsupdate)
  • Re: File sharing fails.
    ... Still no working network is obvious.. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.basics)
  • Re: paging all socket geniuses
    ... Windows, my laptop, or me or all three are... ... about the absence of a network... ... Ping was a nice courtesy of a tamer Internet of the past. ... machines and firewalls are configured to block all ICMP traffic (which ...
    (comp.lang.lisp)
  • Re: Windows XP on a Macintosh network
    ... > with Windows machines. ... You'll have to look in your Mac's network ... > Printer Wizard works very well to add network laser printers to Windows ...
    (microsoft.public.windowsxp.network_web)