Netlogon errors???

RKDusRKDus Posts: 20Member ■□□□□□□□□□
Maybe someone can point me in the right direction for this one?

We have a bunch of servers were V2Ved to a different VMware environment and have since been giving RPC Netlogon 5783 and 5719 errors in the System logs. Sometimes it specifies a DC and sometimes just the domain names. All servers are 2k3. I can telnet ok to the DCs over 135. Should I be concerned about this? It doesn't affect all servers that were migrated, only a particular type of application server (8 servers in total), and doesn't seem to have any impact on the server or application functionality, not that I can see anyway. Names have been changed to protect the victims.


Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5783
Date: 5/09/2013
Time: 10:39:14 AM
User: N/A
Computer: Server1
Description:
The session setup to the Windows NT or Windows 2000 Domain Controller \\DC2.domain.com for the domain DOMAIN is not responsive. The current RPC call from Netlogon on \\Server1 to \\DC2.domain.com has been cancelled.

For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.

Comments

  • EssendonEssendon Posts: 4,548Member ■■■■■■■■■■
    Are these VM's from the same domain?
    NSX, NSX, more NSX..

    Blog >> http://virtual10.com
  • RKDusRKDus Posts: 20Member ■□□□□□□□□□
    Hi Essendon

    Yep they are all in the same domain.

    Say you're not a fan of Essendon in the AFL are you? If so I hope you've recovered from the hiding from Richmond last week :)
  • EssendonEssendon Posts: 4,548Member ■■■■■■■■■■
    Check this out (if you havent already) > NETLOGON Error 5783 on Exchange Server 2010 to Server 2008 R2 Domain

    Yes, I'm a huge fan of the Bombers mate. I dont want to talk about that game. You a Tigers fan? I dont want to talk to you if you are, j/k!
    NSX, NSX, more NSX..

    Blog >> http://virtual10.com
  • RKDusRKDus Posts: 20Member ■□□□□□□□□□
    Nah I just arrived in Aus, and went to my first footy game and that happened to be it. Sorry for your troubles though :)

    Thanks for the link I hadn't seen it before. I'm leaning towards it being something to do with network adapters in vCentre, based on the fact that the errors only started after they were migrated. I'm having trouble figuring out why it only happens on a particular kind of application server, they would all have been deployed at the same time though..
Sign In or Register to comment.