<div>
So does this 'server' think its still a member of the domain? or does it access a share on the domain.
</div>


So does this 'server' think its still a member of the domain? or does it access a share on the domain.

<div>
No, the server doesn't exist anywhere, either physically or have an entry in AD. &nbsp;
</div>


No, the server doesn't exist anywhere, either physically or have an entry in AD.  

<div>
It must still be in AD somewhere. Was this server a domain controller did it have roles on it?
</div>


It must still be in AD somewhere. Was this server a domain controller did it have roles on it?

<div>
Pretty normal really - the box XXX is still sitting out on the LAN somewhere although it no longer has a computer account in AD.<br />
<br />
Thanks,<br />
Brian Desmond<br />
Active Directory MVP
</div>


Pretty normal really - the box XXX is still sitting out on the LAN somewhere although it no longer has a computer account in AD.

Thanks,
Brian Desmond
Active Directory MVP

<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
I currently have a domian controller logging the following message:<br />
<br />
The session setup from computer 'XXX' failed becuase the security database does not contain a trust account 'XXX' &nbsp;referenced by the specified computer.<br />
<br />
The issue is that this server account does NOT exist anywhere in AD users and computers. &nbsp;There are also no DNS entries that point to this server name. &nbsp;It must be looking somewhere else in AD to log this corrupt record.<br />
<br />
I have searched through the various posts about this topic, however, no one seems to have a solution for a machine that is non-existant on the domain. &nbsp;Please let me know if you have any ideas. &nbsp;Thanks<br />
<br />
Nate<br />
<br />

</div>
</div>


Hello,

I currently have a domian controller logging the following message:

The session setup from computer 'XXX' failed becuase the security database does not contain a trust account 'XXX'  referenced by the specified computer.

The issue is that this server account does NOT exist anywhere in AD users and computers.  There are also no DNS entries that point to this server name.  It must be looking somewhere else in AD to log this corrupt record.

I have searched through the various posts about this topic, however, no one seems to have a solution for a machine that is non-existant on the domain.  Please let me know if you have any ideas.  Thanks

Nate



Netlogon Error 5723

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).