NETLOGON error report...

[chris.hogg]

Guys

Looking through the logs of our Domain server we are receiving the following error

Source: NETLOGON

event ID: 5719

Type: Error

This computer was not able to set up a secure session with a domain controller in domain **OLD DOMAIN** 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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

As you can see, I've edited out our domain name, but the domain in the error is our OLD domain that no longer exists (could be why it cant be reached...). However nothing should be trying to reach this domain, let alone at 2,3 and 6 am!

Is there any way of tracking down the reason behind this / what could be causing it?

Thanks in advance!

cj

[cluberti]

I would check the obvious things first - make sure you don't have any trusts configured against the old domain in sites & services, make sure you don't have any lmhosts or hosts entries on the box pointing to the old domain, and make sure DNS (and WINS, if in use) contains no references to the old domain.

Also, any scripts or apps that use AD should also be checked to make sure they don't reference the old domain as well.