On an x64-based version of Windows Server 2003 SP2, a PPP dial-up connection uses the default gateway on the remote network even if you disable this option in the TCP/IP settings

Consider the following scenario. On a Microsoft Windows Server 2003-based computer, you have a Point to Point Protocol (PPP) dial-up networking connection. This PPP connection has the following option configured:Note To view this option, follow these steps:

1. Right-click the dial-up networking connection, and then click Properties.
2. Click the Networking tab, click Internet Protocol (TCP/IP), and then click Properties.
3. Click Advanced.

When you establish a connection in this scenario, the IP address of the default gateway on the remote network is incorrectly set to the address of the PPP connection. You do not expect the dial-up connection to use the default gateway on the remote computer after you disable this option. Additionally you may receive the following error message:

This problem occurs if the following conditions are true:

• You use a 32-bit program to establish the dial-up connection.
• The 32-bit program is running on an x64-based version of Windows Server 2003 Service Pack 2 (SP2).

Note You do not experience this problem when you use the program on a 32-bit version of Windows Server 2003.

This problem occurs because of a problem in Windows Server 2003 SP2.

On an x64-based version of Windows Server 2003 SP2, the correct Remote Access Service Manager (RASMAN) values are not copied into the thunking structure. Therefore, a 32-bit dialing program appears to ignore the 64-bit networking settings.

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

You must be running one of the following to apply this hotfix:

• Windows Server 2003 Service Pack 1 (SP1)
• Windows Server 2003 Service Pack 2 (SP2)
• Windows Server 2003, x64 Edition

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfix.

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, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based systems

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Note The hotfix that is mentioned in this article also modifies the behavior of the dial-up networking APIs. For more information, click the following article number to view the article in the Microsoft Knowledge Base: