FIX: Outbound PPTP connections may disconnect after 60 seconds if the ISA Firewall Service is running

Outbound PPTP connections from a computer that is running Microsoft Internet Security and Acceleration Server (ISA Server) may disconnect after 60 seconds if the ISA Firewall Service is running and the internal network adapter is bound as the first network adapter.

This problem may occur if ISA Server is installed in either Integrated mode or Firewall mode and if the ISA Firewall Service is running. During the first 60 seconds, clients may be able to ping remote hosts and may be able to transfer data through the tunnel until the PPTP connection is disconnected. You may temporarily prevent this problem by stopping the ISA Firewall Service. This problem affects only outbound PPTP connections that are established from the computer that is running ISA Server.

This problem may occur if Network Address Translation (NAT) is applied to all outbound connections when the ISA Firewall Service is running. When ISA Server processes an address change notification, ISA Server may incorrectly unbind SecureNAT from the external interface. This behavior causes all NAT mappings for the interface to expire. A NAT scavenger thread that runs every 60 seconds then deletes these expired mappings. The PPTP tunnel is disconnected because the NAT mappings have been deleted.

However, the PPTP tunnel may remain connected if the computer that is running ISA Server sends a PPTP control message before the remote peer sends a PPTP control message. This behavior re-creates the NAT mapping correctly. Therefore, incoming packets are delivered to the correct port. The NAT mapping is re-created correctly only if the local server sends the first PPTP control message.

Prerequisites

You must install ISA Server Service Pack 1 (SP1) before you apply this hotfix.

For additional information about how to obtain the latest ISA Server service pack, 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.

Hotfix file information

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
This hotfix also applies to the French, German, Spanish, and Japanese versions of ISA Server.

You might be able to avoid this problem, or you might be able to make this problem occur less frequently, by changing the network adapter binding order so that the external network adapter is bound as the first adapter.

Note If the computer that is running ISA Server is operating in a domain, either as a controller or as a member, or is operating as a DNS or WINS name server, do not change the network adapter binding order. This change may interrupt internal communications. Instead, install the hotfix that the "Resolution" section describes.

To change the network adapter binding order, follow these steps:

1. In Control Panel, open Network and Dial-up Connections.
2. On the Advanced menu, click Advanced Settings.
3. On the Adapters and Bindings tab, verify that the external network adapter is the first bound network adapter.
4. Click OK.

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

When you experience this problem, the following event may appear in the system log file on the remote VPN server if the Routing and Remote Access service has been configured to log the maximum amount of information. The average connection time will be approximately one minute.

Event Type: Information
Event Source: RemoteAccess
Event Category: None
Event ID: 20048
Date: DD/MM/YYYY
Time: Time
User: N/A
Computer: SERVERNAME
Description:
The user DOMAIN\USERNAME connected on port VPN4-125 on MM/DD/YYYY at HH:MM and disconnected on MM/DD/YYYY at HH:MM. The user was active for 1 minutes 2 seconds. 321 bytes were sent and 5349 bytes were received. The port speed was 10000000. The reason for disconnecting was user request.

To make the Routing and Remote Access service log this event, follow these steps on the remote VPN server:

1. In the Routing and Remote Access Microsoft Management Console (MMC) snap-in, right-click the server name, and then click Properties.
2. On the Event Logging tab, select Log the maximum amount of information, and then click OK.

For additional information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base: