Title: Logging into a disconnected DC

Good afternoon..  Hoping someone can give me some pointers here…

We have an office in the UK that is connected back to our US HQ via a VPN link (over the Internet).  At that site, they have a AD DC which is also a GC and DNS server.  This afternoon their VPN link is down (Internet issue) and for some reason they can not authenticate against their local DC for logins…  All clients are Win 2kPro or Win XP Pro and receive an error similar to 'Unable to contact the domain' when they attempt to login…  the users at the site can't even log into the DC machine itself with an administrative domain account (error: Please check that the username and password are entered correctly…  I've verified that the name and password they have are correct and can log into DC's in our site - they've used the credentials in the past and I'm pretty sure that with the number of times they've tried they should've typed the info correctly at least once)

I do check AD replication on a semi-regular basis and have never noticed anything out of the ordinary with that site (dcdiag, netdiag, replmon, and the AD Replication Monitor app)…  The domain is a Win2k Native domain…  I know I've tested disconnected sites before and they've always been able to authenticate locally while the VPN link was down (we have other sites that operate like this) and have never seen this problem… 

At this point I'm just looking for some possibilities or pointers on things to check until the site is back up and I can take a look at that server, Event Logs, etc… 

TIA

Joe Pochedley
A computer terminal is not some clunky old television
with a typewriter in front of it. It is an interface
where the mind and body can connect with the universe
and move bits of it about. -Douglas Adams

Reply via email to