webserver on wingate proxy problem

[sputnik]

newbie here, I have a wingate 6.0 trial install, with webserver as wingate client. I have a website on it that I can surf from my network, but people outside of my network get "page can't be displayed message". I'm hurting because it's my online portfolio and I can't pitch it to a potential employer,
halp!

thanks- Sputnik

[sputnik]

I tried, in thw www proxy server, general interface of wingate : changing service port to 8088, as wingate server is installed on webserver. I don't think this did the trick tho. All other settings are default, I just installed the wingate proxy server recently and haven't twiddled with it yet.

[Pascal]

The problem you're facing is that you have a web proxy listening on port 80 as well. Now, if you fine-tune your binding policies you should be okay. Depending on where the web-server is located, you might have two different solutions.

First make sure that the WWW Proxy Service only binds to your internal adapter.

Scenario 1 - Web Server on the WinGate machine
If the web-server is on the WinGate machine all you should need to do is to open a firewall hole by creating a port security action. Do this by going into the Extended Networking properties, switching to port security and creating a hole for port 80 [tcp] (If the webserver is listening on port 80).

Make sure that the web server you are using binds to your EXTERNAL adapter.

Scenario 2 - Web Server behind the WinGate machine
You have two choices here. You need to get traffic from the WinGate machine to the webserver. The easiest way is to go into Extended Networking Properties again and to create a port security action as before - but don't make the action "Allow Packet". Make it "Redirect Packet" and redirect it to the internal IP of your web-server.

As an alternative - create a TCP Mapping. This is a proxy-like service, but then take care to bind it to the external IP only and to redirect it to the IP of your web-server.

Good luck!

[sputnik]

Hi, thanks so much for the pointers.
My setup is "scenario 1", webserver on Wingate machine.
I'm not well versed on port lingo yet, tho, so can you clarify
for me the specifics of "creating a hole for port 80".

Within the Extended Network Driver: Port Security interface:
I see my options as
"LAN connections to internet" and
"Connections from the internet".

Can you guide me as to which of the 2 to use(or both) and the actual settings within beyond the TCP election ?

Thank you thank you

[sputnik]

figured out the "creating a hole for port 80" - just did what seemed logical,

Within the Extended Network Driver: Port Security interface:
chose to add 'Connections from the internet',
-checked "internet computers to the Wingate PC" TCP
ports 80 to 80
allow packet
cloak connection failures

thanks again for pointing me in the right direction..

[Pascal]

Yup, you got it all right. Glad to hear you got it working.