Very Slow Login

[Alan]

Have a PC running XP Pro into a 2000 server.

Login is very slow (up to 5 mins) loading personal
settings.

Once logged in the system works fine.

No problem with the other 8 machines in the building.

Have tried - server reboot, swap network cable. As the
system runs ok after login cannot think the PC itself is
at fault.

Any ideas what may be causing slow login ?

 

[Ron Lowe]

Have a PC running XP Pro into a 2000 server.

Login is very slow (up to 5 mins) loading personal
settings.

Once logged in the system works fine.

No problem with the other 8 machines in the building.

Have tried - server reboot, swap network cable. As the
system runs ok after login cannot think the PC itself is
at fault.

Any ideas what may be causing slow login ?

Slow logons to a win2k domain usually indicate a DNS problem.

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
DNS and AD FAQs:
http://support.microsoft.com/?id=291382

 

[jason]

are you use roaming profiles or logon scripts? when login
in that particular pc plz do this hit cntl-alt-delete then
chosse task mngr and then look at the processes and see
which one is using up most cpu or memory then kill it i
think you should see if u r using login scripts that maybe
that is hogging resources if so disable logon sciprt for
that user only

if this is not the case once logged in chekc your event
viwer for things like page file considerations etc

 

[jaosn]

yeh yeh hes right sorry my reasoning about roaming
profiles is prob not right in this scenario