J
J. Knapp
We have an aging domain controller, so we installed a new 4 processor box,
installed Win2KAS on it, did the DCPROMO bit and the box seems fine.
Except it takes 5 minutes to logon.
(This also happens on a regular server we're using for Terminal Services
when its a member of the domain; when it's not in the domain, logon works
just fine -- but then we don't have domain services, so we had to manaully
duplicate logins, etc.)
The original server logs in just fine in a timely fashion.
Any workstation in the domain logs on right away, logon script runs moments
after the "Applying Personal Settings" goes away.
On the server, it seems like something is timing out after 300 or 600
seconds and then the desktop comes up.
Any pointers on what could be hanging things up?
DNS seems to be working fine, its running on both machines; so I would
assume its not a can't find DNS issue, since its running on the local
machine...?
Many thanks in advance,
Jeff
installed Win2KAS on it, did the DCPROMO bit and the box seems fine.
Except it takes 5 minutes to logon.
(This also happens on a regular server we're using for Terminal Services
when its a member of the domain; when it's not in the domain, logon works
just fine -- but then we don't have domain services, so we had to manaully
duplicate logins, etc.)
The original server logs in just fine in a timely fashion.
Any workstation in the domain logs on right away, logon script runs moments
after the "Applying Personal Settings" goes away.
On the server, it seems like something is timing out after 300 or 600
seconds and then the desktop comes up.
Any pointers on what could be hanging things up?
DNS seems to be working fine, its running on both machines; so I would
assume its not a can't find DNS issue, since its running on the local
machine...?
Many thanks in advance,
Jeff