Sign in to vote. Hi I have about 7, Win XPsp3 stations in a corporate domain. Users experience a very slow logon of minutes. Sunday, February 12, PM. Dude, the best way to debug a problem like this would be to use the "Sysinternals Suite" and use the Process Monitor tool procmon within this you can trace the next boot, this will show you what is happening all under the hood, so you will be able to trace the slowness from the timestamp records, then see the previous event to that event and see what is causing the problem.
Hope this all makes sense! Monday, February 13, AM. I forgot about procmon. I will give this a try. No worries Options - Enable Boot Logging If you know its GINA thats waiting for something filter on that, look whats happening just before it, and then you should catch the suspect Helping to find the needle in the hay stack : Please vote if helpful. Edited by adamgovuk Monday, February 13, PM. Everything is exactly the same.
Just the new machine. Very strange. I am trying the scripts removal today to see if that does anything. If not, I will try making static ips. I took away the old logon scriots and replaced with gpo. Also gave static ip. Still doing the same thing. Have one windiws server and a server. Sometimes after welcome screen goes away it just turns black and stays there for an hour never brining up desktop.
I had dhcp coming from the rputer, I just changed it to come from the server. Now the 2 windows 10 machines stay black after logon for exactly 5 minutes before they come on instead of sometimes not coming on at all or taking 30 minutes. I found this to also fix my issue, sometimes found that the startmenu would not be able to click on. Just wanted to share. In our company we had Kaspersky Anti-Ransomware Tool for Business which was causing the 20min to login into Windows 10 , after unistalling or reinstaling, this issue is gone.
To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Best Answer. View this "Best Answer" in the replies below ». Popular Topics in Windows Items in "My Network Places" can be an issue as well. As HopelessN00b indicates, these things create long timeouts and hence the long wait.
This looks like a DNS issue. You mentioned verifying the clients were configured to use your domain controllers. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 9 years, 3 months ago. Active 9 years, 3 months ago. Viewed 3k times. No major changes have been applied to our network.
Improve this question. Bill the Lizard 1 1 gold badge 7 7 silver badges 15 15 bronze badges. Emily Pinkerton Emily Pinkerton 21 1 1 silver badge 2 2 bronze badges. Ok, before you drive yourself nuts in lower level logs, what to RSOP. My experience and money says login times this long are almost certainly due to a logon script or user-level GPO calling files or network resources that can't be found, and creating long wait times because of network timeouts.
In addition, Sysinterals procmon can help with additional boot logging. Exhibit A , Exhibit B. Add a comment.
0コメント