A 32-bit application may not work correctly on a computer that is running a 64-bit edition of Windows Server 2003

A 32-bit application that calls Windows Winsock may not work correctly on a computer that is running a 64-bit version of Windows Server 2003. You may experience this problem if the following conditions are true:

• The application is developed by using a layered service provider (LSP).
• The application is designed for 64-bit processes and for 32-bit processes.
• A 64-bit protocol is installed on the computer after the 32-bit protocol is installed on the computer.

For example, you install the Microsoft Internet Security and Acceleration (ISA) Server client on a computer that is running an x64-based version of Windows Server 2003 Service Pack 1 (SP1). This computer has the IPv4 protocol installed. However, it does not have the IPv6 protocol installed. Then, you install the IPv6 protocol in this operating system. In this scenario, the 32-bit processes that are using Windows Winsock may not work correctly.

This issue occurs because this application calls the 32-bit Windows Winsock that correctly points to the 64-bit catalog in a 64-bit version of Windows Server 2003.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To install this hotfix, you must have Microsoft Windows Server 2003 SP1 installed.

Restart requirement

You have to restart the 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 item in Control Panel.

Windows Server 2003, x64-based versions

Windows Server 2003 with Service Pack 1, Itanium-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows Server 2003 Service Pack 2.

For more information about the layered service provider, visit the following Web site: