Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/925733

From BetaArchive Wiki

Article ID: 925733

Article Last Modified on 12/4/2007



APPLIES TO

  • Microsoft Internet Security and Acceleration Server 2004 Enterprise Edition
  • Microsoft Internet Security and Acceleration Server 2004 Standard Edition
  • Microsoft Internet Security and Acceleration Server 2006 Enterprise Edition
  • Microsoft Internet Security and Acceleration Server 2006 Standard Edition



SYMPTOMS

Consider the following scenario:

  • You are running Microsoft Internet Security and Acceleration (ISA) Server 2004 or Microsoft Internet Security and Acceleration (ISA) Server 2006 on a computer that has only one network adapter installed. This is known as a single-homed configuration. Typically, you use this configuration if the following conditions are true:
    • When ISA Server is located in the internal corporate network or in a perimeter network.
    • Another firewall is located at the edge that connects and protects corporate resources from the Internet.
  • A temporary network failure occurs. The network outage lasts for more than three minutes.
  • When the network connection is restored, the following event is logged in the Application log:

    Event Type: Warning
    Event Source: Microsoft ISA Server Web Proxy
    Event Category: None
    Event ID: 14148
    Date: Date
    Time: Time
    User: N/A
    Computer: Computer
    Description: The Web Proxy filter failed to bind its socket to IP address port 8080. This may have been caused by another service that is already using the same port or by a network adapter that is not functional. To resolve this issue, restart the Microsoft Firewall service. The error code specified in the data area of the event properties indicates the cause of the failure.


In this scenario, client computers cannot communicate with ISA Server until you restart the Microsoft Firewall service.

Note To restart the Microsoft Firewall service, use either of the following methods.

Method 1: Use the Services console to restart the Microsoft Firewall service

  1. Click Start, click Run, type services.msc, and then click OK.
  2. Right-click Microsoft Firewall, and then click Restart. If you are prompted to stop dependent services, click Yes to enable Service Control Manager (SCM) to correctly restart the dependent services.

Method 2: Use the command prompt to restart the Microsoft Firewall service

Type the following commands at a command prompt. Press ENTER after each command.

net stop fwsrv /y

net start fwsrv


Note The /y switch that is in the net stop fwsrv command enables SCM to stop the dependent services.

WORKAROUND

To prevent this problem, disable the TCP/IP Media Sense feature in Windows. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

239924 How to disable the "Media Sensing" feature for TCP/IP in Windows


STATUS

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

Keywords: kberrmsg kbhowto kbprb kbexpertiseinter KB925733