In (e-mail address removed) <
[email protected]>
posted a question
Then Kevin replied below:
Thanks for posting the ipconfig /all I see that you have at least two
serious problems.
Problem 1. Your Primary DNS suffix is a single-label name, if this is the
actual name of your AD domain, this won't even begin to work until you make
registry entries on your DC _and_ _all_ running Win2kSP4, WinXP or Win2k3.
I'll post the KB For this below. Even after you make the registry entries,
your AD domain may not apply Group Policies properly because your domain
name _will_ _not_ resolve in DNS. Your Domain must resolve so the SYSVOL DFS
share is accessible at \\CHC022\SYSVOL\ If you click on this link and you
get an error you have the problem and there is no easy fix for it.
Possible problem 2. If the Primary DNS suffix is not the same as your AD
domain name in ADU&C, e.g. I can se you Primary DNS suffix is CHC022 but if
you AD Domain name in ADU&C is CHC022.com, .net, or .something-else, then
this is a disjointed namespace which there is a fix for. That KB will be
posted below, too.
Problem 3. The most common mistake is the use of your ISP's DNS in TCP/IP
properties, this is a definite problem. _Never_ use your ISP's DNS in _any_
_position_ on _any_ member of an Active Directory domain.
Problem 1.
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684
826743 - Clients cannot dynamically register DNS records in a single-label
forward lookup zone:
http://support.microsoft.com/?id=826743
Possible Problem 2.
257623 Domain Controller's Domain Name System Suffix Does Not Match Domain
Name
http://support.microsoft.com/?id=257623
Problem 3.
300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1
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