OpenVPN Access Server Reviews

This was a test bed in which to use a virtualized Citrix server to be connected with the downtown Tacoma site. We needed that to be able to not only access the local network over there, but also to use thin clients there to virtualize the work stations on our test location.

It allows us to actually use the Citrix server, just that simple.

A valuable feature for us is its ability to see the new Citrix server as a local server within the company.

And it allows us to test abroad. We have a couple other sites that we want to try to get people to remote into. Having that feature really helped.

The user interface that we had to implement. I would like to see a simpler interface, so that we can make the connection between the local network using the LAN IP.

Also, I would be more happy with the idea of licensing to have a reduced price with longer, grouped, annual fees. We have a lot of other software that does the same thing. It's a little higher price if you're going with a shorter stint, but there's a reduction in price for three- and five-year contracts.

It's been more of a hardware issue with us. The VPN has been working fine, but on our side, where our test bed is, we've just been trying to get it fine-tuned. But, no, OpenVPN hasn't had any problems.

Not yet. 

It's been pretty good. We only had one question when we were first implementing it. My crew and I were answered very quickly. The technical support was responsive.

We didn't have a previous solution. We had done a little research and we went with OpenVPN as the first option. It wasn't that we went through several before it.

It was pretty straightforward. We've seen terrible things with Citrix, so nothing compared to that.

I would say the product's pricing is a good value. I would recommend to other companies to implement it. I've seen other software, in tandem with the service, to be very expensive.

We were attempting to do a closed VPN between the two sites, but it really doesn't work with the local IPs that we wanted people's Citrix agents to be able to get in. We wanted it to emulate the IP of it being local because eventually we were going to move the Citrix server to the Tacoma site.

Do your homework, and make sure that your test site where you're going to be setting this up has a good, solid connection with your ISP. That was the issue we ran into. We actually had to get our ISP out here to fix the modem that we were having issues with.

We use the solution to access FTP pages and file sharing.

The solution is reliable, easy to use, and open source. It's free at no cost.

I have been using OpenVPN Access Server as a user.

The product is stable. There are no interruptions, and it works smoothly.

The solution’s scalability is fine. It encompasses security advances and investments in the industry.

The solution is free. It is worth the money.

The tool works fine and doesn't bother me all day.

I recommend the solution.

Overall, I rate the solution a ten out of ten.

We are a solution provider and the OpenVPN Access Server was one of the products that we used for our customers. It is used to create remote desktop connections into the cloud network, where people who are working from home can share resources with people in the office. When people are working in an office then they have a local network, and OpenVPN expands the network for use externally.

We are no longer using this solution because of complaints raised by our customers about security vulnerabilities. The server is now shut down.

This server allows you to connect to a network that does not have any public IP addresses. You first dial-up the OpenVPN to get onto the network, then directly use the private IP for the local device. Once the connection is made, we can do development work, maintenance, or whatever is required.

The most valuable feature is the remote connection capability.

It is easy to use.

There is support for multi-factor authentication.

We would like to be able to access the parts of the network that belong to other virtual LANs, which is not currently possible. For example, if an organization has different VLANs for sales, developers, and production, then we can only connect and view one of these segments. If you can access sales then you will have visibility of that particular subnet and not be able to see the developer VLAN resources.

The security needs to be improved because it was a complaint that our customers had. I'm not sure exactly what the specific issue is, other than they told us that it was not compliant with their organizational policies.

It is not possible to scale this solution horizontally, which is something that should be improved. They could allow multiple instances to run in different zones, synchronizing with each using a round-robin scheduler.

It would be great if they added intrusion prevention and detection (IPS/IDS) features. If they had these then there would be less need to use other products, such as firewalls. It would allow everything to run under one umbrella with centralized control.

We were using OpenVPN for about one year and we migrated away from it about three months ago.

Horizontally, this solution is definitely not scalable. Vertically, it is possible but there will be some downtime. Scaling requires that we stop the server, upscale it, select a different instance, and then restart it. The downtime is approximately five minutes.

