• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 223
  • Last Modified:

IF AD server goes down across WAN

Corp. is the host for our AD services.  We are a plant across a frame circuit that has a 2k3 server for file sharing.  Last night our circuit died, (corp. does all dhcp/wins/dns also), my clients worked for some time then expired.  I updated the hosts file to do name resolution.  How could I keep my clients from expiring?  If I have a local 2k3 server, how can it provide validation to my clients instead of depending on corp.?
2 Solutions
DCPromo the remote server, add DNS and DHCP to it locally which would then make the remote location able to function whether the link is up or not.
Additionally, configure both the local and the remote servers as Global Catalog servers, as some authentication functionality is dependent on this.

A better security option would be to deploy a DC on separate hardware from your file server, but if you are budget-constrained they can technically co-exist on the same hardware.
Forced accept.

Community Support Moderator

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Tackle projects and never again get stuck behind a technical roadblock.
Join Now