terça-feira, 22 de maio de 2012 19:37
I am attempting to join 3 Windows XP machines to a domain. But when I do try to join the Domain, I receive the error message: A domain controller for the domain mainengineering.local
could not be contacted. Ensure that the domain name is typed correctly. When I click on details
the following information comes up:
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain mainengineering.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.mainengineering.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:
. (the root zone)
Also, when I go into the command prompt and use the nslookup command the error message appears:
Can't find server name for address 127.0.0.1: No response from server
*************.net can't find mainengineering.local: Non-existent domain.
In the network connections settings, I have each NIC static set to the Primary DNS of 127.0.0.1 since this is identical to the server.
When I nslookup on my server in cmd prompt I get the message:
Forgive me if I leave any info out, I'm new to Server AD
The only roles that are installed are DNS, AD DS and File Services.
Please help if possible.
Todas as Respostas
terça-feira, 22 de maio de 2012 20:16
127.0.0.1 is the local loopback address...it points to the computer itself and not to the server.
Your dns settings in the client should point to the ip of the server 192.168.50.2 ?
terça-feira, 22 de maio de 2012 20:24
1. Double check the DNS settings in NIC parameters. There is ONLY local network DNS - most probably this DNS on domain controller - and NONE public one.
2. For configuration purposes you can disable firewall on server.
3. Add suffixes in Windows clients, namely the mainengineering.local
4. Run dcdiag for Active Directory diagnostics.
5. If the problem persists, use network monitor to catch the traffic (either from Microsoft of free Wireshark)
terça-feira, 22 de maio de 2012 20:32
please post an unedited ipconfig /all from the DC/DNS servers and the problem machines.
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
- Sugerido como Resposta Ravikumar PulagouniMicrosoft Community Contributor quarta-feira, 23 de maio de 2012 03:44
- Não Sugerido como Resposta Ravikumar PulagouniMicrosoft Community Contributor quarta-feira, 23 de maio de 2012 03:45
quarta-feira, 23 de maio de 2012 04:04
As Weber said above, posting of IP information will give us clue to identify what the problem is?
Seems we have communication/network issue between xp machines and DNS server.
- Configure IP settings properly if you use static IP addressing.
- Ping DNS server IP address and make sure there is connectivity between DNS server and XP machines.
- Make a manual entry of DNS IP address in NIC adapter properties, IP settings.
- Check for firewall settings at DNS server.
- Check for VLAN restriction settings if you have any?
Regards, Ravikumar P
quarta-feira, 23 de maio de 2012 07:53
Check IP adress for client and server
Try to ping the server
If can't ping check the Firewall settings and dns
quarta-feira, 23 de maio de 2012 08:21
DNS issue. Please provide IPCONFIG /ALL from DC and CLIENT. Comment the real domain name but other info you can leave.
MCP | Microsoft Certified Professional
MCTS 70-640 | Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
MCTS 70-642 | Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration