Discussion Locked

WinXP Pro Domain login is very slow

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Win XP Pro take over 5 minutes to login to Windows 2k Server domain. No user or computer setting have enable in Group Policy.

Any ideas on how to resolve this

6 replies

by sramesh2k

Slow logon to domain in XP Pro

You may experience extremely long delays (up to 5 minutes) when logging into domains using Windows XP Pro. This is caused by the asyncronous loading of networking during the boot up process. This speeds up the loginprocess in a stand-alone workstation by allowing the user to log in with cached logon credentials before the network is fully ready.

To disable this "feature" and restore your domain logons to their normal speed, open the MMC and add the group policy snap-in. Under Computer Configuration-->Administrative Templates-->System-->Logon, change "Always wait for the network at computer startup and logon" to ENABLED

Refer this article here:

http://www.windowsxpatoz.com/cgi-bin/performance/index.cgi?answer=1036283899&id=1036282433

Best Regards,
Ramesh Srinivasan
AOL: SRamesh2K

by icario

Thanks. Already tried this it reduced login timme to about 2 minutes from 5 minutes.

by icario

Thanks. Already tried this it reduced login timme to about 2 minutes from 5 minutes.

by hdettmer

On some XP Pro installations, when connected to a network, The system seems to freeze after logging in and the desktop may not appear or will freeze for a minute or longer. As timed with the utility, Bootvis.exe, the problem was/is with the driver mrxsmb.dll, adding over 67 seconds to the boot time. Turning off and restoring file and printer sharing eliminated 65 seconds from the boot time.

Alt-click (or right-click) on Network Places > Properties.
Alt-click on Ethernet Adapter connection > Properties.
Un-check "File and Printer Sharing for Microsoft Networks" > OK.
Reboot.
If you need file or printer sharing, repeat the above, re-check the box and re-boot again.

This discussion is closed to new replies.