FIX: Server Publish May Fail on Dial-up Links

If you use ISA Server to server publish on a dial-up adapter link (such as an analog modem, ISDN, or ADSL), the server publish operation may fail. This problem may occur although you use a fixed IP address on the dial-up interface.

When you run netstat -an from a command prompt on the computer running ISA Server, you see that ISA Server is not listening on the published port on behalf of the published service. Because of this, no connections can be made to the server published service.

Typically, this problem occurs on a slow link such as an analog modem connection. However, it may occur when you use any type of dial-up adapter.

To get the server publishing rule to work, you must turn off and then turn on the server publishing rule, or you must stop and then restart the Firewall Service.

ISA Server receives IP address change notifications from the operating system (OS) when the dial-up link is brought online. Sometimes, ISA Server may receive notifications before the IP address on the dial-up adapter is bound to the interface. This causes ISA Server to reject the dial-up interface as a valid interface for server publishing.

Additionally, ISA Server will miss the next notification (a few milliseconds later) from the OS when a valid IP address is bound to the dial-up adapter. Because ISA Server does not receive this second notification, it does not server publish on the dial-up interface. ISA Server can server publish on the dial-up interface again when it receives a new notification.

You must install ISA Server Service Pack 1 (SP1) before you install the following hotfix. For additional information about how to obtain the latest ISA Server service pack, click the article number below to view the article in the Microsoft Knowledge Base: A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site: To install the fix, run the self-extracting file. You do not have to restart the computer running ISA Server. If the computer is part of an ISA Server array, you do not have to shut down the whole array; you can still install this fix on a one-by-one basis.

The English version of this fix 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 
--------------------------------------------------------
24-Oct-2002   20:21   3.0.1200.179   176,912   Mspadmin.exe 
24-Oct-2002   20:20   3.0.1200.179   388,368   W3proxy.exe 
24-Oct-2002   20:21   3.0.1200.179   297,232   Wspsrv.exe 
24-Oct-2002   20:21   3.0.1200.179    99,600   Msphlpr.dll 
				

This fix also applies to the French, German, Spanish, and Japanese versions of ISA Server.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Note that although you have installed this hotfix, the Application Event Log may record informational events similar to the following: This event occurs because the first notification that ISA Server receives from the OS, before the valid IP address on the dial-up adapter is bound to the interface, fails. The event does not affect ISA Server. When ISA Server receives the second notification, a few milliseconds later, it can server publish successfully.