Information Technology Consulting Service

www.katarincic.com


Welcome Guest Search | Active Topics | Members | Log In

Slow logon to domain in XP Pro Options · View
scott
Posted: Wednesday, March 31, 2010 1:44:13 PM
Rank: Administration
Groups: Member

Joined: 3/24/2008
Posts: 2,754
Points: 5,438
Location: South Florida USA
Slow logon to domain in XP Pro

http://www.tweakxp.com/article37007.aspx


Quote:

This is caused by the asyncronous loading of networking during the boot up process. This speeds up the login process 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.

This can be fed to clients via a group policy from a Windows 2000 server by upgrading the standard policy template with the XP policy template. Since this is an XP only command, non-XP systems will ignore it in a domain distributed group policy.





scott
Posted: Wednesday, April 14, 2010 11:23:54 AM
Rank: Administration
Groups: Member

Joined: 3/24/2008
Posts: 2,754
Points: 5,438
Location: South Florida USA
http://www.computing.net/answers/windows-2003/slow-logins-only-with-xp-pro/4260.html

Quote:

I found a lengthy post on another site that seems to quote MS KB text and offers an explaination and solution... we'll see if this helps:
Lenthy logins to a domain are usually caused by incorrectly setting up
DNS. Here is information about that from MVP Ron Lowe:

"XP differs from previous versions of windows in that it uses DNS as
it's primary name resolution method for finding domain controllers:

"If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS. ( Which may or
may not work. )

"1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the Win2k
server itself. They should NOT be pointing to an ISP's DNS server. An
'ipconfig /all' on the XP box should reveal ONLY the domain's DNS
server. You should use the DHCP server to push out the local DNS server
address.

"2) Ensure DNS server on Win2k is configured to permit dynamic updates.

"3) Ensure the Win2k server points to itself as a DNS server.

"4) For external ( internet ) name resolution, specify your ISP's DNS
server not on the clients, but in the 'forwarders' tab of the local
Win2k DNS server.

"On the DNS server, if you cannot access the 'Forwarders' and 'Root
Hints' tabs because they are greyed out, that is because there is a
root zone (".") present on the DNS server. You MUST delete this root
zone to permit the server to forward unresolved queries to yout ISP or
the root servers. Accept any nags etc, and let it delete any
corresponding reverse lookup zones if it asks."

How Domain Controllers Are Located in Windows XP -
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861
Setting Up the Domain Name System for Active Directory -
http://support.microsoft.com/default.aspx?scid=kb;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000 -
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
DNS and AD FAQs - http://support.microsoft.com/?id=291382



Users browsing this topic
Guest


Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Main Forum RSS : RSS

YAFPro Theme Created by Jaben Cargman (Tiny Gecko)
Powered by Yet Another Forum.net version 1.9.1.6 (NET v2.0) - 11/14/2007
Copyright © 2003-2006 Yet Another Forum.net. All rights reserved.
This page was generated in 0.046 seconds.