Solved

Netlogon Event ID 5783 - Terminal Server Hangs at Loading Personal Settings

Posted on 2008-10-29
5
3,103 Views
Last Modified: 2013-11-21
DC and TS are on the same LAN segment and running 2K3 (R1 for the DC and R2 for the TS).  Out of the blue an event 5783 is logged (below) and from then on no clients can connect to the terminal server until it is rebooted.  When they try it just hangs at "Loading your Personal Settings.  The server will literally go months without incident and rebooting always fixes this problem.  The terminal server is a DNS server but not a domain controller.  (Best practices for DNS settings also appreciated  for this scenario.)

Event Type:      Error
Event Source:      NETLOGON
Event Category:      None
Event ID:      5783
Date:            10/29/2008
Time:            8:55:37 AM
User:            N/A
Computer:      TS
Description:
The session setup to the Windows NT or Windows 2000 Domain Controller \\DC.corp.local for the domain CORP is not responsive.  The current RPC call from Netlogon on \\TS to \\DC.corp.local has been cancelled.
0
Comment
Question by:David Blair
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
5 Comments
 
LVL 59

Accepted Solution

by:
Darius Ghassem earned 500 total points
ID: 22831261
Does this server point to itself for DNS? You should point it to the DC for DNS resolution. Having this server a DNS server when it is a Terminal server is a bad idea because of security issues.

http://www.eventid.net/display.asp?eventid=5783&eventno=1024&source=NETLOGON&phase=1
0
 
LVL 1

Author Comment

by:David Blair
ID: 22831336
The server was pointing to itself with the DC as a secondary.  I switched these.  Should I remove it's own IP entirely and only point to a DC?  How about entering use the IP of two DC's (I have one at another site)?
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 22831367
Yes, do that. Have both DCs listed in the DNS settings of the TS server. Once you have these setting in do a ipconfig /flushdns then a ipconfig /registerdns. Give the server a restart.
0
 
LVL 1

Author Comment

by:David Blair
ID: 22831439
Got it.  Will reboot this weekend.  How should I configure DNS suffixes?  Currently corp.local is manually entered on both the TS and DC, among other servers.  Is this cool?

Because this is such an infrequent and serious error, I'm going to leave this question open until the weekend in case there are any additional suggestions.
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 22831474
That is fine.
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

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

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found listed in my profile here: http:…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…

749 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