

We’re glad to hear you found VNC Connect easy to use, manage and deploy. Review collected by and hosted on G2.com. For this reason, VNC-based solutions should only be done within secure environments, and NOT "to access secure environments remotely". Any direct access solution brings the risk of whatever is on your remote computer into the environment, and that comes with a risk of cross-contamination.

All VNC serves a purpose, but I never like seeing that purpose being for remote access. It's just a lot of work to get to what other solutions provide natively.

Direct access solutions work if you deploy another product on top of that for privacy, plus dedicated jump servers, isolate them. This means if you want to compare it in the same realm as some of the other remote access solutions, then you need to be fair to where it falls short. Why? Because this solution is a direct access solution. If you'd like to use this securely then you should have an expert on hand (not your neighbor's kid, but an expert in security and cryptography). VNC Connect advertizes strong security, but what do they mean when they say that? They mean they have options for strong encryption and authorization but don't do that by default.
