Select the product you need help with
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 settingsArticle ID: 940871 - View products that this article applies to. On This PageSYMPTOMSConsider 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: On the General tab in the Advanced TCP/IP Settings dialog box, the Use default gateway on remote network check box is cleared. Note To view this option, follow these steps:
Remote Access error 720 - A connection to the remote computer could not be established. You might need to change the network settings for this connection. This problem occurs if the following conditions are true:
CAUSEThis 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. RESOLUTIONHotfix informationA 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: http://support.microsoft.com/contactus/?ws=support 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesYou must be running one of the following to apply this hotfix:
Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfix.File informationThe 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 versionsCollapse this table
Windows Server 2003, x64-based versionsCollapse this table
Windows Server 2003, Itanium-based systemsCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONNote 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:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
PropertiesArticle ID: 940871 - Last Review: October 8, 2011 - Revision: 3.0 APPLIES TO
|
Back to the top
