netgeek1
asked on
Login Security Policy Takes Between 10-45 Minutes.
I have an Windows Network running an AD Domain. Some computers, I believe only the Win2K machines, intermittently experience a login problem were the "Applying security policy" screen may 'hang' for approx 10-45 minutes. We have applied nothing other than the default policies on the Domain, and other machines do not experience this problem when this problem is occuring with some machines. It seems to occur at random times thoughout the day. I have also noticed a similar problem on standalone Win2k machines were it may take between 30 seconds and 2 minutes for this screen to disappear.
ASKER
Sorry... Let me answer all those questions.
There is a DNS server. It is on the local subnet.
The clients are configured to use DNS.
As far as all other network settings go, the clients are able connect and use the network, the same as all other clients, after they complete login.
The Domain Controller is on the same subnet as the clients.
Finally, the clients all get there ip from DHCP.
I have noticed a problem similar to this on my home based Win2k machine, which is not on a domain, uses static IP, and no DNS. Of course the time period is only a matter of 30sec-2minutes, but it is also intermittent.
There is a DNS server. It is on the local subnet.
The clients are configured to use DNS.
As far as all other network settings go, the clients are able connect and use the network, the same as all other clients, after they complete login.
The Domain Controller is on the same subnet as the clients.
Finally, the clients all get there ip from DHCP.
I have noticed a problem similar to this on my home based Win2k machine, which is not on a domain, uses static IP, and no DNS. Of course the time period is only a matter of 30sec-2minutes, but it is also intermittent.
I agree with kristinaw, this smacks of DNS, does the event viewer tell you anything, perhaps that it is timing out?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
watching
having same problem with new domain, 2 doz comps are fine, its only the 1 win2k client that has this issue
who ever solves this problem will receive matching points from me, if it also solves mine.
Shep
having same problem with new domain, 2 doz comps are fine, its only the 1 win2k client that has this issue
who ever solves this problem will receive matching points from me, if it also solves mine.
Shep
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:
Answered by: kristinaw
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
JulianCrawford
EE Cleanup Volunteer
I will leave a recommendation in the Cleanup topic area that this question is:
Answered by: kristinaw
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
JulianCrawford
EE Cleanup Volunteer
do you have a dns server in your domain?. is it on your local subnet?
are the clients who are experiencing the problems configured to use the dns server? have all other network settings been doublechecked?
is there a domain controller on the same subnet as the clients experiencing the problems?
are the problem children configured with static addresses or do they get their addresses from a dhcp server?
kris.