L2TP May Not Use the Default IP Address

This article was previously published under Q322018
This article has been archived. It is offered "as is" and will no longer be updated.
Layer 2 Tunneling Protocol (L2TP) may not use the default IP address as the source when it makes new connections. This occurs if you have multiple IP addresses that are specified on the network adapter. Typically, the default IP address is the first IP address that is bound. L2TP may use any bound IP address as its source when it sends packets. This can cause problems with firewalls such as Microsoft ISA Server which may block IP addresses except for the default IP address.
L2TP over IP is not designed to look for the default IP address.

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

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.

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, submit a request to 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. The English version of this fix has the file attributes (or later):
   Date         Time     Version        Size     File name   ---------------------------------------------------------   10-Jun-2002  7:30:18  5.0.2195.5873   58,128  Rasman.dll   26-Jul-2002 13:55:34  5.0.2195.5967  152,848  Rasmans.dll   10-Jun-2002  7:30:18  5.0.2195.5873   54,032  Rastapi.dll

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot
ISAKMP Negotiation

Article ID: 322018 - Last Review: 10/24/2013 11:41:39 - Revision: 4.7

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbnetwork kbwin2ksp4fix kbbug kbenv kbfix kbui kbwin2000presp4fix KB322018