6.5.2 looses under ENS / port security a REDIRECT of Port 80

[sigih.]

Hello again !

now 6.5.2 has an unknown reaction.
I ADD a REDIRECT of PORT 80 and under ACTION I REDIRECT PACKET TO IP ADDRESS 192.168.0.1 and OVERRIDE PORT to 8000 for INTERNET COMPUTERS TO THE WINGATE PC on TCP.
Port 8000 has the Webserver behind Wingate at 192.168.0.1.
I Press OK and all is OK and works fine.
I can reach the Webserver via Internet and our guys from outside can get there infos on our webserver.

But after a reboot of the Server there is no REDIRECT ... only a ALLOW PACKET under PACKET and the REDIRECTion is lost.
No connection is possible from outside.
I have to set the REDIRECT every time again ...

Has anybody the same effect.
Is there another way to redirect the ports ?
Do I have something wrong ?

regards
sigih.

[logan]

There is probably a proxy server in WinGate claiming port 80. When WinGate starts up, any running proxy services will create holes in the firewall for themselves. These holes override manually created holes. To stop the automatic holes from being created and overriding the manually created ones, you will need to disable the proxy service creating the hole or change its bindings.

If this is not the case, the the new settings might not be getting saved to registry. Try clicking the save button in the GateKeeper before restarting WinGate to see if the changes remain.

[sigih.]

@ LOGAN

So now I disabled the WWW Proxy and made the REDIRECT in ENS manually - now it working and also after a reboot the redirection is still here.
Now another question:
The bindings in WWW Proxy are away - only under POLICY BINDINGS the entrys are here - think this is OK and I have the same Firewall security or do I have less sec. on port 80 now?

regards
sigih.

[sigih.]

@ LOGAN again ...

still working but now under HISTORSY / ACTIVITY I see only the NAT information from the clients - before I saw the ACTIVITY in clear text ... http://...
Not a great problem but the detailled information before was better to find bugs on the clientside ... is there a way to get "both" - redirection + detailled informations ?

TNX
sigih.

[adrien]

the entries in the port security table are set up by the proxy depending on which interfaces the proxy binds to.

For Internet connections to the WinGate computer to get messed up by the WWW proxy bindings, the WWW proxy must have been configured to be bound to the external interface.

For connections to now show up as NAT where before they showed the URL, means you turned off either connection intercepts (WWW proxy server->Sessions tab), or your proxy isn't bound to the internal adapter.

The default policy for binding for most services is to bind to any internal adapter. This should work for you.

[sigih.]

@ adrien

TNX ... now I understand the redirect function ...

But is there a way to see the traffic on the website from outside ?
At the moment the webserver behind is on port 8000 - can also change the port to a "better" one ...

regards
sigih.