Re: coming from NT
From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 05/04/04
- Next message: Phillip Windell: "Re: Where to put my multiple servers?????"
- Previous message: Hubert Mayr: "windows 2003 vpn server in local lan behind us robotice 8022 router"
- In reply to: noobtech: "Re: coming from NT"
- Next in thread: Phillip Windell: "Re: coming from NT"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 4 May 2004 10:04:26 -0400
noobtech wrote:
> I Don't want to beat this to death but I'm truly confused with DNS
> and it's role in a domain. I'd take some classes but unfortunately at
> this point that is not an option. I've brought a few books but they
> don't cover what I'm not understanding
>
> if I had a basic router that could do NAT/DHCP (like a Linksys or
> Netgear) then all my clients on my (non domain) LAN would be pointing
> to the router as its default gateway. I have done this before easily
> in a small office where we had 5 computers that just needed internet
> access. In such cases all computers nic's would be pointing to the
> router as the default gateway. It's pretty much point A to point B.
>
> In a domain situation it's different.
No it isn't.
> Client's in a domain are not
> directly directed to the Lan router.
> Under NT they were directed to
> the domain controller. And from there it would go to the Router.
Only if you were using the NT server as a router - were you running a proxy
server on the NT box?
>
> In windows 2xxx when DNS is on a member server and not on the Domain
> controller. Who do the clients point to as their default gateway, DNS
> or Domain controller?
You need AD-integrated DNS to run AD properly.
Clients and servers all point to the IP address of whatever "device"
connects them to the Internet. Either your router/firewall as you mentioned
(and if you don't have one, get one - why turn a DC into a router?) or your
server if you're multihomed and going that route, ISA, whatnot.
DNS and the domain config has absolutely nothing to do with this. :-)
> Who does the DNS server point to as it's
> default gateway? If it's not the router but the DC why? Who does the
> Domain controller point to as it's default gateway? if it's not DNS
> but the router, why?
Again - all computers - servers & workstations alike - have to point to
whatever IP gives them Internet access.
>
> based on what I know so far:
> I see a purpose for DNS server to have the lan router as it's default
> gateway but I don't see the purpose of having the Domain controller
> use the lan router as it's default gateway.
Why not?
> Nor do i see a purpose in
> having the clients use the Domain controller as its default gateway.
Well, they can't, unless you're using it as a router to get them to the
Internet.
Get a router/firewall and point all clients & servers at its internal IP as
default gateway. For DNS, again, make sure that all servers and workstations
specify *only* the internal AD-integrated DNS server's IP address in their
network settings. The AD-integrated DNS server should be set up with
forwarders to your ISP's DNS servers for external resolution. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202 for more
info.
- Next message: Phillip Windell: "Re: Where to put my multiple servers?????"
- Previous message: Hubert Mayr: "windows 2003 vpn server in local lan behind us robotice 8022 router"
- In reply to: noobtech: "Re: coming from NT"
- Next in thread: Phillip Windell: "Re: coming from NT"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
