You receive a "Web Proxy service failed to bind its socket" event message when you use both IIS and ISA Server 2000

When you use both Internet Information Services (IIS) and Internet Security and Acceleration (ISA) Server 2000, you may receive the following event in the event log:

14147: Web Proxy service failed to bind its socket to %1 port %2. This may be caused by another service that is already using the same port or by a network adapter that is not functional.

This problem occurs when the Web Proxy cannot bind the forward Web listener’s port because IIS is already using the port.

If you make publishing rules, make sure that IIS is not listening on the respective port.

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

The 0x80072740 error code in the data area occurs if another program is using the port. After the outgoing Web requests listener is reconfigured, the Web Proxy tries to bind to the port in the new configuration. If that does not work, the Web Proxy returns to the same condition as after a failure during startup, with no port bound and waiting for reconfiguration. If the other program, such as IIS, is reconfigured not to use another port, the port for the ISA Web Proxy is freed. Also, the Web proxy does not retry to bind, because it does not monitor the port or the other program to determine when the port is freed. In the case where you are reconfiguring the other program, use one of the following methods to make the Web Proxy service try again to bind to the port:

• Restart the Web Proxy service.
• Reconfigure the Web Proxy service to a different port, and then re-configure the service back to the original port.