Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Not familiar with 2003 server/Event ID :5513

Status
Not open for further replies.

tedkilroy

Technical User
Dec 8, 2004
49
US
I am running SBS 2003 with 15 computers 2k pro/XP pro. I keep getting this error type for some of the users on a daily basis(just upgraded from NT). I followed the link it provided on the bottom which takes me to Microsoft and it explains the event. Problem, its explanation of a resolution is for nt workstation or server. The symptoms state "a domain controller for your domain could not be located and you have been logged on using a cached information". Any suggestions on how in the resolution section I can do this for 2k/xp computers?
 
Off the cuff it sounds like a DNS problem. Windows 200x domain rely on DNs to communicate with the domain.

So make sure that your clients have thier local TCP/IP properties setup correctly. You will have to point DNS to the new Windows 200x DC. DNS should be pointing to your local DNS server (and not the ISP).

-hope this helps..

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact (Sales@njcomputernetworks.com)
 
No that did not help, the exact words were in the event Id 5513 Source Netlogon:

The computer "Computer" tried to connect to the server \\Domain using the trust relationship established by the SAILS domain. However, the computer lost the correct security identifier (SID) when the domain was reconfigured. Reestablish the trust relationship.

For more information, see Help and Support Center at
 
AS a test, try to remove the computer/server from the domain (make it part of a workgroup). Then re-join the domain.


Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact (Sales@njcomputernetworks.com)
 
Taking them off domain to workgroup and back will destroy their data/pst content. I tried that with one of the first systems here so I learnt that the hard way. Do you know if their is a way to migrate their computer/profile (their listed as local) without taking them off domain?
 
This shows the steps to re-join the computer back to the domain and retain profile...



Another method:

(From an external web site)

have you reconfigured anything or is this a fresh install?

Generally with this error messages these are the steps:

you will have to remove all the computers from the domain delete the computer accounts and add them back.

If you have a lot of clients and you don't want to touch all the machines then you can use the netdom utility
netdom has a switch for join and one for remove

Description of Netdom.exe Syntax and Versions

NetDom examples

At this point I would suggest removing one computer..deleting that computer from Active Directory
and then rejoining it.
If that process works then you have the answer, if not we can think of another way


Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact (Sales@njcomputernetworks.com)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top