[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 387
  • Last Modified:

Clients won't login to local domain controller when WAN link is down

I have a Win2K AD domain in a school district, and have multiple sites configured in AD, each with their own domain controller. These sites are connected physically by T1. When the T1 is up and operational, the clients login just fine, and by running a script, I can tell that they are authenticated by the local on-site domain controller. But when the WAN is down, they can't log in at all. The local DC's are configured as GC controllers, and each site has all their resources local. I designed it this way so they would be able to continue to work when the WAN link was unavailable. But it's not working. Something is still tying them to the main site, where the PDC emulator resides. Shouldn't I be able to log these clients in with local resources when the WAN is down?
0
David Goldsmith
Asked:
David Goldsmith
  • 5
  • 4
1 Solution
 
Gareth GudgerCommented:
Yes you should.

Are these all separate domains? Or is it the same domain but with a DC in each location?

Also, how are you binding the NICs in the DCs? I assume these are multihomed to allowed internet access or do they have a different gateway for that purpose?
0
 
David GoldsmithAuthor Commented:
Single domain, separate DC in each location. Servers not multi-homed, they have a gateway to get back to the District Office and on out to the internet.
0
 
Gareth GudgerCommented:
Is a DNS server operating locally on the local DCs? And are the clients using the local DNS if you check their IP info?
0
Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

 
David GoldsmithAuthor Commented:
No local DNS, only primary DNS servers at main site. Is that it? I have to have DNS services running on each remote DC?
0
 
Gareth GudgerCommented:
Yes if you lose DNS capabilities you wont be able to log on. Set up a secondary DNS server at each local location (just put it on with the DC) and specify the secondary DNS server as an additional DNS server in the clients IP settings.
0
 
David GoldsmithAuthor Commented:
As I'm asking that question, it's becoming obvious to me that I would definitely need DNS at the site in order to route network requests internally...either that, or implement a local hosts file on the clients for internal requests.
0
 
Gareth GudgerCommented:
Depends on the number of clients you have at each location I guess. I would say if you have more than 5 to 10 use a DNS server...less headache.

Also a DNS server in each location should improve performance (as long as the local DNS server you implement is listed first in the clients IP settings with the remote second).
0
 
David GoldsmithAuthor Commented:
Thanks, that was a forehead slapper...I should have known that one...
0
 
Gareth GudgerCommented:
Happens to all of us. :)
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

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