Re: How to configure Windows 2003 as a Router ?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Whatever device you use as a router, it is going to be a single point of
failure unless you have a very complicated routing setup with multiple
paths.

How are you planning to connect HQ to a remote site? Leased lines or
VPN?

"Peter" <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:e9Y6Tq9iHHA.4704@xxxxxxxxxxxxxxxxxxxxxxx
Dear Bill,

Thank you for your advice.

The reason why we consider this option is because our Network Officer says
that by using a Windows 2003 Server as a router for connecting machines in
headquarter to a remote site.

I just wonder whether it is a good idea as the single point of failure
will be the Windows 2003 Server and the 2 NIC.

Regards,
Peter


"Bill Grant" <not.available@online> wrote in message
news:ussb9S4iHHA.4032@xxxxxxxxxxxxxxxxxxxxxxx
It is possible to allow IP routing without using RRAS, but it is pretty
pointless. Simply configure RRAS to be a LAN router from the wizard and
it will do it for you.

As Jeremy pointed out, all this does is configure the machine so that
it can forward traffic from one subnet to the other. Whether it routes or
not depends on how the two subnets are configured.

If all you want to do is link these two subnets, the routing is
trivial. You simply make the RRAS router the default gateway for both
subnets. eg

192.168.1.x dg 192.168.1.1
|
192.168.1.1 dg blank
RRAS
192.168.2.1 dg blank
|
192.168.2.x dg 192.168.2.1

Any traffic which is not local (ie not in the same IP subnet) is sent
to the router. The router can deliver it in the other subnet because it
has an interface in that subnet (ie the target machine is local to the
router).

Usually the setup is not as simple as that. One subnet is usually
using some other router, such as an ADSL Internet device as its default
gateway. Simply enabling IP routing doesn't do much because the trafffic
never gets to the RRAS router. You need extra routing to get the traffic
to the correct router. If you are in that situation and can't see what
extra routing you need, post a description of how your network is set up.

PS. I hope this server is not a DC. Using a DC as a router is not
recomended and it may cause you all sorts of odd problems.





.

Relevant Pages

  • Re: Routing and RRAS Problem - Pleasehelp
    ... Traffic from your "internal" subnet can get ... out to the Internet by default routing, but the return traffic will fail. ... You need to add an extra route to the Linksys router so that it knows how to ...
    (microsoft.public.windows.server.networking)
  • Re: please advise - problem with routing
    ... > Sorry for the confusion, again, ther is cisco router which connects ... > "Dana Brash" wrote in message ... >> This configuration can be accomplished by changing the subnet mask on ... >> routing anything and just using a different subnet mask, ...
    (microsoft.public.windows.server.networking)
  • Re: New to RRAS for Routing
    ... Perhaps you could read a basic text on IP routing. ... you do not need any routes on the router ... The router has an interface in each subnet, so it is aware of both ... If the default route is not to the internal router, ...
    (microsoft.public.windows.server.networking)
  • Re: How to configure Windows 2003 as a Router ?
    ... failure unless you have a very complicated routing setup with multiple ... Simply configure RRAS to be a LAN router from the ... If all you want to do is link these two subnets, the routing is ... Any traffic which is not local (ie not in the same IP subnet) is sent ...
    (microsoft.public.windows.server.networking)
  • Re: getting routes from internet facing routers
    ... Attacker can get the routing info by exploiting routing protocol in ... Just have a proper ACL on the router, ... seeing what private IP routes ... Securing Apache Web Server with thawte Digital Certificate ...
    (Security-Basics)