Making the DomainController the Default Gateway

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

is it a good or bad idea to make our Win2k domain-controller the default
gateway?
Are there issues/dangers??
We want to set this up because than we can add static routes on the server.

Now the DHCP sets the default gateway for our LAN to a router. We have to
add persistent routes on every client for specific trafic.

Is there maybe a better way to do this??

Mario
 
Assuming you want to enable RRAS on the DC, it is not recommended because that may cause some connectivity issues.

Name resulotion on RRAS
Name Resolution and Connectivity Issues on W2K Domain Controller with RRAS and DNS
.... issues if the W2K domain controller is configured with RRAS and DNS. ....
www.chicagotech.net/nameresolutionpnvpn.htm

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Hi,

is it a good or bad idea to make our Win2k domain-controller the default
gateway?
Are there issues/dangers??
We want to set this up because than we can add static routes on the server.

Now the DHCP sets the default gateway for our LAN to a router. We have to
add persistent routes on every client for specific trafic.

Is there maybe a better way to do this??

Mario
 
Mario, why can't you add the static routes on the LAN router?

If you make the domain controller the default gateway of your LAN, you
will need to make major changes to your routing setup. Only the DC would
connect to the router. The DC would need an extra NIC connecting to the LAN,
and this is not a recommended way to run a DC.
Here are simple diagrams of the two situations.

Internet
|
router
192.168.0.1
|
LAN machines (including the DC)
192.168.0.x dg 192.168.0.1

Internet
|
router
192.168.0.1
|
192.168.0.2 dg 192.168.0.1
DC
192.168.1.1 dg blank
|
192.168.1.x dg 192.168.1.1
 
Back
Top