I have been in contact with technical support and the experience was good. They have knowledgeable people.

We have migrated to Fortinet because of security vulnerabilities.

The initial setup is easy. Once we go to the marketplace for the license, we can install and start using it. This involves selecting an image, then selecting a VM, and deploying on that. You then install the certificate and create the users. Creating users is also easy to do.

 One person is enough for this task and it will take between 15 and 30 minutes to deploy.

Our in-house team deploys OpenVPN for our customers. After the deployment is complete, users will log in, download their profile, and then they can connect.

Before migrating to Fortinet, we looked at other vendors including Cisco. We found that based on the sizing we needed, the pricing of Cisco AnyConnect was not as competitive.

Personally, I have not found any differences between these products that affect what I need to do.

Personally, I like this product and our decision to shut down the server is in response to decisions made by our customers. I have not found any issues with it, myself.

I would rate this solution a nine out of ten.

It allows us to give access to our office network in a safe and secure way to users, no matter which computing platform they use. 

1. Easy to set up.
2. Clients for multiple platforms
3. It runs on Linux.
4. It allows for two-factor authentication. 

This makes it very easy to administer if it is running on a Linux server where you can do everything over CLI or a web-based interface. Some software only has clients for MAC and Windows, which is annoying. Two-factor authentication allows us to not force frequent password changes.

There was one annoying feature where we had to disable and enable the user. I cannot remember what it was exactly, but I think it was for a password lockout. It would be nice if there was a checkbox, or something, in the web interface to allow you to unlock a user whose password was locked. 

No issues. It is solid as a rock.

Never.

I do not think we ever had to use technical support. I mainly found answers on the web forums.

No.

It was already set up when I got there. 

However, I have set up OpenVPN elsewhere. The initial setup is very straightforward as long as you understand something about the way the OS works, and how the networking and certificates work.

Not applicable.

It is good stuff.

We primarily use the solution for a secure VPN connection.

Overall, it's okay and performance-wise it's fine.

It is easy to set up.

The solution is stable.

It can scale well. 

It is open-source and free to use. 

The performance could be a bit better. The stability could always be enhanced. 

When there are too many concurrent users trying to connect at the same time, there may be a bit of a bottleneck. When all people would like to reconnect to the VPN at the same time, the performance and availability of the solution could be better.

I've been using the solution for almost a year.

The solution is quite stable and has okay performance. However, it could be better. We'd like the performance to be more robust.

It's a scalable product. If a company needs to expand it, it can do so. 

We have around 2,000 users on the solution right now. 

We're always open to increasing usage. 

I haven't dealt with technical support just yet. I can't speak to how helpful they would be. 

We did not previously use a different solution. 

With OpenVPN, the amount of people you need to deploy and maintain it depends on how many nodes you would need and the number of users as well as whether you are operating 24/7 or operating only during work hours. Likely, you would need between three and six people.

This is an open-source solution. We can use it for free. 

I'd recommend the solution to other users and organizations. 

I would rate the product eight out of ten as I have been mostly pleased with its capabilities. 

Our primary use case was to give mobile knowledge workers a secure connection across the Internet to our LAN, whether by laptop, mobile tablet or smart phone.

It allowed people to remotely access files from their mobile devices. It was so easy for end-users to use that they were able to work more efficiently no matter where they were, whether at a client’s campus, home, traveling – wherever they had a device and internet access.

This open-source solution provided the easiest UX for our end-users and had the greatest interoperability with all the operating systems we used, including but not limited to: iOS, Android, OS X, Windows, and Linux.

The upgrade path from older versions was more difficult than we wanted to tackle, so we ran an older version of the software for longer than I wanted. Patching, updating, and migrating to newer versions was a problem for us. That said, we were on a rather old version that I inherited yet it worked rock solid.

No issues.

We more than doubled our staff at my previous company and our OpenVPN appliance handled it well.

