asked on

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

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.

ASKER CERTIFIED SOLUTION

Darius Ghassem

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

David Blair

ASKER

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)?

Darius Ghassem

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.

David Blair

ASKER

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.

Darius Ghassem

That is fine.