File Sharing Operations to a Share on Local Computer May Be Slow

When you share files on a computer, and then connect to that sharepoint from the same computer, file operations such as XCOPY may be slow if TCP/IP is the protocol being used.

If for example you share out a directory named "test", and then connect to that share from the same computer it was shared from, the TCP/IP stack uses what is called the "loopback" interface. The use of the "loopback" interface is to prevent packets between the client and server (which are on the same computer) from actually being sent out on the network cable.

TCP/IP implements "nagling" and "delayed acknowledgment", even though the interface in this case is loopback. This can cause unnecessary delays.

More details on nagling are available in ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/papers/Tcpimp2.exe (ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/papers/Tcpimp2.exe)

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

• http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
  
  
• 152734  (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.