Re: Alert!Web proxy filter not binding on External and Internal Interf
- From: "ZVR" <nospamever@xxxxxx>
- Date: Tue, 30 Aug 2005 18:20:03 -0400
You are probably running IIS on the same machine. That port (TCP 80) can
only be used by one service at a time, so if IIS is active you won't be able
to run the web proxy service in the same time, on the same port.
Virgil
"tkavanagh" <tkavanagh@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3541FF6B-C6DC-4376-8393-3F4F7EFEE47A@xxxxxxxxxxxxxxxx
> Good Day,
>
> I'm getting this alert since upgrading from ISA 2000 to ISA 2004.
> I'm running Service Pack 1 for ISA server 2004.
>
> I restarted the Firewall Service and the problem continues.
>
> Any Ideas?
>
> Thanks,
> Tommy
> Event Type: Warning
> Event Source: Microsoft ISA Server Web Proxy
> Event Category: None
> Event ID: 14148
> Date: 8/30/2005
> Time: 3:37:43 PM
> User: N/A
> Computer: ISAWEB
> Description:
> The Web Proxy filter failed to bind its socket to 65.240.173.212 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.
> Data:
> 0000: 1d 27 07 80 .'.?
>
.
- References:
- Prev by Date: reconnecting disconnected clients
- Next by Date: Re: "page/authentication" expiration for OWA publication
- Previous by thread: Alert!Web proxy filter not binding on External and Internal Interf
- Next by thread: Can't Access Specific Websites
- Index(es):
Relevant Pages
|
