Article ID: 891307
Article Last Modified on 7/24/2007
APPLIES TO
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Web Edition
SYMPTOMS
You have copied locally encrypted files from a Microsoft Windows-based client computer to a Microsoft Windows Server 2003-based member file server. The files were encrypted by using the Encrypting File System (EFS). Both computers are in a domain that is part of a Windows Server 2003-based or Microsoft Windows 2000 Server-based Active Directory forest. In this scenario, you may experience the following behavior:
- The file server opens three TCP connections for the client on Lightweight Directory Access Protocol (LDAP) port 389 when you connect and start copying files to the file server.
Note You can use the netstat –anop tcp command on the file server to verify this.
- You may receive a warning message that states that the file server does not support encryption for the files that you copy to the file server.
- If you ignore the warning message, the file server opens three more TCP connections for the client computer on LDAP port 389. If you cancel the copying process, no additional connections are opened.
- The state of the TCP connections changes from ESTABLISHED to CLOSE_WAIT after 15 minutes.
- The file server does not close the TCP connections.
- The clients may not be able to log on to the file server if the number of ports that are used by the file server reaches the maximum number of ports that are available.
- You have to restart the file server to release the LDAP port that is used by the TCP connections.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
Restart requirement
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003, 32-bit versions
Date Time Version Size File name -------------------------------------------------------------- 23-Dec-2004 00:22 5.131.3790.244 485,376 Cryptui.dll
Windows Server 2003, 64-bit versions
Date Time Version Size File name -------------------------------------------------------------- 22-Dec-2004 10:47 5.131.3790.244 1,094,656 Cryptui.dll IA-64 22-Dec-2004 10:52 5.131.3790.244 485,376 Wcryptui.dll x86
WORKAROUND
To work around this problem, disable, and then enable the network adaptor.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbqfe kbhotfixserver kbbug kbfix kbwinserv2003presp1fix KB891307
