Welcome to ISAserver.org

Trouble with binding to port 80 - non newbie question

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Web Proxy] >> General >> Trouble with binding to port 80 - non newbie question

Page: [1]

Message

<< Older Topic Newer Topic >>

Trouble with binding to port 80 - non newbie question - 6.Jan.2008 1:57:51 PM

acrane

Posts: 6
Joined: 28.May2002
From: London, UK
Status: offline

Hi Guys,

I have been playing around with a test install of ISA 2006 and have noticed something a bit strange and would like to know if this a quirk or something by design. I know that this is not recommended but it must be allowed as SBS needs to do it.

Scenario:
ISA Server, dual NIC, connected to internal network (192.168.0.0/24) and connected to public network (aa.bb.cc.dd/29).

ISA server configured correctly and internal clients can get out (proxied on 8080) and relevant services published externally (OWA, SMTP etc etc).

External OWA listener is listening on 80 and 443 as is usual; only on the external ip address.

I want to create a dummy web site on IIS running on the ISA server (for a reporting app I am writing) listening on port 80. I can confirm that publishing of port 80 for auto config etc has been disabled on all network definitions and that no services are listening on port 80 for the internal IP address or NIC in total. The web site will not come up with ISA server running as ISA has bound to socket that I am trying to use.
This seems a little strange to me as I think that everything is stopped that corresponds to that socket (ie. internal ip:80) so I stop MS Firewall service and try web site again. Sure enough web site comes up. So next I try to start ISA and low and behold an error in the Application event log.

The Web Proxy filter failed to bind its socket to "external ip" port 80. 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.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Notice that the external ip address has not been claimed by the web site.
To confirm that this is not a spurious error, I stop the external web listener from listening on port 80 and try again. This time it works fine and I get no errors.

I guess my question is one of two things, which service is lying: is IIS claiming IP addresses and binding to them without my knowledge or is ISA server's listeners automatically bind to all IP addresses even though you have configured them not to?

Has anyone else seen this or have any insight? Would love to hear from you if you have.

Config details are as follows:

Windows Server 2003 R2 Std edition 32bit. Service Pack 2. Fully patched.
ISA Server 2006 Enterprise Edition

Thanks and happy new year.

Alex