XP PRO slow at logging in

[Robert Swainson]

Has anyone noticed or experienced issues with XP
professional logging onto the network so slow. Recently I
have done a new network setup for a customer. They are
running a w2k server 933 Meg machine. The drivers are
stripped with parity. I have notice the first time a user
logs onto a machine it can take as long as 2.30 seconds
for the workstation to finish authenticating. However the
one machine with windows 2000 pro takes as little as 45
seconds. Once the profile is created the win2k pro logs on
in about 15 seconds. XP just takes forever and I am almost
at the point in recommending the client standardizes on
win2k. The area that is hanging is applying personal
settings and the processes after that. There are no huge
batch files running or group policies to implement. All it
is doing is mapping 1 printer and 3 network shares. All
machines are up to date with service packs and fixes.
These seams to only occur with win xp pro. There are no
mandatory profiles in use or roaming profiles. Can anyone
give me any tips on how to speed up the logging in process
on these work stations?

Robert F. Swainson, A+, MCSE, CWNP, TCT

 

[David Jones]

Check my reply in the Performance & Maint newsgroup...

 

[Robert L [MS-MVP]]

quoted from http://www25.brinkster.com/ChicagoTech
Why is XP running slower while logon 1

When I login into a Windows 2000 active directory from a new xp pro machine
the login in is extremely slow. After logged on, everything works fine. But
other windows versions don't have this problem.
A: This is almost like name resolution issue. Comparing with previous
versions, XP is heavily dependent on DNS to find DC. If the DNS is
configured incorrectly, XP will take longer time waiting for it to timeout
before it tries using NetBIOS. Make sure
1) The DNS setup correct and have the server information.
2) XP clients can find the DNS server.
3) XP machine's DNS server is pointed to your internal DNS server rather
than your ISP's DNS server.
4) Make sure no errors on logon scripts or GPO's that could be causing
the delay.
5) Check any errors on event viewer.
6) Disable NetBIOS on the interfaces that client will not use.
--
For more and other information, go to
http://www25.brinkster.com/ChicagoTech

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Windows & Network Support, Tips and FAQs on
http://www25.brinkster.com/ChicagoTech
This posting is provided "AS IS" with no warranties.

 

[Ron Lowe]

Has anyone noticed or experienced issues with XP
professional logging onto the network so slow. Recently I
have done a new network setup for a customer. They are
running a w2k server 933 Meg machine. The drivers are
stripped with parity. I have notice the first time a user
logs onto a machine it can take as long as 2.30 seconds
for the workstation to finish authenticating. However the
one machine with windows 2000 pro takes as little as 45
seconds. Once the profile is created the win2k pro logs on
in about 15 seconds. XP just takes forever and I am almost
at the point in recommending the client standardizes on
win2k. The area that is hanging is applying personal
settings and the processes after that. There are no huge
batch files running or group policies to implement. All it
is doing is mapping 1 printer and 3 network shares. All
machines are up to date with service packs and fixes.
These seams to only occur with win xp pro. There are no
mandatory profiles in use or roaming profiles. Can anyone
give me any tips on how to speed up the logging in process
on these work stations?

Robert F. Swainson, A+, MCSE, CWNP, TCT

This is very common.
The usual reason is DNS setup.

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

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314861

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 an 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 lookuop
zones if it asks.


The following articles may assist you in setting up DNS correctly:

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