asked on
Trust Relationship issue from the member server to the Domain
Hi Support
My Environment have 1 AD Server , 2 Join AD server ( 1 Production and 1 DR) , Application cannot work when change the server hostname , in this environment when i put the DR server hostname same as production server it will detect hostname already exist .
Situation
When Production server need to swing to DR server i have to shutdown production server and rename the DR server same as production server name . during testing in DR i got issue that i cannot login to DR server using domain ID , its show the computer have a trust security error
Can you please help on how to solve this issue
Thanks
My Environment have 1 AD Server , 2 Join AD server ( 1 Production and 1 DR) , Application cannot work when change the server hostname , in this environment when i put the DR server hostname same as production server it will detect hostname already exist .
Situation
When Production server need to swing to DR server i have to shutdown production server and rename the DR server same as production server name . during testing in DR i got issue that i cannot login to DR server using domain ID , its show the computer have a trust security error
Can you please help on how to solve this issue
Thanks
Windows Server 2003Active DirectoryDisaster Recovery
Last Comment
9660kel
ASKER
ASKER
Level Date and Time Source Event ID Task Category
Error 7/6/2012 9:15:02 PM NETLOGON 5721 None "The session setup to the Windows NT or Windows 2000 Domain Controller \\server.abc.com for the domain abc failed because the Domain Controller did not have an account server$ needed to set up the session by this computer server.
ADDITIONAL DATA
If this computer is a member of or a Domain Controller in the specified domain, the aforementioned account is a computer account for this computer in the specified domain. Otherwise, the account is an inter domain trust account with the specified domain.
Error 7/6/2012 9:15:02 PM NETLOGON 5721 None "The session setup to the Windows NT or Windows 2000 Domain Controller \\server.abc.com for the domain abc failed because the Domain Controller did not have an account server$ needed to set up the session by this computer server.
ADDITIONAL DATA
If this computer is a member of or a Domain Controller in the specified domain, the aforementioned account is a computer account for this computer in the specified domain. Otherwise, the account is an inter domain trust account with the specified domain.
UNC Suffix needs to be added.
ASKER
How to Add the UNC Suffix
ASKER
Thanks
The server account for your secondary DC has a SID attached to it and the recovery server has a different SID, which is interpreted as a "rogue" server as the account does not match.
What are you trying to do with this arrangement that adding an account to the primary domain for the recovery server conflicts with?
What are you trying to do with this arrangement that adding an account to the primary domain for the recovery server conflicts with?
ASKER
This is due to the sap application that cannot work when we restore the db from production server to the dr. its cant recognize the dr server hostname. to only works is rename the dr server hostname similar to the production server hostname
That is a tough spot, I don't really know how to work around it without doing something horrific to the secondary DC account.
ASKER
Is there any solution to the second ad that can make both site have the same hostname.
Two Computers in the same domain with same hostname ....?? Not Possible they will throw name conflict
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Can you please provide the full error from the event viewer?
Thank you.