Why VPNs Stink

Why is it that we all tend to put up with things even though they are a pain in the neck and waste our time? It is usually because we don’t know that there is a better way. Once we discover the better way, we usually shake our heads and wish we had know about it sooner. We would have saved so much time and trouble.

Well, VPNs fit into the “pain-in-the-neck” category. We keep using them even though they are very frustrating to use and waste our time. Here are 3 of the top reasons VPNs stink:

1. They are time consuming. There is nothing automatic about a VPN. Each new user or each new system you need to connect to requires you to go through a setup process. This can takes hours. Simple and fast VPNs are not.

2. They don’t scale. VPNs were really designed as a corporate access solution for employees needing access to a single location. As soon as you have to access multiple locations, the VPN becomes very cumbersome. The need to access multiple locations is common for systems integrators, VARs, and consultants. Maintaining these multiple VPN connections is difficult and time consuming. I know of an organization that has hired a full-time person just to manage their VPN connections to their 50+ customers!

3. They are a security risk. The dirty little secret about VPNs is that they pose a significant security risk. When you connect your computer to a remote network (or someone connects to your network) you bring with you all your files–good and bad. You could readily introduce a virus onto the remote network and all the computers connected to it. Further, unless the remote network has very strong security policies in place, VPNs allow access to any of the other computers and devices on the network.

iTivity is the better way

VPNs provide inbound connections to remote systems. iTivity allows you to eliminate the use of VPNs, and all its associated problems, by providing outbound connections from remote systems. Check out iTivity and you’ll discover the better way to support remote systems.

(c) 2011 Tridia Corporation

www.tridia.com

iTivity 5.4.04 Build #1

[WIN 32] iTivity Attended iAgent 5.4.04

_____________________________________

1- The iTivity Attened iAgent has been updated to allow the [View] remote control connection to continuing operating during the UAC confirmation dialog on Windows 7, 2008 Server and Vista.

[WIN 32]              iTivity iServer 5.4.04

[WIN 32]              iTivity iAgents 5.4.04

[LINUX INTEL] iTivity iServer 5.4.04

_____________________________________

1- The iTivity iAgents, iManager and iServer now use the OpenSSL release 1.0.0c from 02 December 2010. This update contains several bug fixes, including one to insure the stability of the TLS server (iServer).

Encryption Certificate Error in iTivity iAgent after Installation

Encryption Certificate Error in iTivity iAgent after Installation (UPDATED 09/08/10)

Tridia is currently working on correcting a problem with the generation of self-signed encryption certificates. This problem impacts the deployment and installation of the iTivity iAgent on new systems. Already deployed iTivity iAgents are not impacted by this problem.

Here are complete details: https://support.tridia.com/faq/showfaq.php?faq_id=289

Tridia Releases iTivity 5.4.01

Tridia is pleased to announce the release of iTivity 5.4.01.

iTivity 5.4.01 includes these improvements:

• FTP support for all versions of iTivity prior to 5.1.00
• Agent name appears in the viewer window.
• iManager displays the iAgent support domain.
• Ability to configure items displayed in the iManager on the left hand panel.
• Support for outbound connections across HTTP proxy servers.
• Various bug fixes and corrections.

A complete description of all the improvements in included in the releases notes.

Users who are using Release 5.4.00, or are under the Maintenance Agreement Plan (MAP), are entitled to a free upgrade.

www.tridia.com