1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Slow network writes, fast reads after upgrading to WinXP Pro

Discussion in 'Networking (Hardware & Software)' started by mkeast, 2006/02/14.

  1. 2006/02/14
    mkeast

    mkeast Inactive Thread Starter

    Joined:
    2006/02/14
    Messages:
    1
    Likes Received:
    0
    I upgraded my Dell Precision 530 workstation from Windows 2000 to Windows XP Pro SP2. The machine is fully patched. The NIC is a 3COM 3C920 integrated fast ethernet controller compatible with the 3COM 3C905C-TX.

    This machine is a member of a large domain (Windows 2000 currently migrating to Windows 2003 - not sure how many servers have been migrated). Since I'm a developer and SQL Server DBA for a 30-person office that is part of a larger organization, I upgraded the machine myself (most users have an imaged desktop). After upgrading, I get the same read performance from any network server (I have access to several different domain member servers, including 5 that I maintain) that I got with Win2K, but the write performance is abysmal. Using PerfMon, for Network bytes received/sec I get close to 6 MB / sec, while network writes are about 120 KB / sec. We use Cisco switches, not sure what models. Usually, this type of problem is due to mismatch between the switch port duplex/type setting and the associated setting on the client PC. I tried all of the various settings (should be 100 MBit/Full Duplex), but nothing works.

    Does anybody have any ideas at what else to look for? Thanks

    Mike
     
    mkeast,
    #1
  2. 2006/02/15
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,321
    Likes Received:
    253
    Might try this:

    Speed up network (LAN) browsing in Win2K/XP
    Open the Registry Editor (REGEDIT.EXE)

    Rename the following registry entry:
    HKEY_LOCAL_MACHINE
    \Software
    \Microsoft
    \Windows
    \CurrentVersion
    \Explorer
    \RemoteComputer
    \Namespace
    \{D6277990-4C6A-11CF-8D87-00AA0060F5BF}

    For example, you can rename it to:

    DISABLED {xxD6277990-4C6A-11CF-8D87-00AA0060F5BF}

    This change prevents the browsing computer from checking for scheduled tasks on the remote machine before connecting, which is apparently the reason for the slowness.

    You can check this Knowledge Base article for further reference:

    http://support.microsoft.com/?id=kb;en-us;Q245800
     
    Steve R Jones,
    #2


  3. to hide this advert.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...