Hi all We have an RV042 loadbalancer connected to our two ADSL connections. We host some servers, including a web server (MS IIS 6.0 on Windows Server 2003) behind the load balancer. One of those servers serves as our NAT gateway, which our office LAN is behind. Those servers all talk to the load balancer via 1:1 NAT, which appears to work fine. However we've run into a performance issue, which I suspect is down to the load balancing arrangement. It only affects certain remote client sites, not all. Let's say the client has a WAN IP of 18.104.22.168, and our two public IPs are 22.214.171.124 and 126.96.36.199 (from two different ISPs). The client does an HTTP GET to our website, which resolves to 188.8.131.52. The webserver sends a reply back to the client. Now I have a feeling that this reply is being sent out from (and with a source IP of) either 184.108.40.206 or 220.127.116.11, randomly. Depending on the behaviour of the client's firewall/router/NAT, it is either associating these packets with the wrong source address with the session and accepting and forwarding them to the client, or not associating them and dropping/rejecting them. In the former case, there is no performance penalty and the site works as expected. In the latter case, performance is horrible as the client waits for a timeout and retransmission with (by chance) the correct/expected source IP address. On the test sites we have available, sites with linux boxes as NAT routers seem to have the former behaviour, but sites with residential gateway type boxes (eg linksys wag354g) have the latter behaviour. Is there a known fix here or are we just going to have to ditch the RV042? We need the RV042 for VPN endpointing too (again, this is a bit of a hack because we need the VPN to terminate on the inside of our office LAN, but as-is it terminates out in the 1:1 NAT subnet, which is tricky). Any suggestions here?