Hi everyone,

Yesterday I did an upgrade on our server from Windows 2000 Server SP4 to
Windows 2003 Server. Upgrade went fine but now I am having trouble accessing
Outlook Web Access (Exchange 2003 SP1).
On this Server I am running ISA 2000 SP2 and Exchange 2003 SP1. Before the
upgrade I had no problems accessing the OWA form the Internet. After the
upgrade I am getting an error message from the ISA2000 server saying that the
WebProxy service failed to bind the port 80 on the WAN interface. That
something else is already using it... The OWA works internally on the network
but I cannot access it from the outside world.

Now I had almost the same problem with IIS5.0 running on the Win2k server.
But there was an easy fix for that... I just disabled the SocketPooling
feature on the IIS5 and problem was solved... With the IIS6 on the W2k3
server this did not work. The script ran through fine but no results.. I'm
still getting the errors about the port binding.

Any help is appreciated
Rad Horak

Re: IIS6 hogs port 80 on external interface with ISA2k SP2 by John

John
Wed Aug 18 16:47:26 CDT 2004

See http://support.microsoft.com/default.aspx?scid=kb;en-us;813368

"Rad Horak" <RadHorak@discussions.microsoft.com> wrote in message
news:E92DC22B-168A-4401-BEF3-399B0446D3FE@microsoft.com...
> Hi everyone,
>
> Yesterday I did an upgrade on our server from Windows 2000 Server SP4 to
> Windows 2003 Server. Upgrade went fine but now I am having trouble
accessing
> Outlook Web Access (Exchange 2003 SP1).
> On this Server I am running ISA 2000 SP2 and Exchange 2003 SP1. Before the
> upgrade I had no problems accessing the OWA form the Internet. After the
> upgrade I am getting an error message from the ISA2000 server saying that
the
> WebProxy service failed to bind the port 80 on the WAN interface. That
> something else is already using it... The OWA works internally on the
network
> but I cannot access it from the outside world.
>
> Now I had almost the same problem with IIS5.0 running on the Win2k server.
> But there was an easy fix for that... I just disabled the SocketPooling
> feature on the IIS5 and problem was solved... With the IIS6 on the W2k3
> server this did not work. The script ran through fine but no results.. I'm
> still getting the errors about the port binding.
>
> Any help is appreciated
> Rad Horak