Jon Bendtsen wrote:
Always include the list unless it really has to be elsewhere.
Den mandag 6.feb kl. 22:14 skrev Steve Willis:
Actually, I've almost got this working over tun now. I switched from tap a few days ago (poor performance), and am pushing the "NBT 2" option to the client. Now, each client can see the WINS server's shares in their Network Neighborhood, but can't yet see each other.
In any case, my question still applies, even if I switch back to tap.
Why do the clients even need to connect to the openvpn server if they are
Not all clients are in the same location. There are "clusters" of employees in different buildings. The physical setup is more like this:
Building A: server 1 server 2 employee 1 employee 2 employee 3
Building B: server 3 server 4 employee 4 employee 5 employee 6
Building C: OpenVPN server (co-located)
I want all employees to be able to see servers 1-4, which OpenVPN has done for me nicely. Now, image that you are employee 1, in building A. You are always connected to the VPN so that you can access servers 1-4. However, servers 1 and 2 are local to you. When the name "server 1" shows up in your Network Neighborhood, which route does it use? I'm looking for a way to ensure that it always uses the fast local LAN.
Now, you (employee 1) take you laptop on a road trip. You are still connecting to the VPN, but now you must use the VPN to connect to any of servers 1-4. You shouldn't have to do anything different on you laptop now from when you had it in the office (so no permanent modifications to Windows that will always force routing to the LAN.) For example, you shouldn't have to specify the VPN IP address of the server instead of the LAN IP address just because you are out of the office...the same WINS name should work in both places.
Just to clarify, I have all of the above set up and working. I'm just looking for a way to guarantee that when employee 1 is sitting in his office, his connection to the server in the next room is not taking a 100 mile round-trip because Windows chose the wrong route, without employee 1 having to specify whether he is in or out of the office. Prior to this, we were using SFTP servers, and experience has shown that if any changes have to be made to make a connection work out of the office (like remembering to specify a different IP address to conenct to), the less technical employees have problems.
Thanks for the advice!
____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users