NETLOGON event id 5513

[Vladimir Ovchenkov]

I recently purchased a second 2000 server to be located
off site in a "disaster recovery" location. I configured
AD exactly the same way I have the first server setup
(there are no links between the servers, and they are
different brands) .

I restored all my data, but when I take a client off the
production network and put it on the disaster network, I
get NETLOGON event id 5513

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

If any one has any ideas, I would greatly appreciate the
help.. Thank you.

 

[Scott Harding - MS MVP]

These are completely different domains most likely and the computer account
does not exist on this domain. Depending on how you built this server this
is most likely the problem. When you say "restored my data" are you talking
about actual files/folders or are you talking about Active Directory? Also
computer account change their passwords every 2 weeks, if I remember
correctly, so down the road you would have this problem anyways if this
server is never going to talk to the main domain. You basically have to
rejoin the client to this other domain and that error should go away. A
better way would be to have this remote site as another DC on the domain so
that all the computer account and user account password changes would be
replicated and moving the clients to this other site would be relatively
seemless.

 

[S.J.Haribabu]

Hi Vladimir,

Event Message:
================
The computer computer name tried to connect to the server computer name
using the trust relationship established by the name domain. However, the
computer lost the correct security identifier (SID) when the domain was
reconfigured. Reestablish the trust relationship.

Source Event Log Event ID Event Type
==================================
NetLogon System 5513 Error

Explanation:
============
When a Windows 2000 computer joins a domain, it obtains the domain SID from
the domain controller. The computer retains the SID in its local security
database.

User Action:
==========
Remove and then add the computer to the domain again

Thanks,

(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Vladimir]

Thank you for your replies. What I did when I restored,
was restored all data and active directory. So the server
has the same name, domain info, etc as our primary. I
cannot keep the servers connected via network for cost
reasons - this second server is at a secure off site
location for disaster recovery purposes...like a fire or
catastrophe in our primary facility.

-----Original Message-----
These are completely different domains most likely and the computer account
does not exist on this domain. Depending on how you built this server this
is most likely the problem. When you say "restored my data" are you talking
about actual files/folders or are you talking about Active Directory? Also
computer account change their passwords every 2 weeks, if I remember
correctly, so down the road you would have this problem anyways if this
server is never going to talk to the main domain. You basically have to
rejoin the client to this other domain and that error should go away. A
better way would be to have this remote site as another DC on the domain so
that all the computer account and user account password changes would be
replicated and moving the clients to this other site would be relatively
seemless.

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

"Vladimir Ovchenkov"

I recently purchased a second 2000 server to be located
off site in a "disaster recovery" location. I configured
AD exactly the same way I have the first server setup
(there are no links between the servers, and they are
different brands) .

I restored all my data, but when I take a client off the
production network and put it on the disaster network, I
get NETLOGON event id 5513

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

If any one has any ideas, I would greatly appreciate the
help.. Thank you.

.

 

[Cary Shultz [A.D. MVP]]

Scott,

In WINNT the computer account's secret/secure password was changed every
seven days. In WIN2000 it is 60 days.

Cary

These are completely different domains most likely and the computer account
does not exist on this domain. Depending on how you built this server this
is most likely the problem. When you say "restored my data" are you talking
about actual files/folders or are you talking about Active Directory? Also
computer account change their passwords every 2 weeks, if I remember
correctly, so down the road you would have this problem anyways if this
server is never going to talk to the main domain. You basically have to
rejoin the client to this other domain and that error should go away. A
better way would be to have this remote site as another DC on the domain so
that all the computer account and user account password changes would be
replicated and moving the clients to this other site would be relatively
seemless.

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

I recently purchased a second 2000 server to be located
off site in a "disaster recovery" location. I configured
AD exactly the same way I have the first server setup
(there are no links between the servers, and they are
different brands) .

I restored all my data, but when I take a client off the
production network and put it on the disaster network, I
get NETLOGON event id 5513

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

If any one has any ideas, I would greatly appreciate the
help.. Thank you.

 

[summit]

I had a similiar problem a couple of weeks ago. I reestablished the trust
relationship for all the clients, but each time a user logged on, all of
their settings were missing. For example, production software needed to be
reinstalled and our printers and network paths were manually put in place
and they need to be re-pathed. I checked Docs & Settings and there were 2
listings: one for the original "hsimpson" and the new one
"hsimpson.domain.". Fortunately, there are only 8 workstations at my office
and we are not that hi-tech but I am curious as to how I could have
performed this task better. Is there a way I could have kept their user
settings? Is there a way I could have imported or moved their old settings
into the new ones? Thanks.

Thank you for your replies. What I did when I restored,
was restored all data and active directory. So the server
has the same name, domain info, etc as our primary. I
cannot keep the servers connected via network for cost
reasons - this second server is at a secure off site
location for disaster recovery purposes...like a fire or
catastrophe in our primary facility.

-----Original Message-----
These are completely different domains most likely and the computer account
does not exist on this domain. Depending on how you built this server this
is most likely the problem. When you say "restored my data" are you talking
about actual files/folders or are you talking about Active Directory? Also
computer account change their passwords every 2 weeks, if I remember
correctly, so down the road you would have this problem anyways if this
server is never going to talk to the main domain. You basically have to
rejoin the client to this other domain and that error should go away. A
better way would be to have this remote site as another DC on the domain so
that all the computer account and user account password changes would be
replicated and moving the clients to this other site would be relatively
seemless.

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

"Vladimir Ovchenkov"

I recently purchased a second 2000 server to be located
off site in a "disaster recovery" location. I configured
AD exactly the same way I have the first server setup
(there are no links between the servers, and they are
different brands) .

I restored all my data, but when I take a client off the
production network and put it on the disaster network, I
get NETLOGON event id 5513

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

If any one has any ideas, I would greatly appreciate the
help.. Thank you.

.