event id 1014 DNS Client Events
every time I restart my server (windows server 2008 r2) I see this error :
Name resolution for the name _ldap._tcp.dc._msdcs.Pharma.lan timed out after none of the configured DNS servers responded.
I've tried almost everything, I can't understand this and what to do to resolve it
May 21st, 2011 11:08am
Hello,
for security reasons, never post your domain name in forums with public access.
Please post the ipconfig /all of the DNS server and a problem client.
Please make sure that:
each DC / DNS server points to itself as primary DNS server and to other internal DNS servers as secondary ones
each DC without DNS points to internal DNS servers public DNS servers are set as forwarders and not as secondary DNS servers your client computers points to the correct internal DNS servers
Once done, run ipconfig /registerdns and restart netlogon service on all DCs.
Also, make sure that there is no firewall that is blocking traffic on port 53.
Check also that you are able to ping the server from the client computer. If you are unable to do it then it may be a problem with your routes / network equipements.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner
Microsoft Certified Professional
Microsoft Certified Systems Administrator: Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2011 12:21pm
Hello,
is that the only DC in the domain?
Is it multi-homed, more then one ip address used on the NIC?
Please post an unedited ipconfig /all from the DC/DNS servers here.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
May 22nd, 2011 4:24pm
Hi Customer,
Thank you for your post.
In addition to Mr X and Meinolf Weber, your problem might be caused by that no DNS server is available during the
restart of a DC. The best option is to have always a DNS server up and run and never boot all DC/DNS servers together.
Please also take a look at the following article, the recommendations in this article are for the installation of Windows 2000 Server or Windows Server 2003 environments
where there is no previously defined DNS infrastructure.
Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/kb/825036
Best Regards,
James Zou
Free Windows Admin Tool Kit Click here and download it now
May 23rd, 2011 9:39pm