Link to home
Start Free TrialLog in
Avatar of DK_Monster
DK_Monster

asked on

Event ID 5719 Could not set up a secure session with... non existant domain

Hi Experts,

My 2003 server acting as the sole DC on the domain is experiencing the following errors during start up, which i think might be the cause of poor network performance.

Event ID 5719
This computer was not able to set up a secure session with a domain controller in domain A19 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.  

The interesting thing is that the domain "A19" is the name of an old domain at the site for which there are no servers remaining. At the time, the domain A19 (which ran on 2000 servers) was migrated to a new domain name while replacing the hardware, and I made an effort of ensuring that the Active directory was correctly migrated, trusts established etc at the time

One should therefore simply expect that i had forgotten to remove some temporary trust with the domain A19, but it appears not. I simply cannot find anything or any setting that refers to the domain A19 anywhere. Not even a search of the registry gives any hit.
Any suggestions how I stop my server from trying to establish "a secure connection" with this non-existent domain at every startup??
Much appreciated.
Avatar of and235100
and235100
Flag of United Kingdom of Great Britain and Northern Ireland image

You don't have any record of the old server in lmhosts, do you?
C:\WINDOWS\system32\drivers\etc
(lmhosts.sam - you can edit it with Notepad)
Avatar of DK_Monster
DK_Monster

ASKER

A good point and suggestion, but no sorry, no entries in Hosts or Lmhosts.sam
You don't have WINS configured in your network properties, do you? (this is highly unlikely anyway if your previous domain was w2k-based)
Do you have RRAS started? If you don't need it - disable it.

This is normally a DNS or WINS issue - where you have a record pointing to the "old" server.
Check your DNS for CNAME and A records pointing to the old server name - or the old domain name...
Found two records pointing to an old retired server, but not referenced with the old domain name. I highly doubt that this would be the problem.
No Wins installed or configured in network properties.
RRAS already disabled

Other suggestions?
ASKER CERTIFIED SOLUTION
Avatar of ChiefIT
ChiefIT
Flag of United States of America 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
Oh, yah. It's configured on the swithces.
I havent had a chance to get to the switches just yet, but I will let you know the result when I do.
How goes the battle?