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

[Jeff]

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.....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
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!

 

[Herb Martin]

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.

 

[Kevin D. Goodknecht [MVP]]

In

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.....

If you have a Win2k or Win2k3 Domain, you _are_ using Active Directory.

Post the ipconfig /all of the DC and the client.

 

[Guest]

Perhaps I should have been a bit more specific with the
information I provided. We are on an NT domain, our DNS
server is running Red Hat Linux 9, we DON'T use WINS here,
and the DHCP server is serving up the correct DNS server
entries......I ran a NETDIAG and this is the output it
provided:


Computer Name: 4200-FISH
DNS Host Name: 4200-FISH
System info : Windows 2000 Professional (Build 2195)
Processor : x86 Family 6 Model 8 Stepping 1,
AuthenticAMD
List of installed hotfixes :
KB329115
KB820888
KB822831
KB823182
KB823559
KB824105
KB824146
KB825119
KB826232
KB828035
KB828741
KB828749
KB835732
KB837001
Q147222
Q295688
Q816093


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection 2

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : 4200-FISH.concord.org
IP Address . . . . . . . . : 216.204.202.151
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 216.204.202.1
Dns Servers. . . . . . . . : 216.204.196.100
216.204.202.91


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names is
missing.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this
interface.


Global results:


Domain membership test . . . . . . : Passed
Dns domain name is not specified.
Dns forest name is not specified.


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{69BA1CD3-8648-4576-8C58-B9182960CFE6}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the
<00> 'WorkStation Service', <03> 'Messenger Service',
<20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed


Redir and Browser test . . . . . . : Failed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{69BA1CD3-8648-4576-8C58-B9182960CFE6}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{69BA1CD3-8648-4576-8C58-B9182960CFE6}
The browser is bound to 1 NetBt transport.
[FATAL] Cannot send mailslot message
to '\\CONCORD*\MAILSLOT\NET\NETLOGON' via redir.
[ERROR_BAD_NETPATH]


DC discovery test. . . . . . . . . : Failed

This computer cannot be joined to the [CONCORD] domain
because of one of the
following reasons.

1. The DNS SRV record for [CONCORD] is not registered in
DNS; or

2. A zone from the following list of DNS zones does not
include delegation
to its child zone.

Such zones can include [CONCORD], and root zone.

Ask your network/DNS administrator to perform the
following actions: To
find out why the SRV record for
[_ldap._tcp.dc._msdcs.CONCORD] is not registered in the
DNS,
run the dcdiag command prompt tool with the command
RegisterInDNS on the
domain controller that did not perform the registration.
[FATAL] Cannot find DC in domain 'CONCORD'.
[ERROR_NO_SUCH_DOMAIN]


DC list test . . . . . . . . . . . : Failed
'CONCORD': Cannot find DC to get DC list from
[test skipped].


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Skipped


LDAP test. . . . . . . . . . . . . : Failed
Cannot find DC to run LDAP tests on. The error
occurred was: The specified domain either does not exist
or could not be contacted.



This computer cannot be joined to the [CONCORD] domain
because of one of the
following reasons.

1. The DNS SRV record for [CONCORD] is not registered in
DNS; or

2. A zone from the following list of DNS zones does not
include delegation
to its child zone.

Such zones can include [CONCORD], and root zone.

Ask your network/DNS administrator to perform the
following actions: To
find out why the SRV record for
[_ldap._tcp.dc._msdcs.CONCORD] is not registered in the
DNS,
run the dcdiag command prompt tool with the command
RegisterInDNS on the
domain controller that did not perform the registration.
[WARNING] Cannot find DC in domain 'CONCORD'.
[ERROR_NO_SUCH_DOMAIN]


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped
The IPSec Policy Agent service is not started.


The command completed successfully

 

[Kevin D. Goodknecht [MVP]]

In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:

Perhaps I should have been a bit more specific with the
information I provided. We are on an NT domain, our DNS
server is running Red Hat Linux 9, we DON'T use WINS here,
and the DHCP server is serving up the correct DNS server
entries......I ran a NETDIAG and this is the output it
provided:

Then you are in the wrong news group, NT4 does not use DNS for locating the
domain, It uses NetBIOS broadcasts and NTLM Authentication.
Netdiag will not help you diagnose this problem much, it is intended to
diagnose TCP/IP problems for Active Directory domain connectivity.
I suggest you post in the microsoft.public.windowsnt.domain newsgroup.

 

[Jeff]

I just assumed this was the Windows 2000 client issue, not
the NT domain issue, seeing as though I am able to add
other windows 2000 clients to the domain.....

-----Original Message-----
In (e-mail address removed)

posted a question
Then Kevin replied below:

Then you are in the wrong news group, NT4 does not use DNS for locating the
domain, It uses NetBIOS broadcasts and NTLM Authentication.
Netdiag will not help you diagnose this problem much, it is intended to
diagnose TCP/IP problems for Active Directory domain connectivity.
I suggest you post in the

microsoft.public.windowsnt.domain newsgroup.

 

[Kevin D. Goodknecht [MVP]]

In

I just assumed this was the Windows 2000 client issue, not
the NT domain issue, seeing as though I am able to add
other windows 2000 clients to the domain.....

Maybe it is and maybe it isn't but to get the best coverage it should be
posted in a group that can help you, since NT4 domains don't use DNS for DC
locator, the nt4 domain group would help you more.

 

[Herb Martin]

What Kevin said (in other posts), plus:

If you have Microsoft machines/domains using legacy
clients or legacy servers, even Win2000+ if you wish
BROWSING to work, then you are using NetBIOS for
name resolution.

Without WINS, that NetBIOS resolution is inefficient
and likely BROKEN.

A common mistake of UNIX admins who don't understand
Microsoft networking clients and servers is to believe that
"NetBIOS is bad" and therefore "WINS is bad".

Nothing could be further from the truth -- in fact, WINS
servers fix almost all of the "bad" of NetBIOS.

If you have an IP-Microsoft network of any significant
complexity, then you NEED WINS servers and every
client and "server" must be set as a WINS client.

Significant complexity = more than one subnet (usually)

Also, asking a UNIX-DNS/NT4-Domain/Win2000-client
question in a Win2000 SERVER-DNS newsgroup isn't your
more effective option usually, but it sure wastes a lot of
your time and ours if you don't mention that in the first
post.