christian.mackin@kohlex.com
I am trying to connect with two Access Servers on AWS that are geographically in opposite direction from my client location. The latency to each Access Server on AWS is 50ms to the west and 150ms to the east, respectively. In order to reduce series latency, I would like to connect to these servers in parallel. Otherwise I would effectively end up with more than 200ms latency from the east server.
I have read online about adding an additional TAP adapter, which I have added. I have loaded two profile configurations into the configuration folder. I can connect to each server independently, but if I try to connect to both at the same time I get the following error:
WARNING: Failed to renew DHCP IP address lease on TAP-Windows adapter: The operation was canceled by the user. (code=1223
I have been trying for several weeks to get this network solution working. Any community support would be greatly appreciated.
The Johan
Often when people try to connect to 2 OpenVPN servers at the same time they run into routing collissions or subnet collissions. This is incidentally the primary reason that the client that comes with the Access Server is consciously limited to just 1 server - it won't do 2 at the same time.
If you use the community edition and add a second TAP adapter, you can connect to two Access Servers at the same time but you should ensure that they are not set to route all client internet traffic through the Access Server (there's your first collission already) and that the subnets that you use on both Access Servers for both the subnets that you want to access (give clients access to) and that the VPN clients themselves are on are unique and don't overlap.
If you use bridging, you're gonna have a bad time too, with this kind of setup. If you use routing you should be okay.
