Re: ISA Server Web Proxy and port usage

Thanks for your assistance,

please note that now my clients work as gateway and proxy clients and they are ok with Internet access.

I have some further questions to ask about your reply.
1) As you can see in the error description, it is the web proxy filter that fails to bind. Is it the same as web proxy or they are different? I noticed though that the web proxy listener uses port 80 but I have not seen web proxy filter as such anuwhere.
2) I already use port 8080 for proxy from the standard installation of ISA and this is the port I configure the clients to use in IE. Can it be used here again?






"Brandon Jiang[MSFT]" <jybao@xxxxxxxxxxxxxxxxxxxx> wrote in message news:GfHQTCvEJHA.1640@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello Andreas,

Thank you for your post. This is Brandon and I will be assisting you in
this post.

From your previous post, I know you receive the following warning which
mentions Web Proxy fails to bind 80 port because it is used by other
service or application. Please correct me if I have any misunderstanding.
Event Type: Warning
Event Source: Microsoft ISA Server Web Proxy
Event Category: None
Event ID: 14148
Date: 08/09/2008
Time: 15:11:34
User: N/A
Computer: *******
Description:
The Web Proxy filter failed to bind its socket to 81.4.*.* 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.

This error means ISA service fails to listening on port 80 because it is
occupied by other service or application. It could not be ignored. Please
allow me share you my analysis.

Analysis:
1. ISA service will listening on the configured web proxy port.

2. Any http traffic originated from Web Proxy Client will be forward to
this web proxy port, then ISA will handle those traffic.

3. If ISA service cannot listen on that port, the http traffic will be
unable to pass through ISA.

4. As you know, port 80 is used for ISS by default.

According to this analysis and behavior, I would recommend you configure
Web proxy to listen on other port, such as 8080.

Suggestion:
Change web proxy port to other port, such as 8080.
You can configure it from "web proxy" tab in the properties Window of
"Internal" network",

If you have any question on my reply or any further question or concerns on
this topic, please feel free to post back.

Thanks and Have a good day!

Warm Regards,
Brandon Jiang

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
~~~~~~~~~~~~~~~~~~~~~


.

Relevant Pages