Exchange
--
Questions
--
Followers
Top Experts
Exchange 2010 affected by AD site change
Our AD team recently made some changes on our AD sites and accidently dropping our IPs (PC and Server VLANs) from any scope assignments. In theory this should not have had any effect on Exchange as it should just use a random DC? But our server just stopped transferring emails with the below errors logged. Before we realised that an AD change was made we tried rebooting the server where it just hanged on starting the exchange services. After the scope was fixed and the machine rebooted everything returned to normal. Server running, CAS and Mailbox roles. Why did the scope change have an affect on the server or should I be looking elsewhere for a root cause?
The Third Party Replication Manager could not access Active Directory. Error: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.. Initialization will be retried automatically.
Process MSEXCHANGEADTOPOLOGYSERVIC
Process MSEXCHANGEADTOPOLOGY (PID=1476). The site monitor API was unable to verify the site name for this Exchange computer - Call=DsGetSiteNameW Error code=800703e5. Make sure that Exchange server is correctly registered on the DNS server.
The Active Directory system configuration session couldn't be retrieved.
Exception message: "The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.".
Error 0xfaf connecting to Active Directory.
Thanks!
The Third Party Replication Manager could not access Active Directory. Error: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.. Initialization will be retried automatically.
Process MSEXCHANGEADTOPOLOGYSERVIC
Process MSEXCHANGEADTOPOLOGY (PID=1476). The site monitor API was unable to verify the site name for this Exchange computer - Call=DsGetSiteNameW Error code=800703e5. Make sure that Exchange server is correctly registered on the DNS server.
The Active Directory system configuration session couldn't be retrieved.
Exception message: "The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.".
Error 0xfaf connecting to Active Directory.
Thanks!
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Thanks for the response Drashiel. But should the server not have located the best/nearest DC and used that even though it was not part of a site(we are connected to the closest site with a 300meg WAN link)? (No other services was affected, file, printer, SQL servers were all fine) I failed to mention this server is part of a DAG with the partner server sitting in another site. The DAG did fail over during the reboot but clients could still not connect to it, maybe because they did not belong to any site...
SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Another thing i have found out in the meantime is that Exchange 2010 uses AD Site for email routing.
Not enough technical detail provided.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Exchange
--
Questions
--
Followers
Top Experts
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.