wingate blocks client access to hotmail and secure sites

[joverdorf]

I'm using Wingate 5.2.3 as a proxy server for my tiny home network. Recently I fooled around with my firewall settings to try to make the network more secure, blocking certain ports. Afterward, my client machine could no longer access any https sites, including hotmail, our banking site, etc. I've read a bunch of posts related to this problem, but none of them give me clear instructions what to do.

Can anybody help? I've already reverted to the default security settings, deleted and restored my www proxy, stopped and restarted wingate engine, etc.

jason_overdorf@hotmail.com

[genie]

Make sure that the HTTP proxy allows secure access to the ports you need: go to HTTP proxy properties, page HTTPS connections.

[joverdorf]

Your description of the pages was a bit mystifying as there is no http proxy, but I checked the WWW proxy under the https tab, and it is enabled to accept any port. Unfortunately the problem is still there.

[labull]

Jason,

SSL is usually on port 443.

Try opening this port.

Larry

[joverdorf]

thanks.... unfortunately that didn't solve the problem. Port 443 is open and so is port 8080, which is the one the client is set to use for https. I'm stumped.

Jason

[genie]

Is it HTTPS traffic only that gets blocked? Check the firewall config and make sure that port 443 is not being blocked or redirected.

[MattP]

Did you say that the client is being directed to use port 8080 for SSL connections? Where have you specified this? SSL is usually sent over port 443, perhaps you should reconfigure your client to use this port for SSL?

Matt

[joverdorf]

Yes, only the https sites are blocked, eg hotmail, bank sites, etc. The port for ssl was set on the browser's proxy settings. I tried resetting to 443, but that didn't solve the problem.

[genie]

Hold on - in your client's browser you have Web proxy set to Wingate machine, don't you? Do you have TR for HTTP proxy?

[joverdorf]

Yes, I have client's browser set to use host machine's IP address as a proxy, with the standard ports. On the server machine I'm running wingate with www proxy set up.

[joverdorf]

BTW: I hope this doesn't sound dumb, but what is TR?

[genie]

Oh, sorry - Transparent redirect.

[joverdorf]

As far as I know, there's no transparent redirect set up. The only place I saw something like this was under the "www proxy" tab for non-proxy requests, which is currently set to "reject"

[Nev]

As far as I know, there's no transparent redirect set up. The only place I saw something like this was under the "www proxy" tab for non-proxy requests, which is currently set to "reject"

Hi Jason,

Where they are pointing is to the Sessions tab for the WWW proxy, you can enable T/r to intercept NAT/WGIC requests that way.

Nev.

[joverdorf]

I tried setting up transparent redirect, and that caused it to keep searching infinitely for the login page instead of telling me there's something wrong with the proxy setup. Weirdly, this continued after I changed back to no redirect.