I have a network with dozens of XP clients controlled by a Windows 2008 domain controller. One client, and only one of them, takes 3-4 minutes to log in. This is only the case after a reboot. If I log off and log on as a new user without restarting it works fine. I have tried to login using different usernames after the reboot and it is the same effect for each one, so I do not think it is profile related. I have seen mention of DNS issues causing this problem, but I have followed all the advice along those lines and still the problem persists. I have even installed the Profile Hive Cleanup utility.

Dani AI

Generated

The slow pause right after a reboot points to a computer-side startup hold (Group Policy, startup scripts, services or a driver waiting on a network resource) rather than a per-user profile problem. already narrowed it to the machine and confirmed basic network reachability, so next moves should be evidence gathering (logs and traces) and quick isolation tests to find the exact timeout.

Collect targeted diagnostics first:

  • Check Event Viewer (System, Application and the Microsoft-Windows-GroupPolicy/Operational log) for gaps and these common IDs: 1058, 1030 (GPO/read errors), 5719 (no logon servers), and service timeouts such as 7000/7011. Note the timestamps; they show where the 3–4 minute stall occurs.
  • Produce a Group Policy report (run elevated):
    gpresult /h C:\gpresult.html
  • Verify DC discovery from the client:
    nltest /dsgetdc:YOURDOMAIN
  • Capture what actually waits during boot: enable Procmon boot logging (Sysinternals -> Options -> Enable Boot Logging), reboot, then analyze the saved boot log for long I/O/network timeouts. For network-level capture use netsh trace start/stop to collect an ETL if needed.

Use quick isolation to narrow causes. Temporarily disable the NIC before boot to see if the pause goes away. If it does, the problem is a network lookup or policy/script contacting an unavailable server. Boot with non-Microsoft services disabled (clean boot) to rule out third-party drivers/AV. Compare the working machine’s gpresult and event timestamps to this machine’s.

Common fixes once you identify the culprit: fix unreachable shares referenced by computer startup scripts or GPOs, remove problematic startup scripts or printer mappings, update/reinstall the NIC driver, and as a last resort test rejoining the computer to the domain or creating a new computer account. If the logs show specific event IDs and the mapping above doesn’t resolve it, collect the Procmon/netsh traces and match the exact failing path before making changes.

Recommended Answers

All 10 Replies

HMM, does that machine work on the network?

Not .....
Only really in contact with users and network printers

so it's connected can you try and ping on that machine?

client enter the network, but the process of preparing the desktop delayed for a long time

Yes I understand.

Can you ping the server from the machine?

Please post the results

To ping do the following

Click on Start->Run
type 'cmd' without quotes
then type 'ping xxx.xxx.xxx.xxx' without quotes
xxx.xxx.xxx.xxx is the servers IP.

yes I can
I can ping any PC
apply computer settings
just problem
I whit

ok post results?

My problem lies in the apply computer settings , I try to log into my account, that Delays of more than 3 minutes and not in the communicative network to work, I upgraded the server from the net and then to 2003 to 2008.

For me to help you, I need you to help me.

ok

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.