Wingate ignoring NIC bingings?

[Anifinity]

I have 2 network adapters in my computer, each with their own router and external connection to the internet through 2 different ISP's. I have just setup a WWW proxy server and set 2 bindings, the first for my Primary NIC and the the second for my Secondary NIC. For the primary NIC, It is currently showing 192.168.1.126 as the IP address from my router and for the secondary NIC it is showing 192.168.0.100. If I setup an HTTPS proxy in firefox using 192.168.0.100 on port 80, I will only have web browsing when I turn on the binding for that specific adapter (this makes sense); if I enable the binding for my other NIC but leave firefox configured for the first NIC, the proxy server does not respond (as expected).

Since I am only able to get connectivity when my HTTPS proxy settings match the active binding in wingate, this leads me to believe the proxy is functioning normally.

The issue is, if I check the IP address in the web browser, both bindings show the same external 70.70.xx.xx IP address, despite the internet connections coming from completely different ISP's. According to each of my routers, the primary NIC should use IP 70.79.xxx.xxx while the secondary should show 69.172.xxx.xx.

What can I do to correct this? It definitely seems like connections are leaving the same interface to the internet despite the bindings.

Any help is appreciated.

[adrien]

Hi

We've found that the OS will choose the outgoing interface and next hop (e.g. gateway) based on the system route table and destination address of a packet (source IP), regardless of the interface a connection is bound to. This will in practice always go to the same one. Are the metrics for both default routes the same?

You may be able to get around it if you can configure the port forwarding on your routers to perform NAT (e.g. to translate the source address incoming to the router's internal address).

Adrien