Discussion Locked

Windows XP Pro is SO SLOW

0 helpful
16 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I just installed a new Windows XP Pro onto our network (domain) and noticed that it takes FOREVER to do anything. I waited 2+ minutes for it to "apply your personal settings". When browsing the network to copy files from shared drives, it takes forever to go from one folder to the next. What is XP doing?

16 replies

by ann777

How to set WinXP Performance Options:

http://support.microsoft.com/default.aspx?scid=kb;en-us;308417

You haven't really given us any information to go on here.

How much RAM do you have in this computer? What Processor are you running (CPU and MHz)? Are you certain that the nic (network card) drivers are written for WinXP? Are the servers local or remote? Have you done a tracert? Or a ping? Does device manager show any problems?

by lmayeda

The PC is an optiplex 260 2.4ghz with 512MB ram. The NIC is an integrated card with factory installed drivers. Ping and Tracert seems to work OK

by quintar51

To add to Anna's Answer, what protocls are you using on your XP machine? Unnecessary protocols can slow down your network browsing, hence giving you long wait times. Also, I would recommend you take a look at the event viewer for further clues.

by lmayeda

Using TCP/IP. Your suggestion to look at my event viewer pointed me in the direction of network security and eventually led me to a registry fix. Thanks

by blaine moore

If you are hanging on steps such as applying personal settings, or running startup scripts, etc etc, your problem may be your NIC. Download and install the latest winxp compliant drivers or swap your NIC out.

by lmayeda

Will defer this option since the NIC was factory installed along with the drivers and the PC is brand new.

by cuss

I had the same problem, This did the trick. Go ot your services and disable "Indexing Service"

by lmayeda

Solved problem via registry fix ... didn't get to try your solution. Thanks anyway.

by orpheum

this is probably not a permanent fix, but map a network drive to the shared drive/s. i do this all the time and what windows does is it gives the mapped drive network clearance so it does not use any browsing or searching threads. it is as if that network drive is on your local PC.
Let me know how this works out, it will NOT fail!!

by lmayeda

We have several mapped drives that are accessible. It seems that the PC has to "learn" where a drive is and that takes about 30 seconds. Once it knows, it is fast .. however, how long does it remember the location of a folder?

by orpheum

how long does it remember the location of a folder?

it is an always on connection.as long as the machine which contains that drive is on when u log in with the problem computer, it will "reconnect at logon" provided you checkmarked this when you mapped the drive.

you should be okay with a mapped drive.

by lmayeda

Typically what you stated is true for my other W2k and WNT machines ... the problem seems to be related to XP. Thanks.

by lmayeda

I browsed thru the Microsoft website and I think I have found the solution...several others were having similar problems with their XPs. I first backed up my registry then performed the following modification:
HKLM\CurrentControlSet\Services\Lanman|workstation\Parameters
Changed Enable Security Signature to 0
System

This discussion is closed to new replies.