My advice would be "Don't even think about it!" Multihoming a DC is bad
practice and will cause all sorts of odd problems which you don't want.
Making a DC a remote access server causes the same problems, because as soon
as a remote user connects, the server acquires an extra IP address for its
"internal" interface, which causes the same problems. (The only exception is
sbs server, which is designed to run in this config).
If you are determined to do it anyway, at least read KB292822 and
830063.
"DaveH" <(E-Mail Removed)> wrote in message
news:7294B3B9-C010-4198-AEA7-(E-Mail Removed)...
> Next week I will be attempting to setup the RAS & VPN server role on my
> Win2003 Enterprise server. The server is the DC w/ AD installed. The
> server
> has two NIC's one that is used for our intranet (192.168.1.x) and the
> other
> (207.5.x.x) that is currently disabled that I want to use for our internet
> connection. My thought is to remove my Linksys router that sits between
> our
> 192.168.1.x network and the internet and use the two NIC's to separate the
> networks having the server translate NAT and route. The goal would be to
> enable the clients to establish a VPN connection with the server to
> retrieve
> email and connect to our ERP software.
>
> My first question would be regarding the IP addressing. I believe that I
> have to remove the gateway address from the 192.168.1.X NIC to use the
> gateway address on the second NIC to forward to my ISP. Is this correct?
>
> Second, I don't think I have to setup any routes because during the
> installation it looks like I will have to designate the internet
> connection
> NIC and the intranet NIC. Is this correct?
>
> Is there any other issues I should be aware of or any suggestions?
> Dave
>
|
Similar Threads
Linear Mode