Tech support wasn’t needed during my 5 years administrating OpenVPN.

OpenVPN was already implemented when I took over the IT department. I do know that there was also a Cisco VPN product in place, but it was finicky and many of our end-users had issues with the Cisco VPN. At the time, it also didn’t work on mobile devices and the required ports were blocked by certain ISPs (like some hotel internet connections, cellular providers, etc.)

In-house expertise.

At one point I had to purchase addition connection licenses. I was very pleased with the pricing and licensing; so much easier than navigating the confusing jungle of Microsoft and Cisco licensing and pricing. That alone made the product a delight to manage.

I didn’t purchase OpenVPN, but I have evaluated other products for other departments I managed at other companies. Cisco and Fortinet are the two I remember off hand.

We did not use this product on AWS. We hosted the server on our network.

My advice would be, if OpenVPN fits your environment and needs, it’s a great solution. Do it.

The primary use case for me is to encrypt my traffic to the Internet and protect my privacy on my home network.

One of the valuable features of OpenVPN is that it is free. I have set the default routes to the VPN server so that all traffic is encrypted.

One area for improvement in OpenVPN is the ability to selectively terminate connections. If the program could list active connections and provide an option to delete or kill them, it would be a useful feature. This would save users the trouble of having to restart the entire program each time they need to terminate a connection.

I’ve been working with OpenVPN for two years now.

It is a stable product.

The initial setup is straightforward.

You do not need a professional team to deploy the solution. I did it myself and it took around half an hour.

You don’t need to buy anything to use OpenVPN. But if you want access to the enterprise version, you need to buy a license for that.

OpenVPN's usage depends on the network preferences and deployment complexity.

I would rate it a seven out of ten.

Interoffice connections. We had offices in India and the US. To connect both of them to the same environment, we were using OpenVPN for that. It was so we could maintain a file store, exchange files and documents securely through our own proprietary mechanism, instead of having to rely on Dropbox and the like. 

Interoperability between different offices. We didn't have to keep exchanging documents via email and other tech. We were able to maintain a common file store because of the complete VPN setup we had using OpenVPN.

The compatibility with almost any Linux operating system, and how easy it is to write scripts and generate keys for people to use and log in. I found it easy to deploy quickly.

Some of the issues we faced were things like, if someone's key is not working, or if we had to remove someone's permission from it, or maybe an employee left the company and we had to take their key out. That seemed a little bit more complicated than it had to be.

Also, I think right now the GUI part of it is locked out behind the pay wall. It could use something that gives it a very basic, minimal, graphic interface for logging in, for the community version. That would probably be a good step forward.

We did not encounter any stability issues in our scope.

Our use case was less complex than most. We did not come across any issues with scalability.

I usually found support online, so I didn't have to use tech support.

We started off with OpenVPN when we were evaluating what we could use for our needs and we ended up with OpenVPN. I have used other VPN solutions at other offices, but in the cases that I've dealt with, OpenVPN was the choice.

If we had to create something for someone who was not necessarily tech savvy, I had to set that up on their computer, I had to write "read me's" and other things so that they could install their client and then connect to the VPN by themselves. So it was hard to set up for people who are not tech savvy. I had to actively provide assistance and walk them through the whole process.

The product's pricing is good value, definitely. It is one of the best features, I would say.

Evaluate the product before seeing which type of licensing is good for you. I think there is a good evaluation method available for OpenVPN, so you can just evaluate if it meets your needs. Then go forward with the right licensing policy.

OpenVPN is a good option for kick-starting any kind of interoperability between offices. It doesn't have a huge setup time, so it's a quick way to start experimenting with how the organization would work with its VPN requirements. Even if your requirements are very small, it's a very convenient to start off with this solution.

I rate it at eight out of 10 because it gives value for what it provides. You need technical know-how to get started on it, but it is also very swift. It has all the right features but it's technically challenging if you're not tech savvy. Providing clients with keys is not that straightforward.