RE: Block Web access for non-Web Proxy clients
- From: "Ara" <ara@xxxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Tue, 5 Apr 2005 12:44:33 -0700
Dan,
Thank you for your email. I have it applied but I get this error. Is it
the cause that your internal isa ip address differs from me?
The Web Proxy filter failed to bind its socket to 192.168.1.254 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.
The failure is due to error: 0x80072740
-----Original Message-----
From: Ball, Dan [mailto:DBall@xxxxxxxxxxx]
Sent: Tuesday, April 05, 2005 12:18 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Block Web access for non-Web Proxy clients
http://www.ISAserver.org
True, you should be able to add that port into the protocol definition
created in your instructions also. Glad you pointed that out, forgot
about that, all they'd have to do is switch to https (if that site
supported it) instead of http and it would go through after all...
-----Original Message-----
From: Thomas W Shinder [mailto:tshinder@xxxxxxxxxxx]
Sent: Tuesday, April 05, 2005 13:34
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Block Web access for non-Web Proxy clients
http://www.ISAserver.org
Hi Roy,
The users will still be able to disable the Web proxy settings. They
just won't be able to get to any resources requiring outbound access TCP
80, and I assume we can do the same thing with TCP 443, since the same
principles apply.
Tom
www.isaserver.org/shinder
Tom and Deb Shinder's Configuring ISA Server 2004
http://tinyurl.com/3xqb7
MVP -- ISA Firewalls
Other related posts:
