Linked by David Bogen on Mon 26th Jan 2004 04:47 UTC
For many systems administrators, choosing and managing a VPN system is often quite a headache. Inflexible clients, servers, and protocols often prevent VPN's from being smoothly integrated into an already functioning network. The fact that many VPN clients are installed on users' home computers, well out of the reach of the systems administration team, often means that troubleshooting and upgrading VPN systems is time consuming and a struggle for both admins and users.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
I don't see any reason why anyone should bother with OpenVPN. For permanent connections or certificate based solutions, IPSEC is the way to go.
Have you tried to deal with IPSec through NAT? It's doable, but if you're a small company that cannot buy a commercial IPSec solution (one that comes with Windows clients that can tunnel IPSec through UDP), it won't work.
I played with FreeS/WAN and Win2K IPSec and it's a nightmare if you must open a VPN link through NAT (you must be able to do that if you want to give your road warriors enough flexibility).
OpenVPN deals with that issue gracefully.
I know the issue is not the protocol itself, but a lack of a free Win2K client that can tunnel IPSec through NAT, but whatever the cause, if it doesn't work, then you must search for something else.