WWW proxy only works from LAN not external IP

[bret10]

I have searched all over this forum and the WinGate knowledge base and have yet to find an answer...

I would like to be able to use the WinGate server to access the internet from work, abroad, etc. Right now I can only get the proxy to work through my local LAN accessing the gate directly through 192.168.1.105:80. But when I change the proxy address to my external IP x.x.x.x:80, I cannot connect?

WinGate is behind a router with DHCP. I am using a typical WinGate installation.

What I have done:

I checked port 80, I can verify that it is open.
I have bound the WWW proxy to my external interface.
I have disabled DHCP and NAT in WinGate, (as this is taken care of by my router).
I have no firewalls active and the WG firewal does have port 80 open.

I have also tried SOCKS on port 3128 (which is open via router and firewall) and have the same problem.

Also, is there a way that I can specify which ip addresses can connect?

Thanks

[adrien]

Hi

What sort of internet connection do you have, and how many network adapters?

for example, if you are using a DSL/NAT device to connect to the net, you'll need to open a port (80) in that and forward it to the WinGate server.

You'll also want to secure WinGate so only authorised users can access it from the outside, else you'll find lots of people surfing through it pretty quickly.

when you say that you see no bindings in the WWW proxy when you set the binding policy to bind to external, that indicates there's no external adapter (or no adapter installed that is marked for external usage) hence my second question.

Adrien

[bret10]

I have cable internet and only one network adapter installed on my computer, though its listed twice. once as local area connection and another as broadcom (the actual chipset). Local area connection is listed as "internal" and the broadcom as "external". when i add a binding for 'any external', it does not bind the broadcom. when i add a binding for 'any internal', it binds the Local Area Connection. If I change the Local Area Connection to "external" it does bind as external. but in either scenario i have the same problem, no connection from internet.

I have a router between the cable modem and my wingate server. But I have already verified that port 80 is open and can send/receive. I even went to the extend of adding a port forward for port 80 (and 3128 for SOCKS as 1080 is blocked by isp) in the router setup. Both ports are open as mentioned in previous post "I checked port 80, I can verify that it is open."


UPDATE:

When I look at the History Column, I can see other computers connecting to my WWW proxy and my SOCKS.

I see:
vpn8.hotplots.net 83.169.60.33 SOCKS Connect 74.125.39.19:443
vpn8.hotplots.net 83.169.60.33 SOCKS Connect 74.125.39.19:443
222.134.77.71 htp://ww....
115.195.251.135 htp://ww...

Obviously this is external traffic. So is it possible I am setting up my proxy incorrectly? It works with my internal lan ip: 192.168.1.105:80, but not with xx.xx.xx.xx:80, from the lan or an external source. But obviously people are getting here, is there a way to see exactly address they are accessing when they connect with wingate