Multiple Gateways not being used by Wingate

[allteks]

Hi,

I have installed Wingate on a server to be used as a proxy for our users. They main reason for the proxy is to use the multiple gateways feature to enable failover for web users.

I have 3 web connections at our office. All routers are on the same subnet and are reachable from the server. The server has a default gateway of 192.168.1.22. This is the primary Internet connection and one that I dont want users to us.

There are two other routers available on .1 and .2. So I added these two extra gateways into the Windows 2003 IP stack and ave them a higher Metric so the main gateway wouldn't get affected.

I then added them into the gateways tab on the www proxy service within Wingate. Add had it so the default is .2 and if that fails go to .1.

Nice and easy I thought. However whenever I go out on to the Internet I am using the .22 router, the servers default gateway. It seams that the gateways feature of Wingate is making no effect at all.

Any ideas anyone?

[adrien]

Hi

2 things to check.

1. That Windows firewall isn't running - that breaks gateway selection because it changes the source port numbers for outgoing connections, so WinGate ENS doesn't match the outgoing connection with the one from the engine.

2. That your users are actually going through the WWW proxy. Is this intercepting connections?

Adrien

[allteks]

Adrian,

Thanks for the reply. I have checked and Windows Fwall isn't running, and yes the clients are definately using proxy. The clients actually have a different DG (192.168.1.1) so its easy to tell if the proxy is intercepting or not.

any other thoughts.

thanks again

Steve

[jamesc]

When you say that the Windows Firewall is off, in the control panel or the Windows Services? I recommend turning it off in the services so you knock out MS's implementation of NAT.


(Qbik: there was a support ticket made for this today in GS; replied and also asked for more info so we can review AllTeks settings)

[allteks]

Firewall Services are disabled.

I have tried the same implementation on another server and have the exact same issue. On both servers the ENS driver wont load either. They are both Dell servers running Windows 2003 R2.

Steve

[jamesc]

My response in the support ticket may be in your spam folder? I have included it here too.

Just received word back from one of our developers. To get ENS loaded on your Dell PE850, you will need to install a Non-Dell Windows Operating System, I know it is not convenient but we believe there is not a lot more we can do regarding ENS failing to load.

*Alternatively, let us know if you can make it work or if we can have a session on the box via Remote Desktop; it may not be until next week.

[allteks]

ok, I have installed this on a non dell server and get the same results. Is it something to do with haveing metrics on the gateways under the IP stack?

[allteks]

scratch the above post ...nothing to do with Metrics as the DG's are all set to automatic and it makes no difference.

[Pascal]

Is ENS loading on the new server?

[allteks]

yep ens works fine. Everything is fine except failover!!

Cheers

Steve

[allteks]

I have a fix for this....

I remove the extra gateways out of the network settings so it just shows the default gateway. If I then add the 2 routes, one for each gateway, via route add the failover function works. Seems a strange way of doing it as route print shows exactly the same information both ways. Anyway problem solved.

Thanks for the help

Steve

[Pascal]

Interesting, I was discussing this with Adrien yesterday.

When alg.exe (Application Layer Gateway - Windows Firewall / ICS) is running it performs translation that changes what we are expecting to see between the WinGate Engine and the WinGate Driver. Thus, it could prevent us from enforcing the right gateways.

So, either that wasn't causing your problem or you found a way around it!

[adrien]

hi Steve

That's really interesting about the difference between adding the routes via the network adapter config, vs route add command.

I presume all the routes still showed up in GateKeeper, and all the gateways?

In testing here, we've just added extra gateways using the network config dlg, but admittedly I haven't tried this on 2003, only 2k.

Adrien

[allteks]

Yes, to my surprise the extra gateways where there to be selected.

All seems fine now though. Just need it to work on a Dell installed O/S!!

Steve

[adrien]

Yeah looks like we may have to buy one to test on. They won't lend us one.

Adrien