Re: Win2k3 Active Directory dns, dhcp errors. All linked together but can't figure it out.

Upon a fresh reboot of SF DC, here are many of the warning and error
Event ID's for the SF DC.

Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40960
Date: 12/14/2005
Time: 12:44:13 PM
User: N/A
Computer: SF-SERVER-02
Description:
The Security System detected an authentication error for the server
ldap/sf-server-02.netdomain.local. The failure code from
authentication protocol Kerberos was "There are currently no logon
servers available to service the logon request.
(0xc000005e)".

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0 ^..À


Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40960
Date: 12/14/2005
Time: 12:44:16 PM
User: N/A
Computer: SF-SERVER-02
Description:
The Security System detected an authentication error for the server
LDAP/SF-SERVER-02. The failure code from authentication protocol
Kerberos was "There are currently no logon servers available to service
the logon request.
(0xc000005e)".

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0 ^..À

Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40960
Date: 12/14/2005
Time: 12:44:13 PM
User: N/A
Computer: SF-SERVER-02
Description:
The Security System detected an authentication error for the server
ldap/sf-server-02.netdomain.local. The failure code from
authentication protocol Kerberos was "There are currently no logon
servers available to service the logon request.
(0xc000005e)".

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0 ^..À


Event Type: Error
Event Source: DhcpServer
Event Category: None
Event ID: 1059
Date: 12/14/2005
Time: 12:45:30 PM
User: N/A
Computer: SF-SERVER-02
Description:
The DHCP service failed to see a directory server for authorization.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 3a 20 00 00 :

Event Type: Information
Event Source: DhcpServer
Event Category: None
Event ID: 1044
Date: 12/14/2005
Time: 12:45:30 PM
User: N/A
Computer: SF-SERVER-02
Description:
The DHCP/BINL service on the local machine, belonging to the Windows
Administrative domain netdomain.local, has determined that it is
authorized to start. It is servicing clients now.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 ....

Event Type: Error
Event Source: DhcpServer
Event Category: None
Event ID: 1059
Date: 12/14/2005
Time: 12:45:58 PM
User: N/A
Computer: SF-SERVER-02
Description:
The DHCP service failed to see a directory server for authorization.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 3a 20 00 00 : ..

Event Type: Warning
Event Source: smtpsvc
Event Category: None
Event ID: 2012
Date: 12/14/2005
Time: 12:46:01 PM
User: N/A
Computer: SF-SERVER-02
Description:
SMTP could not connect to the DNS server '127.0.0.1'. The protocol used
was 'UDP'. It may be down or inaccessible.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d5 04 00 00 Õ...

Event Type: Warning
Event Source: smtpsvc
Event Category: None
Event ID: 2012
Date: 12/14/2005
Time: 12:46:01 PM
User: N/A
Computer: SF-SERVER-02
Description:
SMTP could not connect to the DNS server '127.0.0.1'. The protocol used
was 'UDP'. It may be down or inaccessible.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: d5 04 00 00 Õ...

Event Type: Error
Event Source: smtpsvc
Event Category: None
Event ID: 2013
Date: 12/14/2005
Time: 12:46:01 PM
User: N/A
Computer: SF-SERVER-02
Description:
SMTP could not connect to any DNS server. Either none are configured,
or all are down.

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: W32Time
Event Category: None
Event ID: 17
Date: 12/14/2005
Time: 12:47:04 PM
User: N/A
Computer: SF-SERVER-02
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the
manually configured peer 'time.windows.com,0x1'. NtpClient will try the
DNS lookup again in 15 minutes. The error was: No such service is
known. The service cannot be found in the specified name space.
(0x8007277C)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 17
Date: 12/14/2005
Time: 12:47:16 PM
User: N/A
Computer: SF-SERVER-02
Description:
Time Provider NtpClient: An error occurred during DNS lookup of the
manually configured peer 'tock.usno.navy.mil,0x1'. NtpClient will try
the DNS lookup again in 15 minutes. The error was: No such service is
known. The service cannot be found in the specified name space.
(0x8007277C)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: NTDS General
Event Category: Service Control
Event ID: 1000
Date: 12/14/2005
Time: 12:43:11 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SF-SERVER-02
Description:
Microsoft Active Directory startup complete, version 5.2.3790.1830

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 2087
Date: 12/14/2005
Time: 12:44:43 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SF-SERVER-02
Description:
Active Directory could not resolve the following DNS host name of the
source domain controller to an IP address. This error prevents
additions, deletions and changes in Active Directory from replicating
between one or more domain controllers in the forest. Security groups,
group policy, users and computers and their passwords will be
inconsistent between domain controllers until this error is resolved,
potentially affecting logon authentication and access to network
resources.

Source domain controller:
wy-server-01
Failing DNS host name:
f69df8a0-bcb1-4257-acee-a298e8dcbaeb._msdcs.netdomain.local

NOTE: By default, only up to 10 DNS failures are shown for any given 12
hour period, even if more than 10 failures occur. To log all
individual failure events, set the following diagnostics registry value
to 1:

Registry Path:
HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC
Client

User Action:

1) If the source domain controller is no longer functioning or its
operating system has been reinstalled with a different computer name or
NTDSDSA object GUID, remove the source domain controller's metadata
with ntdsutil.exe, using the steps outlined in MSKB article 216498.

2) Confirm that the source domain controller is running Active
directory and is accessible on the network by typing "net view
\\<source DC name>" or "ping <source DC name>".

3) Verify that the source domain controller is using a valid DNS
server for DNS services, and that the source domain controller's host
record and CNAME record are correctly registered, using the DNS
Enhanced version of DCDIAG.EXE available on
http://www.microsoft.com/dns

dcdiag /test:dns

4) Verify that that this destination domain controller is using a
valid DNS server for DNS services, by running the DNS Enhanced version
of DCDIAG.EXE command on the console of the destination domain
controller, as follows:

dcdiag /test:dns

5) For further analysis of DNS error failures see KB 824449:
http://support.microsoft.com/?kbid=824449

Additional Data
Error value:
11004 The requested name is valid, but no data of the requested type
was found.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: NTDS General
Event Category: Service Control
Event ID: 1394
Date: 12/14/2005
Time: 12:48:52 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: SF-SERVER-02
Description:
All problems preventing updates to the Active Directory Database have
been cleared. New updates to the Active Directory database are
succeeding. The Net Logon service has restarted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... One thought, when you introduced the Windows Server 2008 and before making them DC's, did you extend the schema on the SBS 2003 server? ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Big trouble with DC in China
    ... > Since then, this server has so may errors in the event logs (KCC, ... > DNS, FRS) that I wouldnt know where to start. ... > Source domain controller address: ...
    (microsoft.public.windows.server.active_directory)