Starting RRAS kills TCPIP on server

[Guest]

I want to host VPN on our domain controller using RRAS. We set it up
according to MS help. We have a DSL router as the gateway, which also
provides DHCP and NAT. We opened port 1723 on the Lynksys router for VPN.
When RRAS is started, we lose internet access from that server and can't ping
it from other hosts. What's happening?

 

[Bill Grant]

You won't be able to use the standard setup and have your router provide
DHCP and NAT if you are running Active Directory.

The standard setup just has RRAS acting as a NAT router for the LAN,
forwarding DNS requests to the ISP DNS server. This won't work for AD. AD
needs all machines to use the local DNS server.

Basically you need DHCP to give the clients the router IP as the default
gateway, but your local DNS server address for DNS. AND you need to modify
your local DNS to forward requests to a public DNS server (such as your
ISP). So your client machines point to the local DNS server ONLY. If the
request is local, it replies itself. If not, it forwards the request to get
the info it needs, then returns that to the client.