Windows server 2008 and www proxy binding problem

[mother111]

With 6.5 installed mail works, however with all my windows firewalls down everytime I add a internal or ext binding for www proxy I get error and does not start. What am I missing?

Error log.

01/23/09 15:55:58 Error: Service failed startup on interface 127.0.0.1:80 error 10013
01/23/09 15:55:58 Error: Service failed startup on interface 192.168.10.1:80 error 10013
01/23/09 15:55:58 Error: Service startup complete or partial failure
01/23/09 15:56:12 Service stopped
01/23/09 15:56:15 Error: Service failed startup on interface 127.0.0.1:80 error 10013
01/23/09 15:56:15 Error: Service failed startup on interface 192.168.10.1:80 error 10013
01/23/09 15:56:15 Error: Service startup complete or partial failure
01/23/09 15:59:17 Service stopped
01/23/09 15:59:26 Error: Service failed startup on interface 127.0.0.1:80 error 10013
01/23/09 15:59:26 Error: Service failed startup on interface 192.168.10.1:80 error 10013
01/23/09 15:59:26 Error: Service startup complete or partial failure
01/23/09 15:59:36 Service stopped
01/23/09 15:59:41 Error: Service failed startup on interface 127.0.0.1:80 error 10013
01/23/09 15:59:41 Error: Service failed startup on interface 192.168.10.1:80 error 10013
01/23/09 15:59:41 Error: Service startup complete or partial failure
01/23/09 15:59:49 Configuration changed
01/23/09 15:59:53 Service stopped
01/23/09 15:59:55 Service started successfully
01/23/09 16:32:51 Service stopped
01/23/09 16:32:57 Service started successfully
01/23/09 16:36:56 Configuration changed
01/23/09 16:36:56 Error: Service failed startup on interface 127.0.0.1:80 error 10013
01/23/09 16:37:28 Configuration changed
01/23/09 16:37:28 Error: Service failed startup on interface 192.168.10.1:80 error 10013
01/23/09 16:37:56 Configuration changed
01/23/09 16:38:05 Configuration changed
01/23/09 16:38:05 Error: Service failed startup on interface 65.39.85.146:80 error 10013

[mother111]

Tried wingate on port 85 and the bindings work, however my webserver is on 80. I case this helps anyone.

[genie]

This is access denied error. Make sure there are no other applications running on port 80.

[mother111]

Solution/Workaround...Did not find the port 80 conflict, however just changed to port 85 in wingate and changed one of the network browsers to in the "LAN Connection" settings to port 85 and everything is working. The more I understand this product the more I enjoy it. KUDOS

[steve1]

Still having problem is there a work around for may WWW service "error" when adding any bindings. My website server (iis 7) runs on port 80 hower conflicts with wingate that is on 80. All firewalls a "off" at present
What can I do anyone!

[logan]

You can't have two services running on the same port. You will need to change either IIS, or the WWW Proxy to use a different port number. Port 8080 is the most commonly used alternative.

[steve1]

You can't have two services running on the same port. You will need to change either IIS, or the WWW Proxy to use a different port number. Port 8080 is the most commonly used alternative.

So changing my webserver to 8080 and leaving the wingate at 80 internet viewer will still be able to view my website? Thanks

[logan]

Only if you tell your visitors to go to port 8080 instead of the usual port 80.

I recommend changing the proxy to port 8080, and leaving IIS on port 80 if IIS is running a comercial website.

[steve1]

Yes that is what I did wingate set to 8080. I hope that clients can see my website now.
Can you check if not to busy? Much appreciated.

URL removed

thanks

[logan]

yup, its there

[steve1]

yup, its there

Thank You