adrien wrote:Is this being accessed on an intranet or inbound from the internet?
If Inbound from the internet, then it should just work on that port (although it will mean the people will need to have a :90 on the end of the server name in their URLs which is a drag).
If from the Intranet outwards, then there may be a problem. WinGate will not allow you to NAT through to the external interface of itself as a destination. It instead relays the connection up the local stack instead of NATting the connection.
However, is there any particular reason you need to host on port 90?
Which web server software are you using?
You could simply run it on port 80, and disable the WWW Proxy in WinGate.
Adrien
I am using Microsoft IIS5
I have 3 Intranet sites (which the client will be inbound from local routing)
I have 1 Internet site (which will receive traffic from the internet)
I can not disable the WWW Proxy service, as that is the entire reason I am using wingate; for all outbound traffic from LAN/WAN routing must, according to our policy, go through the proxy.
I can not rely on the client to put in :90 on any of the sites. I must allow them to run as if they are on the default port.
Additionally, previously I was able to set up Non Proxy request to route to the same server (IIS and Wingate reside on the same server) via port 90 and it worked. This no longer works for some reason.
To summarize, I need to be able to run IIS Websites on port 90 w/out requiring clients to know about it. I need WWW Proxy Service for all outbound internet traffic. I will have an Internet site also on this server that needs to be able to accept inbound traffic from the internet to port 90 seemlessly to the client.
I was told this was possible when I bought the software.