Article ID: 946409
Article Last Modified on 12/31/2007
APPLIES TO
- Windows Server 2008 Standard
- Windows Server 2008 Enterprise
- Windows Server 2008 Datacenter 32-Bit
- Windows Server 2008 Enterprise 32-Bit
- Windows Server 2008 for Itanium-Based Systems
- Windows Server 2008 Standard 32-Bit
- Windows Web Server 2008
Beta Information
This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.
No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.
SYMPTOMS
Consider the following scenario:
- You have two dial-up virtual private network (VPN) connections.
- These VPN connections have classless addresses that share a classful address.
In this scenario, the routes do not work correctly. Although, the first VPN connection is successful, the second VPN connection is not successful.
This problem occurs when you do not select the Use default gateway on remote network check box in the VPN TCP/IP settings.
CAUSE
This problem occurs because the routing table is loaded incorrectly. The routing table that is used in the classful address routes is loaded into both of the VPN routes. Therefore, the routing table routes the packets of the second VPN connection through the first VPN connection.
WORKAROUND
To work around this problem, add post-connection CmRoutes to the stack, or add manual routes to stack.
Keywords: kbexpertiseinter kbtshoot kbprb KB946409
