?
Solved

Error 5774 Source Netlogon

Posted on 2006-04-12
8
Medium Priority
?
1,327 Views
Last Modified: 2012-08-13
I have a Windows 2003 Server, with serves as our PDC and Email Server for Exchange 2003.  I've never had a problem until recently and this is the error message showing up in the Event Logs.  The challenge is, I have to fix this REMOTELY from off-site.  Can anyone give assistance?




The dynamic registration of the DNS record 'ForestDnsZones.mydomain.org. 600 IN A 169.254.98.134' failed on the following DNS server:  

DNS server IP address: 216.147.43.193
Returned Response Code (RCODE): 5
Returned Status Code: 9017  

For computers and users to locate this domain controller, this record must be registered in DNS.  

USER ACTION  
Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. You can find this program on the Windows Server 2003 installation CD in Support\Tools\support.cab. To learn more about  DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by  this domain controller, run 'nltest.exe /dsregdns' from the command prompt on the domain  controller or restart Net Logon service. Nltest.exe is available in the Microsoft Windows  Server Resource Kit CD.
  Or, you can manually add this record to DNS, but it is not recommended.  

ADDITIONAL DATA
Error Value: DNS bad key.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
Comment
Question by:CHILINVLN
  • 3
  • 3
7 Comments
 
LVL 85

Expert Comment

by:oBdA
ID: 16437597
There are two problems that show up immediately:
Your DC doesn't have a static IP address, or if it's entered statically, it's from an incorrect range. 169.254.0.0 is the range reserved for APIPA, it should not be used for a normal network.
APIPA
http://www.webopedia.com/TERM/A/APIPA.html

Then your DC has an external DNS server specified in the TCP/IP properties, instead of itself (and, if applicable, other *internal* DNS servers). Change the DC to point to itself only, configure forwarders (the 216 DNS server for example) for external resolution.
You should be able to fix the DNS entry remotely. Changing the IP range should be done while you're there, that involves somewhat more work.
Check here for details about the correct DNS settings in an AD domain:

10 DNS Errors That Will Kill Your Network
http://mcpmag.com/features/article.asp?EditorialsID=413

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/?kbid=825036
0
 
LVL 1

Author Comment

by:CHILINVLN
ID: 16437654
My DC DOES have a static IP address, which is 192.168.1.4 and it's locked.  If you ping the IP or the name of the server from any machine in the office, it does resolve.

I have the DNS forwarding to three other IP's, however, none of those are the ones on this error message.  This problem was first noticed when my users tried to access their email with Outlook 2003.  However, they CAN access their email over the web, which is telling me the IP's and IIS is correct.

Here is another thread on that for reference.
http://www.experts-exchange.com/Networking/Email_Groupware/Exchange_Server/Q_21808339.html
0
 
LVL 85

Expert Comment

by:oBdA
ID: 16437898
Then you have an unused NIC in the machine which is trying to obtain a DHCP address; this should be disabled.
You won't find the 216 IP address from above in the forwarders; it's a DNS server entry in the TCP/IP properties of a NIC (probably the unused one!)
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 1

Author Comment

by:CHILINVLN
ID: 16438600
Remember, this is my domain controller.  It's ASSIGNING IP addresses out.  There is only 1 nic enabled, and the IP is static 192.168.1.4  The DNS Forwarders on it are correct.

I can't find this IP address ANYWHERE on the server...  216.147.43.193

THere has got to be an explanation for this and why it's causing everyone to not be able to reach the Exchange Server (on the same server) to access email other than OWA.
0
 
LVL 85

Expert Comment

by:oBdA
ID: 16468759
That's rather bizarre.
Did that machine ever have a second NIC that was connected directly to an ISP (the IP address above is ns.apollohosting.com), and then removed?
If so, change the view in Device Manager to display hidden devices, check if the old NIC shows up, and delete it.
0
 
LVL 1

Author Comment

by:CHILINVLN
ID: 16468782
I solved this myself.. and this was the problem.

Our primary firewall was acting as a DHCP which conflicted with our true DHCP on the server.  I had our ISP disabled the DHCP on the firewall, I reconfigured our forwarders for DNS to point to itself rather than outside DNS servers, and I restarted all DHCP services.

This completely flushed out the problem and resolved everything on the network.  When and how the DHCP services were changed on the firewall, I dunno, however, it was fixed.  This gave me a hard time mainly because I didn't even begin to think the problem was coming from my firewall.  Naturally, I thought the problem was server based and I couldn't locate it anywhere.
0
 

Accepted Solution

by:
GranMod earned 0 total points
ID: 16914974
PAQed with points refunded (500)

GranMod
Community Support Moderator
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
Screencast - Getting to Know the Pipeline
Look below the covers at a subform control , and the form that is inside it. Explore properties and see how easy it is to aggregate, get statistics, and synchronize results for your data. A Microsoft Access subform is used to show relevant calcul…

862 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question