Re: W2K3 AD Configuration Question
From: Miha Pihler (mihap-news_at_atlantis.si)
Date: 12/19/04
- Next message: m.marien: "Re: Domain or Workgroup?"
- Previous message: Guy: "RE: Domain or Workgroup?"
- In reply to: Richard: "W2K3 AD Configuration Question"
- Next in thread: Richard Young: "Re: W2K3 AD Configuration Question"
- Reply: Richard Young: "Re: W2K3 AD Configuration Question"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 19 Dec 2004 13:51:31 +0100
Hi Richard,
In Active Directory domain clients use DNS to find domain controllers. For
this they uses special records called resource records that can not be found
in your ISP's DNS server. These resource records tell the clients which
server is global catalog (among other information that clients might need).
So one of your servers (e.g. Active Directory server) will have to be DNS
server for your active directory domain.
You can continue to use your firewall NAT device as DHCP server. You will
just have to reconfigure it to give out your active directory DNS for
preferred DNS.
Note: Clients and all servers (including domain controllers) that are
members of domain must point to your internal DNS server if you want your
domain to function properly.
After you change this on your network, configure your DNS server (probably
your AD server) to forward unknown requests to your ISP.
.net name is OK as long as this name is not already in use on the internet.
If it is, your clients will have very hard time comunicating or browsing
their web site.
Feel free to post back if you have any additional questions.
Mike
"Richard" <Richard@discussions.microsoft.com> wrote in message
news:96586BDD-817F-42A9-A0B2-6A27C91A5F57@microsoft.com...
> I'm setting up a small lan (less than fifeteen machines including a single
> W2K3 server), I am experiencing some odd behavior with the configuration
> and
> I am seeking advices/pointers to correct the problem. The configuration
> is
> as followings:
>
> Cable Modem connected a standalone Firewall/NAT server which in turn is
> connected to a 10/100 Mbps Switch. (The Firewall/NAT server also acts as
> the
> DHCP server for the network.)
>
> W2K3 is running AD but is not configured as the DHCP or DNS server; these
> functions are handled externally by the ISP and internally by the
> Firewall/NAT server. When a setup the W2k3 domain i used the Management
> Wizards. When requested to enter a domain name I entered a name with the
> *.net suffix, question: Should I have used the *.local suffix instead, as
> this system (network) will not be registered on the Internet? The network
> is
> meant for private use only but access from the nine or so clients on this
> private network will need access to the Internet.
>
> One of the problems that I continue to see is that from time-to-time the
> client systems cannot locate and be authicated by the DC. When this
> happens
> I have to logoff of the client, which complains that it cannot save user
> profile information nor can it sync the users My Documents folder which is
> stored on the DC. In addition, connectivity to all fileshares located on
> the
> DC are lost as well. Once the user logs off and then re-logs into the
> server
> everything is fine...at least until the problem repeats itself. Any
> suggestions for resolving this issue? Connectivity to the Internet is not
> lost when the authenication problem with the DC occurs. A user, from any
> system, can surf the Web without interruption.
- Next message: m.marien: "Re: Domain or Workgroup?"
- Previous message: Guy: "RE: Domain or Workgroup?"
- In reply to: Richard: "W2K3 AD Configuration Question"
- Next in thread: Richard Young: "Re: W2K3 AD Configuration Question"
- Reply: Richard Young: "Re: W2K3 AD Configuration Question"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
