Leave it just like it is except that you stop using the ISP's DNS and use
the internal AD/DNS. It doesn't matter which nic they are on but it is more
logical to place them in the Internal nic. You could leave DNS blank on the
external nic or use the same AD/DNS on both nics, doesn't make much
difference. DNS settings are really "global" for the whole machine dispite
what it looks like.
The *only* place the ISP's DNS server IP#s should ever appear is in the
Forwarders List within the config of your AD/DNS. It should never be
anywhere else. Make sure whatever you use for a firewall allows your AD/DNS
to make outbound DNS Queries to the ISP's DNS.
Also make sure the Internal nic is at the top in the priority in the
binding,...found at:
Properties of Network Places
Advanced from the top menu
Advance Settings... from the drop down menu
......should be obvious from that point.....
Leave everything else the way it is,...don't try to get "creative"....
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"MIchael Trantas" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi -
>
> I have several servers that I am trying to add to my Active Directory
domain
> that are multihomed and are connected to both internal (AD) and external
> (Internet) networks. The currect TCP/IP configuration is as follows:
>
> INTERNAL NETWORK SETTINGS:
> IP Addr. - 192.168.0.35
> Subnet - 255.255.255.0
> Gateway - NONE
> DNS Servers - NONE
>
> EXTERNAL NETWORK SETTINGS:
> IP Addr. - 192.168.100.6
> Subnet - 255.255.255.0
> Gateway - 192.168.100.1 (internal NAT'd address)
> DNS Servers - 146.145.64.2 (our provider's dns servers)
> 146.145.64.3
>
> How do I set this machine up so that it will authenticate internal users
to
> the Active Directory network while hosting websites on my DMZ??? I tried
> this with another server and it takes a really long time to log into the
> computer under the domain account...
>
> Michael
>
>
Similar Threads
Linear Mode
