FIX: Outbound PPTP connections may disconnect after 60 seconds if the ISA Firewall Service is running
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.
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.
PrerequisitesYou 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 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: 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 informationThe 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.
Date Time Version Size File name ------------------------------------------------------- 21-Dec-2003 09:07 3.0.1200.302 178,448 Mspadmin.exe 21-Dec-2003 09:07 3.0.1200.302 103,184 Msphlpr.dll 21-Dec-2003 09:07 3.0.1200.302 393,488 W3proxy.exe 21-Dec-2003 09:07 3.0.1200.302 299,280 Wspsrv.exe
This hotfix also applies to the French, German, Spanish, and Japanese versions of ISA Server.
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:
- In Control Panel, open Network and Dial-up Connections.
- On the Advanced menu, click Advanced Settings.
- On the Adapters and Bindings tab, verify that the external network adapter is the first bound network adapter.
- Click OK.
Event Type: Information
Event Source: RemoteAccess
Event Category: None
Event ID: 20048
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.
- In the Routing and Remote Access Microsoft Management Console (MMC) snap-in, right-click the server name, and then click Properties.
- On the Event Logging tab, select Log the maximum amount of information, and then click OK.
Article ID: 831531 - Last Review: 12/08/2015 05:20:08 - Revision: 4.4
- kbnosurvey kbarchive kbautohotfix kbqfe kbhotfixserver kbisaserv2000presp2fix kbfix kbbug KB831531