DNS issues
- From: JimA <JimA@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 15 Nov 2007 07:45:00 -0800
I was reviewing my logs and noticed the following errors:
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1566
Date: 11/15/2007
Time: 7:04:35 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SERVER
Description:
All domain controllers in the following site that can replicate the
directory partition over this transport are currently unavailable.
Site:
CN=NewYork,CN=Sites,CN=Configuration,DC=Premier,DC=local
Directory partition:
CN=Configuration,DC=Premier,DC=local
Transport:
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=Premier,DC=local
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 11/15/2007
Time: 7:04:35 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SERVER
Description:
The Knowledge Consistency Checker (KCC) has detected problems with the
following directory partition.
Directory partition:
CN=Configuration,DC=Premier,DC=local
There is insufficient site connectivity information in Active Directory
Sites and Services for the KCC to create a spanning tree replication
topology. Or, one or more domain controllers with this directory partition
are unable to replicate the directory partition information. This is probably
due to inaccessible domain controllers.
User Action
Use Active Directory Sites and Services to perform one of the following
actions:
- Publish sufficient site connectivity information so that the KCC can
determine a route by which this directory partition can reach this site. This
is the preferred option.
- Add a Connection object to a domain controller that contains the directory
partition in this site from a domain controller that contains the same
directory partition in another site.
If neither of the Active Directory Sites and Services tasks correct this
condition, see previous events logged by the KCC that identify the
inaccessible domain controllers.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 11/15/2007
Time: 7:04:35 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SERVER
Description:
The Knowledge Consistency Checker (KCC) was unable to form a complete
spanning tree network topology. As a result, the following list of sites
cannot be reached from the local site.
Sites:
CN=NewYork,CN=Sites,CN=Configuration,DC=Premier,DC=local
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date: 11/14/2007
Time: 12:37:53 PM
User: N/A
Computer: SERVER
Description:
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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7c 26 00 00 |&..
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date: 11/14/2007
Time: 12:38:00 PM
User: N/A
Computer: SERVER
Description:
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.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7c 26 00 00 |&..
Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13508
Date: 11/15/2007
Time: 2:32:04 AM
User: N/A
Computer: SERVER
Description:
The File Replication Service is having trouble enabling replication from
NYDC01 to SERVER for c:\windows\sysvol\domain using the DNS name
nydc01.Premier.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name nydc01.Premier.local from
this computer.
[2] FRS is not running on nydc01.Premier.local.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d9 06 00 00 Ù...
Our main server in is FL with a VPN connection to NY. I can connect to the
NY server via RDP but the users (in NY) have complained of spotty
performance. I seem to remember seeing an incorrect internal IP tied to the
NY site a couple of weeks ago ( it was 1.10 instead of 2.10, 1.10 is a local
server) and I resolved. I have an SBS2003 R1 (SP1) server in Fl and NY has
a 2003 server. Any ideas on how to resolve this would be very welcome.
Thanks
--
Jim A.
.
- Follow-Ups:
- Re: DNS issues
- From: Larry Struckmeyer
- Re: DNS issues
- Prev by Date: Re: remove exchange
- Next by Date: agregar sbs 2003 a dominio existente
- Previous by thread: SBS 2003 and Exchange Backup
- Next by thread: Re: DNS issues
- Index(es):
Relevant Pages
|
