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
makel2Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Aland CoonsSystems EngineerCommented:
As a domain controller running DNS I configure each server with 127.0.0.1 as the first (and sometimes only) DNS address as this will work reliability regardless of what active IP address the adapter gets.

I think you're on the right track.  You may also have some services set to run with domain credentials.

I'm curious to know what the error looks like when it "times out".  

If the server has a valid IP address can you manage it across a LAN connection. Is there anything in the log files to provide direction?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Will SzymkowskiSenior Solution ArchitectCommented:
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.
1
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.