Re: slow logon/authentication

Tech-Archive recommends: Fix windows errors by optimizing your registry

Manny,

regarding 2., review
http://www.microsoft.com/technet/security/prodtech/windows2000/w2kccadm/adsites/w2kadm37.mspx
In essence, unless you have plenty of available bandwidth (and low latency)
between two locations, you should designate them as two separate Active
Directory sites. This will localize authentication traffic and optimize
replication traffic between domain controllers.

3. you can quickly verify this by running SET LOGONSERVER at the Command
Prompt

What method are you using to rename workstations and what is the error you
are receiving when performing this procedure at the second location?

hth
Marcin

"Manny" <Manny@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6AC0C297-9EA6-4C96-A25E-E34F81F86AAC@xxxxxxxxxxxxxxxx
Marcin,

Thank you for the help. Below are the anwers:
1. The slow authentication is at both locations.

2. Please elaborate. I do not understand your question regarding
creating/configuring additional site corresponding to the second location.
Sorry.

3. How do I verify which domain controller is contacted during logon or
workstation rename?

4. The DNS at the second location is set for Active Directory Integrated
just like the other 2 DCs. The clients are set to receive DNS services
from
the server at the second location, and it has the other 2 as
secondary/backups.

Thanks,
Manny


"Marcin" wrote:

Manny,
where are you observing the "slow authentication"? On a client computers
at
one/both of the locations? Have you created/configured additional site
corresponding to the second location? Have you verified which domain
controller is contacted during logon or workstation rename? What's the
DNS
configuration of the third DC and client at its location?

Marcin

"Manny" <Manny@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F859F372-1A10-4A46-AF16-AD4D6E5CA292@xxxxxxxxxxxxxxxx
Since I added a Windows 2003 Server R2 as a domain controller along
with
my 2
original Windows 2003 Servers (original release), I've noticed that it
takes
quite a bit longer for the computer desktop to appear once you enter
your
network credentials. The 2 original DCs are in one physical location
while
the new 2003 R2 DC is in another physical location and connected via
Internet
thru a VPN tunnel.

Aside from the slow authenication, we also noticed that we cannot
rename
workstations at the location with the 2003 R2 DC, while changing
workstation
names at the original location is fine.

Thanks for any help.

Manny





.

Relevant Pages

  • Re: slow logon/authentication
    ... Thanks Marcin. ... creating/configuring additional site corresponding to the second location. ... controller is contacted during logon or workstation rename? ...
    (microsoft.public.windows.server.active_directory)
  • Re: slow logon/authentication
    ... The slow authentication is at both locations. ... The DNS at the second location is set for Active Directory Integrated ... controller is contacted during logon or workstation rename? ... configuration of the third DC and client at its location? ...
    (microsoft.public.windows.server.active_directory)