Link to home
Start Free TrialLog in
Avatar of Mark
MarkFlag for Ireland

asked on

Not able to logon to Windows Server 2008 R2 Enterprise Domain Controller

Hi,

I'm currently in the middle of a Disaster Recovery non-functional test. We have an isolated VLAN setup that will not affect production. We have failed over a large number of production servers and two domain controllers using site recovery manager. Each domain controller is part of an different Forest namespace. Before SRM each domain controller had it's DNS information updated in the Advanced TCP/IP Settings for the network adapter.

DNS server addresses, in order of use
IP Address (Current Production IP Address
IP Address (DR IP Address that will be used once the Domain controller  has been replicated using SRM)
IP Address (Of another production Domain controller
IP Address (Local Host IP Address 127.0.0.1

We can logon one domain controller but can't logon to the another. The logon is using hanging at Welcome then times out. I've attached a print screen. The following registry fix was also applied to production before replication.
domaincontroller1.JPG
domaincontroller2.JPG
domaincontroller3.JPG
ASKER CERTIFIED SOLUTION
Avatar of Aland Coons
Aland Coons
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
In a DR scenario you should NOT be recovering domain controllers using VMware, unless you have DC cloning enabled (server 2012). In a DR scenario you should have LIVE DC's that are in the DR site. when you use SRM you only recover member/applicaiton servers. Doing it this way will mitigate any computer/policies/replicaiton issues which will stop you from logging in.

Will.