Make it easier for normal users to connect with the GUI
Posted: Fri May 02, 2014 7:16 am
Hello!
I hope everyone here is having a great day!
My boss gave me a mission to find a OpenVPN solution which is simple for the users when they are outside the office.
So this was my boss wishlist:
1. When a client connects to the OpenVPN server (which is on a windows server) the openvpn client should get an ip from the windows dhcp server and not from the openvpn server. (After hours and hours of testing I couldnt get this to work. So now the openvpn clients is running on a network range separated from the LAN users and I route the traffic between the OpenVPN clients and the network devices in the office LAN. If someone have the solution to this problem feel free to inform me about how to set this up)
2. When a client connects it should promt for UserID and Password, which should be checked against the Windows AD. (I havent checked how to do this, so right now he got certificates which has to be installed on every client that needs to have OpenVPN access.)
3. Find a more user friendly gui than the one you can find in OpenVPN.
Well this is where I am right now. I would like to use the OpenVPN client GUI but the users wouldnt understand how to connect(or they would get annoyed about how many steps they need to do to connect) since when you start the OpenVPN GUI is just puts itself down in the system tray and you have to find it down there and right click on it to connect or disconnect.
My question is: Is there a way to make the OpenVPN GUI connect as soon as you start it? So the users doesnt need to search for the GUI in the system tray?
Thanks for your time reading this post and I hope you will have a great day!
Best regards/
Peter
I hope everyone here is having a great day!
My boss gave me a mission to find a OpenVPN solution which is simple for the users when they are outside the office.
So this was my boss wishlist:
1. When a client connects to the OpenVPN server (which is on a windows server) the openvpn client should get an ip from the windows dhcp server and not from the openvpn server. (After hours and hours of testing I couldnt get this to work. So now the openvpn clients is running on a network range separated from the LAN users and I route the traffic between the OpenVPN clients and the network devices in the office LAN. If someone have the solution to this problem feel free to inform me about how to set this up)
2. When a client connects it should promt for UserID and Password, which should be checked against the Windows AD. (I havent checked how to do this, so right now he got certificates which has to be installed on every client that needs to have OpenVPN access.)
3. Find a more user friendly gui than the one you can find in OpenVPN.
Well this is where I am right now. I would like to use the OpenVPN client GUI but the users wouldnt understand how to connect(or they would get annoyed about how many steps they need to do to connect) since when you start the OpenVPN GUI is just puts itself down in the system tray and you have to find it down there and right click on it to connect or disconnect.
My question is: Is there a way to make the OpenVPN GUI connect as soon as you start it? So the users doesnt need to search for the GUI in the system tray?
Thanks for your time reading this post and I hope you will have a great day!
Best regards/
Peter