tomy2 said:
I have a win2003 AD server at home with a cpl pcs on a network. I am
trying to set the pcs up to log into the server ....I am unable to
join the domail. I think it is a dns problem. I need to be able to get
out on the net with the pcs as well as the server. the domain i have
is just a local one for my lab. Any help what I am doing wrong?
My first guess is that you have your internal Clients ipconfig configured
with the ISP's DNS and that is the problem. All must use only the DC for
DNS.
When you promoted your DC, the wizard would have asked you to configure the
DC as a DNS server and created the needed zones in DNS.
Use the DNS Management console to connect to your internal DNS server, if
the console says configure your DNS server, run through the Wizard, don't
create a forward lookup zone and DO configure Root Hints. Doing this should
start your internal DNS resolving internet names.
If it does not give you the configure your DNS server message, connect to
your internal DNS and expand it down to Forward lookup zones, You should
have two forward lookup zones if you let the DCPromo wizard configure DNS
for you, one name with your internal domain name and one named
_msdcs.internaldomainname. If there is one named only with a "."(dot) delete
it and DNS should ask you to configure root hints, do this.
If your AD Domain name is a single label DNS name (domain vs. domain.com)
there are registry entries you will need to add to all your clients and DCs.
825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036&sd=RMVP
323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;323380&sd=RMVP
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684&sd=RMVP