Multiple Event Errors on member server 2003

35 pts.
Tags:
DNS management
Event ID
Member Servers
Windows Server 2003
Windows Server 2003 administration
Windows Server 2003 Domain Controller
I have a member server that is running very slowly - slow to log on, slow to access shared files from clients, and won't connect to internet. After reviewing the event log, I have discovered these errors:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 6/23/2010
Time: 5:53:17 PM
User: N/A
Computer: APPLICATIONSERV
Description:
This computer was not able to set up a secure session with a domain controller in domain XXXX due to the following: 
There are currently no logon servers available to service the logon request.  
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  
ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7034
Date: 6/24/2010
Time: 7:02:18 AM
User: N/A
Computer: APPLICATIONSERV
Description:
The QBCFMonitorService service terminated unexpectedly.  It has done this 1 time(s).
Event Type: Warning
Event Source: DnsApi
Event Category: None
Event ID: 11164
Date: 6/24/2010
Time: 7:50:27 AM
User: N/A
Computer: APPLICATIONSERV
Description:
The system failed to register host (A) resource records (RRs) for network adapter
with settings:
   Adapter Name : {D0E1D624-E3B0-4DE2-97EB-8FB68DFE1D40}
   Host Name : Applicationserver
   Primary Domain Suffix : XXXX.local
   DNS server list :
     10.0.1.3
   Sent update to server : <?>
   IP Address(es) :
     xx.x.x.xxx
 The reason the system could not register these RRs was because either (a) the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not accept dynamic updates.
 To register the DNS host (A) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 14
Date: 6/24/2010
Time: 6:04:32 AM
User: N/A
Computer: APPLICATIONSERV
Description:
The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in 960 minutes.
I've tried to Google the errors and they seem related, but I don't know how to resolve them.  Any help would be appreciated.


Software/Hardware used:
Windows Server 2003
ASKED: June 24, 2010  3:09 PM
UPDATED: June 24, 2010  7:45 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

try to change parts of hardware,
network card
or try to connect to internet via usb network card.
have similar problem in 2006 – “The system failed to register host (A) resource records (RRs) for network adapter”
resolved by changing cables, router, network card
hope this helps good luck

Discuss This Question: 6  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • carlosdl
    We had this exact problem (same sequence of events) about a week ago on a W2K3 r2 server, and it was causing severe problems to a couple of networking applications. As this was critical and a quick solution wasn't found, infrastructure people scheduled a maintenance window and re-formatted the server. The problem got solved (but unfortunately the root cause wasn't identified), so, in our case it wasn't a hardware issue .
    65,110 pointsBadges:
    report
  • Labnuke99
    Check name resolution settings on the server. You may also try adding the DC's name/IP to the hosts and/or lmhosts file to give a little help to the name resolution process.
    32,960 pointsBadges:
    report
  • Labnuke99
    Also, did remove and re-add the member server to the domain? Remember to wait for any replication to complete after removing and re-adding the server.
    32,960 pointsBadges:
    report
  • ODSTech
    Batye got me thinking about it and I quickly installed a USB wireless which seemed to resolve the issue. Guessing that means a hardware issue?????
    35 pointsBadges:
    report
  • carlosdl
    Not necessarily. It still could be a configuration issue. The USB adapter might have resolved the internet connectivity issue, but did the other symptoms you mentioned get resolved too ?
    65,110 pointsBadges:
    report
  • ODSTech
    Think it was a bad nic. Completed all updates using wireless. Removed wireless and changed patch cable. Same issues as before. Tried different NIC and problem resolved just as with the wireless. FWIW, all the errors resolved with the wireless also. Thanks for the tips to check hardware. Know its not always the answer, but worked this time.
    35 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following