Re: ???Can't Add machine to Domain due to DNS lookup problem????

From: Herb Martin (news_at_LearnQuick.com)
Date: 05/27/04


Date: Thu, 27 May 2004 10:40:00 -0500


"Jeff" <anonymous@discussions.microsoft.com> wrote in message
news:1375701c443fd$18b9e780$a401280a@phx.gbl...
> Hello Guys.....I have a functional domain and I can add
> any other computers to it, but for some reason, this
> machine "fell off" the domain and I cannot add it....when
> i try, I get this error: "The following error occurred
> validating the name "CONCORD". This condition may be
> caused by a DNS lookup problem. For information about
> troubleshooting common DNS lookup problems, please see the
> following Microsoft Web site:
> http://go.microsoft/com/fwlink/?LinkId=5171"
>
> I have checked out that site, but it just talks about
> active directory and we don't even use active directory
> here.....

Seems odd you would be asking this in a WIN2000 forum
since all Win2000 domains use Active Directory.

You do however likely have a DNS (maybe a WINS issue
if you REALLY are using an NT domain or using an OLDER
client, NT4/9x).

Servers AND clients must be DNS and/or WINS clients if
you use these servers.

For AD (Win2000+) domains, you must use at least DNS, but
older clients (or older domains) will need WINS servers if
you have more than ONE SUBNET (broadcasts work for one
subnet.)

Clients (including servers) must NOT try to specifiy both an
internal AND external DNS server -- use only the INTERNAL.

> I can't seem to figure out what to do at this
> point....usually when a machine falls off the domain, I
> simply remove it from the domain on the machine, and

Actually with Win2000+ you want to STOP doing that;
use "reset" instead.

> uninstall and reinstall the network drivers and re-add it
> to the domain and it works, but not this time.....I would
> appreciate ANY help you could offer in this
> matter....thank you!

If running Win2000+ DCs then run DCDiag on each one;
save output to a text file; search for save, warn, error.

Make sure clients (including DCs, DNS, WINS servers)
ALL specify the correct (internal) name servers.

--
Herb Martin


Relevant Pages

  • Re: Traveling Users Unable to Authenticate to AD
    ... authenticate to your AD while on the NDS network and you believe that DNS is ... One question that comes to mind is what DNS server is the client machine ... domain on the us.parent.com name servers. ... > MYCO.US.PARENT.COM Active Directory, get their mapped drives, access to ...
    (microsoft.public.windows.server.active_directory)
  • Re: Questions on putting up a new DNS server.
    ... > Root domain AD-zone info. ... There are no other servers or clients in the Root domain. ... own DNS servers -- integrate them into AD. ...
    (microsoft.public.win2000.dns)
  • Major Issues After NT4 --> 2003 Upgrade
    ... For some reason, the servers are joining the DNS domain name, instead of the ... Our NT4 domain we'll call "NBIOS" and the DNS domain name that we assigned ... finding that the clients started thinking they were joined to the DNS.com ...
    (microsoft.public.windows.server.migration)
  • Event Viewer Anomoly
    ... DNS operation refused. ... The File Replication Service is having trouble enabling replication ... The topology information in the Active Directory for this replica ... performed with one or more critical servers in order for changes to ...
    (microsoft.public.win2000.networking)
  • Re: DCs to use their own DNS/Domain name, while clients use another
    ... > -All client/member servers configured to use DNS servers that host the ... members should be in that domain for DNS as well. ... Pretty silly since the domain clients are using the BIND set. ...
    (microsoft.public.win2000.dns)