Deployed XP - Network TOTALLY slow!

[KB]

We're halfway through of an XP deployement (backend is Win2k3 servers
- in place for over 6 months). Since, traffic, searching files,
loading files, saving files, opening network directories IS TERRIBLY
SLOW. In some instanced machines "hang" (with all the nice non-window
redraws prevalent to XP).

For instance, copy documents off 98 PC to server - 5 minutes. Remove
old 98 PC, put in place new XP PC. Copy documents back, 12 minutes.
Open users home folder, wait 5 seconds for all files to be found, draw
window. On 98/95, drawing, listing instantanous.

Inter-building link is T1, which have given NO speed complaints prior
to XP workstation install. Half building is now XP (some 30-40 PC's)
- running slow. Half building (30-40) running 95/98 - running fast as
ever.

I would expect XP to be a bit more heavy, but this is rediculous,
almost criminal.

Any thoughts besides Linux desktops?

 

[Carey Frisch [MVP]]

Ensure that you have good DNS name resolution in your environment.
All Windows XP clients should point to an internal DNS server that is
authoritative for the domain.

If that is OK, then you might want to enable UserEnv logging
and take a network trace to see where the delay is:

How to Enable User Environment Debug Logging in Retail Builds of Windows
http://support.microsoft.com/?id=221833

Description of the Windows XP Professional Fast Logon Optimization Feature
http://support.microsoft.com/default.aspx?scid=kb;en-us;305293&Product=winxp

Logon Optimization
http://msdn.microsoft.com/library/d...ry/en-us/policy/policy/logon_optimization.asp

Please visit the experts in the networking newsgroup
news://msnews.microsoft.com/microsoft.public.windowsxp.network_web

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect your PC!
http://www.microsoft.com/security/protect/

-----------------------------------------------------------------------------------------


| We're halfway through of an XP deployement (backend is Win2k3 servers
| - in place for over 6 months). Since, traffic, searching files,
| loading files, saving files, opening network directories IS TERRIBLY
| SLOW. In some instanced machines "hang" (with all the nice non-window
| redraws prevalent to XP).
|
| For instance, copy documents off 98 PC to server - 5 minutes. Remove
| old 98 PC, put in place new XP PC. Copy documents back, 12 minutes.
| Open users home folder, wait 5 seconds for all files to be found, draw
| window. On 98/95, drawing, listing instantanous.
|
| Inter-building link is T1, which have given NO speed complaints prior
| to XP workstation install. Half building is now XP (some 30-40 PC's)
| - running slow. Half building (30-40) running 95/98 - running fast as
| ever.
|
| I would expect XP to be a bit more heavy, but this is rediculous,
| almost criminal.
|
| Any thoughts besides Linux desktops?

 

[Ron Martell]

We're halfway through of an XP deployement (backend is Win2k3 servers
- in place for over 6 months). Since, traffic, searching files,
loading files, saving files, opening network directories IS TERRIBLY
SLOW. In some instanced machines "hang" (with all the nice non-window
redraws prevalent to XP).

For instance, copy documents off 98 PC to server - 5 minutes. Remove
old 98 PC, put in place new XP PC. Copy documents back, 12 minutes.
Open users home folder, wait 5 seconds for all files to be found, draw
window. On 98/95, drawing, listing instantanous.

Inter-building link is T1, which have given NO speed complaints prior
to XP workstation install. Half building is now XP (some 30-40 PC's)
- running slow. Half building (30-40) running 95/98 - running fast as
ever.

I would expect XP to be a bit more heavy, but this is rediculous,
almost criminal.

Any thoughts besides Linux desktops?

How much RAM do the XP desktops have? They should be at 384 or
preferably 512 mb for running Windows XP in a corporate network
environment.

Check the actual page file usage on the XP machines with the page file
usage monitor utility (free) from
http://www.dougknox.com/xp/utils/xp_pagefilemon.htm or from
http://billsway.com/notes_public/WinXP_Tweaks/

If it shows more than 50 mb of actual page file usage on a regular
basis then a RAM upgrade is the answer, or at least part of it.

Good luck



Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."