Windows xp sp2 slows down login times

When I installed service pack 2 for xp on 3 different laptops it takes
forever to login to the domain. Right after you put your password in it
hangs forever. It takes anywhere from 5 to 20 minutes. It works fine on the
desktops that we put it on but every laptop we keep putting it on it does the
same thing. Is there anything out there that can fix this. We have turned
of automatic updates so we don't run into this issue and we need to turn it
back on so people can get their updates. Please help!

I found that MS created an xp2 automatic windows updated blocker for those
who want to keep the auotmatice WU turned on, but do not want the xp2
downloaded just yet. Do a search under xp2 updates and you should find it.

Can not help on your real problem thought, but maybe it will keep those cpus
up to date.

Good luck.

"" wrote:

> When I installed service pack 2 for xp on 3 different laptops it takes
> forever to login to the domain. Right after you put your password in it
> hangs forever. It takes anywhere from 5 to 20 minutes. It works fine on the
> desktops that we put it on but every laptop we keep putting it on it does the
> same thing. Is there anything out there that can fix this. We have turned
> of automatic updates so we don't run into this issue and we need to turn it
> back on so people can get their updates. Please help!

Are these laptops all from one manufacturer? What kind are they? What kind
of domain controller? Once logged into the domain do they then function
normally?
--

""
<@discussions.microsoft.com > wrote in message
news:457672B8-6DC7-417F-8FBC-...
> When I installed service pack 2 for xp on 3 different laptops it takes
> forever to login to the domain. Right after you put your password in it
> hangs forever. It takes anywhere from 5 to 20 minutes. It works fine on
> the
> desktops that we put it on but every laptop we keep putting it on it does
> the
> same thing. Is there anything out there that can fix this. We have
> turned
> of automatic updates so we don't run into this issue and we need to turn
> it
> back on so people can get their updates. Please help!