I'm currently trying to join two forests together between a Windows 2008 R2 and Windows 2012 R2 domain controller. The trust being set up is a two-way transitive trust between both forests and domain controllers. However, at the end of the wizard, it would fail with the following error:
"The operation failed. There error is: There are currently no logon servers available to service the logon request."
Despite the error, I could see the trust is created on both sides of the domain controllers. But when trying to validate the trust from the Domain and Trust properties, it would return the following error:
"The outgoing trust was successfully validated. The secure channel (SC) reset on Active Directory Domain Controller \\TVH-R2D2.tvh.ad of domain tvh.ad to domain tvh2_domain failed with error: There are currently no logon servers available to service the logon request."
Both domain controllers are able to see each other, however, when setting user rights for a folder it could not find any users from the trusted domain. Currently at a loss on what the issue or cause of the issue is.
Here are some notes and steps that have been tried:
- Windows 2012 R2 domain controller is at a Windows 2003 forest level and Windows 2008 R2 domain level.
- Windows 2008 R2 domain controller is at a Windows 2008 R2 forest level and Windows 2008 R2 domain level.
- Added the trusted domain in the DNS as a secondary zone in the DNS manager with read only access (from both DCs).
- Added IP address of the trusted domain controller as a DNS forwarder on both servers.
- Added IP address of each trusted domain controller as a secondary DNS on network adapter of both servers.
- Both domain controllers can ping each other via hostname and FQDN, and to the domain name itself.
- There was an previous orphaned domain controller in AD that was used for testing, but have been removed via ADSI Edit.
- Haven't tried raising forest functional level of the Windows 2012 R2 server from Windows 2003 to Windows 2008 R2 level yet due to concerns of possible conflicts with an Exchange 2003 server in the environment.
Any help or suggestions are appreciated.
Thanks in advanced!