IIS 5 and Wingate on same PC

[moldi]

So I have IIS running on the server and wingate 5.07
I need the transparent redirection (TR)
I need the webserver on port 80
I have 2 NIC's on3 192.168.0.3 and 81.196.19.xxx
IIS has been set to run onlyon 81.196.19.xx, but it still listenes on all IP's
so if wingate is allready started, the webserver won't start
I tried to set the proxy on 8080, but the TR won't work with that.
WHAT TO DO?

[tim]

So I have IIS running on the server and wingate 5.07
I need the transparent redirection (TR)
I need the webserver on port 80
I have 2 NIC's on3 192.168.0.3 and 81.196.19.xxx
IIS has been set to run onlyon 81.196.19.xx, but it still listenes on all IP's
so if wingate is allready started, the webserver won't start
I tried to set the proxy on 8080, but the TR won't work with that.
WHAT TO DO?

Hi, simply disable the external bindings for the proxy. You then need to add a Firewall hole for port 80 for external connections.
IIS will need to be made to listen just on the interface you want. It will do it, but its best to stop the W3SVC, make the change in IIS control, and restart the service.

Tim

[moldi]

As I have said before:
the IIS is set to listen only on 81.196.19.xxx
Wingate WWW proxy is only listening on 192.168.0.3
BUT IIS listens on all interfaces and replies only to those on 81.196.19.xxx
WHY? don't know.

I can see this in SYGATE. It show that wingate is listening on 192...port 80
but IIS is listening on all interfaces on port 80

If I start first IIS and then Wingate. Everything is cool, otherwise, I don't have a working website anymore.

My question is: If I do want TR, but on port 8080 for example, or any other port than 80, what to do?
(there should be at least an alternate port)

[moldi]

IIS and Wingate services set on MANUAL start/stop
Installed Firedaemon and set it to run the following .bat

net stop "www..."
net stop "qbik..."
net start "www.."
net start "qbik..."


In this way I am certain that the WWW server will start before the wingate service does.

You should really take in consideration TR on 8080 also!

[adrien]

One way around this is to make IIS run on a different port, and use a TCP redirect in the ENS to map external connections to the new port on the same machine.

Then you can run the proxy on port 80 without conflict, and use TR.

Adrien