Remote Access applications and appliances.
Remote Access to some is a business requirement while others use remote access to view movies from their DVR.
We all like the idea we can access our personal and business files and folders from any Internet connection. It's what makes us "Look Good" when you can pull up or login to your computer remotely.
We have used many methods of connecting two computers over a WAN (Wide Area Network which some say Internet.)
The key to working remotely is to know how things work. If you run software to connect to your remote computer and your remote computer is running the same software you should know how the connections are established.
For the casual computer user you may never really need to know but it's always a good idea to know then "Who", "How", "Why", and for "What Purpose".
The "Who" in remote connections is; Who is connecting via my remote applications or hardware.
The "How" in remote connections is; How is the connection established, IP, DNS, PORT, Etc.
The "Why" in remote connections is; Why does it do it. (This is going to be technical in part)
The What Purpose is the question you will be asking when you see some of our test results. What purpose does it have connection to 5 servers in 3 countries when I'm in the same room connecting over the internet to the other computer.
READ: What we hope to accomplish here.
The Article List is at the bottom of this page.
What we or should I say "I" want to accomplish in our remote access applications section is not recommend one method over another but rather offer you some insight to and what to know about remote desktop connections, remote control and remote technical support applications.
There are many things that can be fixed or repaired remotely. Settings can be adjusted and policies created. I personally save hours each week working remotely on client systems. But can everything be done remotely? No and you should be aware of what you should not expect from remote desktop services.
Administrator login vs. User login.
When testing a remote application make sure your first tests are not as a local administrator on the computer you are using or connecting to. This will in most cases let you know quickly if registry modifications, firewall adjustments or any number of things are changing that require administrative permissions.
I've always asked users to not work from an administrators login profile. I find it is better to modify local security policies and folder access to run applications than it is to allow full admin rights to any desktop. In the long run if you can not change or modify then when things are working you can't really break them. Sound simple enough?
Just Say No to Remote Techs, for now that is...
A growing part of the industry is Remote Technical support. I have to confess it's easier for me to service 4 systems remotely than it is to drive the distance and walk from room to room. I've had day's that I had to change the backgrounds of the remote computers so I can tell which one I was working. Connecting and working on 4 or more computers at the same time is a great time saver but can become confusing when connection names are similar.
As a technician I run into software applications that are very proprietary. Many times I have to call the technical support line of the software. These are sometimes great experiences and other times nightmares.
Look below for links to articles and reviews we have made. All tests are our personal setups and most times we don't detail how we do our tests but we will detail our results. (Have to keep some technical tricks in our black box.)
Learn and share your experiences with remote access applications. We offer comments that can be changed into topics. If you're good maybe we'll even post one of your articles. But it has to be geared to helping computer users as well as technicians.
We also work with technicians around the US from time to time when reviewing products and applications. So if you know what PF2.exe is, GFI is on your thumb drive and you have control of you local network you might have fun testing with us. We do have a few requirements which when the time comes we will tell you about.
If you are here for the TeamViewer Article we have updated the article to include specifics of how we tested the remote desktop version 4. For those that posted "Did you contact them?" The answer is and was "Yes". But it's not our job to follow-up on emails to tech support it's out job to protect our clients and test software before installing it.