6 replies
by techkid
There isn't anything you can do in this setup. Workstations need to contact the domain dns servers for logon, if they can't contact the dns server, they will wait for a timeout and used cached credentials.
This was the same with Windows NT. No domain controller onsite and the clients can't find one... you get the "domain controller could not be found... please contact network administrator..." error message.
Don't know how your vpn is setup but doesn't the internet access go down when the vpn goes down for these offices?
The only option is to put a domain controller on site.
by cg it
by nico baggus
How aboutr allowing to do a (LM)HOST lookup for
your domain controller only.
It would still allow to reach your domain
controller and (in the process) pull up your VPN
link. When that link is there you can continue.
Kind regards,
Nico Baggus
by jt
the quickest and dirtiest hack of them all for this would be to
put entries for each machine in the hosts file (c:
\windows\system32\drivers\ets\hosts). it's tedious (assign
each machine a static IP, then put the entries from all the
machines from that network into a hosts file, copy the hosts file
to each machine) but it will work.
The best solution would be to deploy a domain controller at
each site (with management it's almost never possible!)
by cweaver
by jwahau
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending