Quantcast
Viewing all articles
Browse latest Browse all 31638

AD/DNS Server authentication issue

Hi everyone,

I apologize if it seems like I am replicating a question that may have been answered, but the threads I've seen don't appear to include my particular situation.

I have inherited a system from my co-worker who has taken a new job.  We have two physical servers, both running Hyper-V.  Note that all of our servers are Windows Server 2008.  On physical server 1 we have the virtual primary domain controller with DNS server, and on physical server 2 we have the virtual secondary domain controller with DNS server.  They each point to themselves as the primary DNS, and the other as the secondary DNS (each configured using the actual IPs, not 127.0.01).  All other virtual servers across these two machines point to these as their DNS servers, and everything normally runs smoothly.

Then the power went out =P.

Because of my inexperience with the system, I am unfamiliar with some of the idiosyncrasies.  So, when I brought up the physical servers, the secondary domain controller came up first, then the primary came up (I was originally told this would be ok).  The websites hosted on the system were working just fine as far as I could tell, and I could access the Internet from my computers hooked up to the domain, so I went home.

However, the servers were not actually in full working order.  It turns out that my machine at work was off the Internet, and some users were no longer able to Remote Desktop into a different machine as a result of the firewall.  When I opened up the firewall for the RDP service to the Public, I could log in from my work machine, but using only the Domain, I could not.  Bearing in mind that I could normally Remote Desktop into this machine using just the Domain-accessible firewall.

My co-worker told me that sometimes authentication issues can occur when the secondary domain controller is brought up before the primary domain controller, and that it usually fixes itself. However, it had been 12 hours since I brought them up, and they showed no signs of fixing themselves.

I'm wondering: has anyone else has encountered these strange issues before?  How might I be able to configure things differently to avoid them in the future?  We are getting new hardware soon and I want to try configuring things to be as "happy" as possible =).

Thanks!



Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>