Link to home
Start Free TrialLog in
Avatar of mmoya
mmoyaFlag for United States of America

asked on

Event ID 5783 NetLogon Active Directory 2003 and Application Server 2008 R2

Hello expert team,

I sporadically experience event ID 5783 netlogon issue on some of our 2008 r2 application servers. For some reason it only occurs on 2008 R2 servers. Any thoughts?

Application server = 2008 R2 with SP1
Active Directory = domain and functional level is 2003.

Error: Event ID 5783 NETLOGON
The session setup to the Windows NT or Windows 2000 Domain Controller \\DC01.ourad.COM for the domain CORP is not responsive.  The current RPC call from Netlogon on \\serverbox01 to \\DC01.ourad.COM has been cancelled.

Thank you!
Avatar of Sajid Shaik M
Sajid Shaik M
Flag of Saudi Arabia image

Netlogon Event ID 5783

 The source server listed in the error message was unable to complete a remote procedure call (RPC) call to the destination server. Most commonly, this means that either the source server could not locate the server in DNS or the RPC interface on the destination server is not working.

 If the source server could not locate the server in DNS, troubleshoot Active Directory replication failure due to incorrect DNS configuration.

If this is not a DNS problem, troubleshoot RPC problems.

check the dns record properly... all the best
 
Avatar of mmoya

ASKER

DNS settings are set-up correctly. I can resolve the application server from the DC and vice versa. RPC service on the application service is also running set to automatic, although RPC locator is set to manual. Are there any other steps I need to take? Thank you again.
try the DNS stale record scavenging...
Avatar of mmoya

ASKER

and set it to what though?

The record time stamp of the application server in our DNS is 10/06/2011 2:00PM and TTL is set to 0:0:20:0


time stamps are applied to records when ageing\scavenging is applied ...So if you checked dns straight away you will see no difference. You will have to wait 8 days before they are scavenged....(or however many days you have set the scavenging period to on the server properties).

try

First right click the DNS Server root folder (server name), and use refresh a couple of times, then Update Server Data, if this doesn't clean enough the data, then use Clear Cache, try using Scavenge Stale Resource Records the last if necessary, this last may take sometime depending the size of your network.
Avatar of mmoya

ASKER

I have a question, what does that update server data do? I just wanted to assess if there are any impacts first.

Question - what makes you think that it is scavenging related issue? Can you please explain why? Ive been trying to troubleshoot this issue and havent had any luck so far..

Appreciate all your help!
good becouse may be your DNS records having similar name stale records... it just a hope....


as per microsoft this could be an issue on dns server or RPC at client side... hence  as u said there is no issue at DNS so did u check the RPC service and it's dependant services... ? is the DFS service is there ?

Avatar of mmoya

ASKER

Our DNS infrastructure here uses a load balancing and DCs don't point to itself (don't ask me why because it is just the way they want it to be designed. Technically I don't agree to it but that is a different story). Could that be the reason why?

Did you mean FRS (not DFS?), RPC service on the problematic DC has FRS as its dependencies.

ASKER CERTIFIED SOLUTION
Avatar of Sajid Shaik M
Sajid Shaik M
Flag of Saudi Arabia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial