Description
When trying to publish HTTP websites (on port 80), the published websites aren't working. Published HTTPS websites (on port 443) are working normally.The following error message is written to the eventlog:
The Web Proxy filter failed to bind its socket to A.B.C.D 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.
A.B.C.D is the TMG's external IP address.
When trying to disable rules for this IP the following message is written to the eventlog:
"A problem preventing the Web Proxy filter from binding its sockets was resolved"
When checking the listeners with netstat -ano, you see PID 4 is listening on port 80 on all the IPs. PID 4 is a system process.
Solution
The problem is caused because the http service is listening to port 80 on all IPs.Opening "Command Prompt" and running the following command:
netsh http add iplisten ipaddress=127.0.0.1
and restarting the TMG services (or rebooting the server) solves the problem.
Affected software:
Threat Management Gateway (TMG) 2010Threat Management Gateway (TMG) 2010 SP1
Threat Management Gateway (TMG) 2010 SP2
Comments:
| Comment #1 from Buff [Username: Guest] at 07/07/2011 10:00 | |
| The forum is a brgither place thanks to your posts. Thanks! | |
| Comment #2 from luiscperu [Username: Guest] at 12/08/2011 02:49 | |
|
OMG, thank you thank you. I will sue microsoft for these kind of bugs. |
|
| Comment #3 from luiscperu [Username: Guest] at 12/08/2011 03:35 | |
|
OMG, thank you thank you. I will sue microsoft for these kind of bugs. |
|
| Comment #4 from MinhSang [Username: Guest] at 26/11/2011 18:59 | |
| Thank you, It also valid in TMG 2010 SP2 | |
| Comment #5 from Addiction [Username: Guest] at 01/06/2012 08:12 | |
| Thanx alot for ur resolution on this annoying matter. Microsoft should hire you! | |
| Comment #6 from Mix Master Mic [Username: Guest] at 29/10/2014 16:33 | |
| OR it could also be that you are running ISA Server 2004 which uses port 8080 AND you also have a website running on the server that is also running in port 8080... |