Exchange 2003 SA wont start -- one DC moved to new AD Site and AD Subnet
I have 3 DCs, all GCs.
I created an AD site and subnet for a remote network.
I moved one DC to the new AD site/subnet and it is NOT the FSMO role
owner.
AD DNS has the correct Default-First-Site-Name DNS info (DCs are the
other two, etc.).
Rebooted Exchange server,and get Topology failure, though netdiag and
dcdiag HAVE NO FAILURES!!!
Forced to move the DC back into the original site -- and SA starts
right up.
Any ideas?
Thanks in advance!
I created an AD site and subnet for a remote network.
I moved one DC to the new AD site/subnet and it is NOT the FSMO role
owner.
AD DNS has the correct Default-First-Site-Name DNS info (DCs are the
other two, etc.).
Rebooted Exchange server,and get Topology failure, though netdiag and
dcdiag HAVE NO FAILURES!!!
Forced to move the DC back into the original site -- and SA starts
right up.
Any ideas?
Thanks in advance!
Jay_Jay70
how are your sites structured physically? layout, connectivity subnets etc
After moving a server that contains the GC role, it takes time for Exchange to figure out what hit it. Because Exchange uses the GC heavily, any changes to GC placement normally cause Exchange to hiccup.
Move the server back, both physically and in AD Sites and Services - be sure you re-IP it and delete ALL references to it in DNS by it's old IP (in EVERY container). Restart the server in the new location while pointed to the main site's DNS so it registers properly at the main site. Then repoint it to itself.
Leave things alone for a period - so that KCC can recalculate what happened. You should now be able to restart the Exchange server without too many issues.
Move the server back, both physically and in AD Sites and Services - be sure you re-IP it and delete ALL references to it in DNS by it's old IP (in EVERY container). Restart the server in the new location while pointed to the main site's DNS so it registers properly at the main site. Then repoint it to itself.
Leave things alone for a period - so that KCC can recalculate what happened. You should now be able to restart the Exchange server without too many issues.
ASKER
Jay: Two subnets (in two physical locations), one AD Site (Default-First-Site-Name).
I didn't re-IP anything. All three DCs/GCs kept the same IPs. I simply added a new site called "COLO" and associated it with the new subnet2 definition I created in AD. I then "moved" the machine into the AD site "COLO", and left the other two machines alone.
The DNS immediately changed (because it is AD enabled) and added another site, and removed the subnet2 DC from the Default-First-Site-Name DNS.
So why would Exchange have the topology failure, even after a reboot, even after dcdiag and netdiag passed all tests?
When Exchange SA stopped and failed, I moved the Dc/GC on subnet2 back to "Default-First-Site-Name" and deleted the subnet definition in AD. No IP change needed. Exchange SA immediately started up again once that was complete.
Thats where we stand now.
Netman: If I move that Dc/GC into the new AD site/subnet, Exchange will seize. Any other thoughts?
I didn't re-IP anything. All three DCs/GCs kept the same IPs. I simply added a new site called "COLO" and associated it with the new subnet2 definition I created in AD. I then "moved" the machine into the AD site "COLO", and left the other two machines alone.
The DNS immediately changed (because it is AD enabled) and added another site, and removed the subnet2 DC from the Default-First-Site-Name DNS.
So why would Exchange have the topology failure, even after a reboot, even after dcdiag and netdiag passed all tests?
When Exchange SA stopped and failed, I moved the Dc/GC on subnet2 back to "Default-First-Site-Name" and deleted the subnet definition in AD. No IP change needed. Exchange SA immediately started up again once that was complete.
Thats where we stand now.
Netman: If I move that Dc/GC into the new AD site/subnet, Exchange will seize. Any other thoughts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.