Re: Active directory and dead WAN connection
- From: "OscarSotoCL" <oscar.soto@xxxxxxxxxxxxxxxx>
- Date: Thu, 26 Oct 2006 15:59:19 -0300
Hi:
Do you have DNS installed on the remote sites?. Normally you need something like this for WAN Sites:
First:
- One Active Directory Site for the central site and one for each WAN site, with subnets definition
Second:
- Central Site: One or Two Domain Controllers with DNS installed
- Wan Sites: One or Two Domain Controllers with DNS installed, all clients configured to connect to the local DNS
With this configuration you could speed up the logon process in the remote sites.
Hope this helps you.
Oscar Soto Casali
MVP Directory Services
"igolo" <mikef@xxxxxxxxxxxx> escribió en el mensaje de noticias:1161888347.330929.302230@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have several remote sites running server 2003 with AD configured as
child domains of the parent domain corp.work.com
The remote sites have a broadband WAN connect to the host site. When a
WAN connection goes down at one of the remote sites the PDC takes about
20 minutes to startup - hanging at the preparing network connections
window. Also adding workstations to the domain takes about 15 minutes.
I thought the purpose of having a copy of AD local to each remote sites
would reduce domain authentication time if the WAN connectio went down.
How can improve the local login time for the remote sites when the WAN
connection breaks?
.
- Follow-Ups:
- Re: Active directory and dead WAN connection
- From: igolo
- Re: Active directory and dead WAN connection
- References:
- Active directory and dead WAN connection
- From: igolo
- Active directory and dead WAN connection
- Prev by Date: Re: Desktop Appearance::Normal Login versus RDP
- Next by Date: Re: ADAM object auditing
- Previous by thread: Active directory and dead WAN connection
- Next by thread: Re: Active directory and dead WAN connection
- Index(es):
Relevant Pages
|
