Wingate V6 not redirecting

[dbs]

Dear Support,

We have a customer who are using Wingate Pro with a port direct to allow a computer on their internal network to get information from an advertising server. With Wingate 5 installed and using 3 network cards - 2 load balanced and 1 for their broadband connection everything worked as planned - the port redirect was setup in extended networking and NAT did the job.

After installing Wingate 6 this no longer works, I have checked that the network cards are specified for the correct job, i.e 192.168.0.1 load balanced on the internal trusted and 192.168.1.1 with a gateway of 192.168.1.254 for the external untrusted, but the redirect on the firewall always appears to have a destination of 192.168.1.1.

Any ideas?

[adrien]

Hi

What port is this on. Is it on the same port as any service running in WinGate?

So if I understand you correctly, you have effectively 2 interfaces, one is 192.168.1.1, which is connected to your broadband router on 192.168.1.254, and is marked as external, and the other is 192.168.0.1.

So, for this redirect to work, the adapter 192.168.1.1 must have an adapter usage of "external", and the other one must have an adapter usage of "internal" - you can edit this on the Network Connections pane of the Network tab in GateKeeper. Then the previous port range settings that you had for WinGate 5.x should still work, i.e. "connections from the Internet", redirect port XX to A.B.C.D etc.

Adrien

[dbs]

Port 5900 and no service is using this port.

Yes the 2 interfaces are 192.168.1.1 and a broadband router of 192.168.1.254 marked as External in Wingate, and 192.168.0.1 marked as internal.

I have deleted and re added this port redirect and still it tries to go to 192.168.1.1 on any port redirect.

[adrien]

When you say "tries to go to 192.168.1.1" I'm not quite sure what you mean.

Does this mean that any incoming connection on port 5900 that comes through your external firewall, and comes to your WinGate machine, instead of being redirected into your Internal LAN, it goes and tries to connect to the WinGate machine itself?

Thse packets will have a destination address of 192.168.1.1 because of the redirect on your external gateway.

I you change the port range setting to deny, do the packets then show up in the Firewall as blocked?

Adrien