Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can not authenticate workstation to server

Status
Not open for further replies.

moviejunkie

IS-IT--Management
Oct 12, 2006
21
US
Help, when I try to add a workstation to the domain (at the ws)(I am running xp pro sp2) it gives me this error, I am running DHCP on the server, I only have one DNS in the server and I have the gateway for my internet connection. then I have a forward in the DNS to my router dns for internet.

I get this error:

Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain mydomain.local:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.local

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child zone:

mydomain.local
local
. (the root zone)

For information about correcting this problem, click Help.


Help plz and thanks

God Bless
Jason
 
One the workstation check the ip address its got,

start - run - cmd - ipconfig /all

Make sure that all the info there is correct especially that it is pointing only to your internal DNS server.

Make sure you can ping the DNS server by IP, Name, FQDN.

On your DHCP server does the XP machine have a valid lease?

Have you connected other machines successfully?

Iain
 
Assuming you aren't familiar with NSLookup, I won't get you to check if the record really exists.

On the server in a command prompt, type in net stop netlogon /y
net start netlogon
net start dns

Wait 15 minutes. Netlogon re-creates thses DNS entried every time it starts. After 15 minutes, still on the server, type in ipconfig /registerdns

On the workstation, through a command prompt, type in ipconfig /flushdns
net stop dnscache /y
net start dnscache

If it still doesn't work, your IP settings on either the client or the server are incorrect, or the DNS server doesn't support dynamic updates.
 
I figured it out, I have two nic's on the server and I was selecting the wrong one in my dhcp settings. Is there a way to select which nic the dns server will broadcast on?
 
DNS doesn't broadcast - it is directed/requested (i.e. it has to have a UDP socket connection to port 53) - there is no broadcast.

If you have two NICs, by default, DNS will listen on both. Usually it is a good idea to have both server NICs point to the internal IP of the server for DNS resolution.

DHCP should also point to the internal IP address of the server for its option 006 (DNS Server). You can change this by running dnsmgmt.msc, expanding Scope Options, and changing option 006 DNS Servers to the internal IP of the server.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top