Wingate not redirecting SSL port 443

[Jim Edison]

Hi All,

Long time Wingate user and this just seems too simple to really be giving me a problem.
Wingate 6.0.4 running on a Win2000 stand alone workstation, Internal and external NICs running ENS

I have web servers (Windows Server 2003 running IIS 6) running behind Wingate and am using a www proxy service to redirect to the severs on various ports - NOT SSL

I added a new server that needs to run https on ssl std port 443. Simple enough to setup a new www proxy on port 443 and Pipe Server Requests to my new server at the internal IP on port 443 but it will not work.

I can access the server on https at the internal address but when I get outside Wingate simply displays (in activity) http when I would expect it to display the full path of the resource which is included in the request. Further strange is that I specifically set the Extended Network Driver Port security on the Auto created tcp port 443 to notify on access and get nothing. It is as if the request is dropping in Wingate, the activity shows there is a connection but no further information other than http and no path or page request.

I have been over my NICs and my DSL router to make sure I was not filtering something there and nothing. The problem seems to be centered on port 443 and https requests. Any input is greatly appreciated.

Thanks Jim E

[genie]

Jim, can you do traffic capture on Wingate machine for this port?

[adrien]

Hi

WinGate doesn't make an SSL connection inbound in this case. It will accept the connection with SSL, but won't make an SSL connection to your internal server.

If you want the internal connection to be also SSL, better to just use a port setting on port 443 in Extended Networking to pipe through to the internal server without involving the WWW proxy.

Regards

Adrien

[Jim Edison]

Hi Genie and Adrien,

Thanks much for your posts. I forgot to consider what a proxy really is so opened the port in EN but had to change a rule to allow a guest in and all worked great. This however raises another question for which I will start another thread Re: security and certificates.

Thanks Again, Jim E