Announcement

Collapse
No announcement yet.

Slow connection with XP to Windows 2003 server

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Slow connection with XP to Windows 2003 server

    I recently upgraded to Windows 2003 server and Windows Xp pro. The problem is that the Windows XP professional stations load the network shares very slowly.

    This is not a problem if I access the 2003 server from a Windows 2000 Pro station. or if I access a Windows 2000 server from a XP station. Only when I am accessing a Windows 2003 server domain with a Windows XP Pro station.

    Anyone have any ideas on this.

  • #2
    you can take a look about SMB signing.
    http://support.microsoft.com/default...b;en-us;814112
    or
    http://support.microsoft.com/default...b;EN-US;321169
    Marcel
    Technical Consultant
    Netherlands
    http://www.phetios.com
    http://blog.nessus.nl

    MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
    "No matter how secure, there is always the human factor."

    "Enjoy life today, tomorrow may never come."
    "If you're going through hell, keep going. ~Winston Churchill"

    Comment


    • #3
      Slow connection to network shares

      This fixed it for me, it's a registry change in the Server and in the XP boxes... worked like a champ.

      Description:
      I installed a Windows 2003 Server and set it up for a File Server Role and Domain Controller role. After I created the shares I connected my Windows XP machines to it. When I attemped to extract a 62K file on the share it took 1 minute. I found a fix for this problem. This only happens if the server is a Domain Controller and you are sharing folders off it. The server is experiencing an issue with delayed acknowledgments (or delack) to a domain controller. This is expected behavior and can be modified via a registry entry. This is also a problem when copying files to a Windows 2000 domain controller. In Windows 2000 the registry entry is "TcpDelAckTicks" and in Windows XP and 2003 the new registry entry is "TcpAckFrequency". On the Windows Server 2003 Domain Controller set the following registry key (I had to create the entry as it did not exist): Key: HKEY_LOCAL_MACHINE\Services\CurrentControlSet\Serv ices\Tcpip\Parameters\Interfaces\ Value Type: REG_DWORDValue Name: TcpAckFrequency Valid Range: 1, 2 Default: 2 Description: This key sets the number of ACKs that will be outstanding before the delay ACK timer is ignored. So, if the value of this key is set to "1" then every packet should be ACKed immediately as there should only be one outstanding TCP ACK as a segment is just received. The value of "0" is invalid and will be treated as the default "2" as the only time ACK count is zero is when a segment is not received and the host is not going to ACK the data. Set this value to 1, reboot the server and you should be fixed!

      Comment

      Working...
      X