0

I am receiving the following 3 errors in my DNS Event Viewer:


------
DNS server has updated its own host (A) records. In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it.

To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.

-------------
The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

-------------
The DNS server was unable to complete directory service enumeration of zone corp.yodock.com. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error.
-------------

There are no replication partners. The server can ping external URL's and external computers can ping the server. There are no duplicate computers listed in Active Directory. When users in the office connected to the server attempt to synchronize their offline files, they get an error message that the domain controller cannot be reached.

I'm ready to pull my hair out here - any suggestions would be greatly appreciated!

2
Contributors
4
Replies
5
Views
8 Years
Discussion Span
Last Post by jamesP814
0

Running NETDIAG returns these results (I removed identifying information):

    Computer Name: COMPUTERNAME
    DNS Host Name: HOSTNAME
    System info : Microsoft Windows Server 2003 R2 (Build 3790)
    Processor : x86 Family 6 Model 15 Stepping 11, GenuineIntel
    List of installed hotfixes :
        KB921503
        KB924667-v2
        KB925398_WMP64
        KB925876
        KB925902
        KB926122
        KB927891
        KB929123
        KB930178
        KB931784
        KB932168
        KB933360
        KB933729
        KB933854
        KB935839
        KB935840
        KB936021
        KB936357
        KB936782
        KB938127-IE7
        KB938464
        KB939653-IE7
        KB941202
        KB941568
        KB941569
        KB941644
        KB941672
        KB941693
        KB942615-IE7
        KB942763
        KB942830
        KB942831
        KB943055
        KB943460
        KB943484
        KB943485
        KB944533-IE7
        KB944653
        KB945553
        KB946026
        KB947864-IE7
        KB948496
        KB948590
        KB948745
        KB948881
        KB949014
        KB950759-IE7
        KB950760
        KB950762
        KB950974
        KB951066
        KB951072-v2
        KB951698
        KB951746
        KB951748
        KB952069
        KB952954
        KB953155
        KB953838-IE7
        KB953839
        KB954211
        KB954550-v5
        KB954600
        KB955069
        KB955839
        KB956390-IE7
        KB956391
        KB956802
        KB956803
        KB956841
        KB957095
        KB957097
        KB958215-IE7
        KB958644
        KB958687
        KB958690
        KB960225
        KB960714-IE7
        KB960715
        KB961063
        KB961064
        KB961118
        KB961260-IE7
        KB967715
        Q147222


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



Per interface results:

    Adapter : Local Area Connection

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : HOSTNAME
        IP Address . . . . . . . . : zz.zz.z.zzz
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : zz.zz.z.1
        Primary WINS Server. . . . : zz.zz.z.zzz
        Dns Servers. . . . . . . . : zz.zz.z.zzz
                                     xx.xxx.xxx.xx
                                     yy.yyy.y.yy


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

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

        WINS service test. . . . . : Passed


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{796B1D56-3CE5-4B61-BDB8-708A03E333EE}
    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 Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


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


DNS test . . . . . . . . . . . . . : Passed
    PASS - All the DNS entries for DC are registered on DNS server 'zz.zzz.z.zzz'
.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver 'yy.yyy.yyy.yy'. Please wait for 30 minutes for DNS server replication.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver 'xx.xxx.x.xx'. Please wait for 30 minutes for DNS server replication.


Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{796B1D56-3CE5-4B61-BDB8-708A03E333EE}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{796B1D56-3CE5-4B61-BDB8-708A03E333EE}
    The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


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


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


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

Edited by mike_2000_17: Fixed formatting

0

Just in case anyone else ever runs into a similar problem, I resolved this issue through trial and error. Turns out when I downloaded the Windows update, it activated the Windows Firewall, which was blocking the connections. As soon as I turned the windows firewall back off, everything was running smoothly again.

0

Thats wierd. Was this windows server 2003? I thaught that came with the firewall off by default anyway (at least in my version - r2 enterprise)

0

Yes, it is Windows Server 2003. The firewall has never been turned on before. I'm not sure how or why it got turned on last week, the only answer I could come up with though was that it happened when I downloaded an update because that is when we started having problems.

Thats wierd. Was this windows server 2003? I thaught that came with the firewall off by default anyway (at least in my version - r2 enterprise)

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.