I've installed the latest version but it keeps reverting back to my old version when I launch the icon.

This happens because of a pesky Microsoft Installer bug.  To get around it, simply uninstall your old version and then run the setup for the new one.  Your settings and groups will remain in tact.

Why does my personal firewall say that VNCScan is accessing the Internet?

This is happening because the automatic update checking feature is turned on in the main preferences.  If you uncheck the box that is labeled as follows, the program will be quiet again:

Absolutely no information is sent to us during the update process.  It simply connects to the first available web server and asks for a tiny text file that tells VNCScan what the latest version is. 

I upgraded from version 2006.1.5 or earlier and now my groups are all gone!!

This happens because the location of VNCScan has changed from "c:\Program Files\TGCS" to "C:\Program Files\Bozteck".  

You can migrate your old groups and settings by doing the following:

1. Locate the folder named "C:\Program Files\tgcs\VNCScan Console .NET\backup" in Windows Explorer
    

2. Copy that folder to "C:\Program Files\Bozteck\VNCScan Console .NET\" and overwrite the existing Backup folder if it exists.
    

3. Run VNCScan and select the Backup/Restore tool from the main File menu
    

4. Restore from a backup dated before you installed the latest VNCScan
    

5. Close out of VNCScan and then open it again

I scan a range of computers but not all of my computers show up. What gives?

Check the timeout and thread settings in the group properties. If your threads are high, then you may need to increase the timeout so that your computer isn't overwhelmed with connection requests and has time to answer them all.

Another possibility is that you need to apply the XP service pack 2 fix found on the download page.

I've applied the XP SP2 patch and I still get a message that I need to apply it after doing a scan.

There are a couple of things that can cause this to happen.  First, try clearing your system event logs and then doing another scan.  VNCScan monitors for a certain event log entry to detect the requirement of the patch and it's not always as expected even after a reboot.

The other thing to try is to re-apply the patch but choose a much larger number for the allowed socket connections.  Try giving it a high number like 10000.

When I connect to a computer, a window says that it's retrying a bunch of times then fails.

The windows that says that is launching because you have the checkbox in the global VNCScan properties set to check status before connecting.  The purpose of this is to allow retries but it is disabled by default because it causes problems in some situations ... perhaps like yours. :)

Try unchecking that box and then connecting again.

When I try to connect, I get an error that said it could not get the address.

This may be happening because the name resolution isn't operating properly.  You can tell VNCScan to use the IP address instead of the registered hostname when connecting to computers.

There is a three level approach to this setting.  You can either apply it in the global properties, group properties, or the computer properties depending on the scope that you would like it to apply.

I get an "access denied" and an "object required" error at the end of my VNC deployment.

Try downloading psexec.zip from here and unzipping a copy of it into both c:\fastpush\vnc7\utils and into the same folder as your vncscan.exe.

This gets around some pesky WMI permission issues in Windows XP.

I have different versions of VNC on my network and I get an “Invalid Protocol” error when connecting.

Make sure that the server on the other end is running the same version of VNC as the viewer that you are attempting to use.  You can set the VNC viewer at the global options, group properties, or the computer properties.  The scope of the setting depends on where you set it.

I use UltraVNC on my network and I get an error about a missing DSM plug-in when connecting.

The most common cause for this is conflicting settings in the group and computer properties.  The DSM plug-in is a part of the UltraVNC deployment that enables encrypted VNC sessions. 

If UltraVNC was deployed on the remote computer and encryption is configured for it, the server will expect you to have a matching key file and be configured to use the same DSM plug-in at the viewer end. 

Things to check:

1. Make sure that you the proper .DSM and .KEY files are located in the same folder as the vncviewer.exe that VNCScan is using
    

2. Make sure that the remote server is running UltraVNC with encryption properly configured if you have the computer properties set to connect using encryption
    

3. Try re-deploying UltraVNC to the remote computer.  VNCScan automatically ensures that the computer properties match the manner that you deployed VNC in.

How can I update my VNC push installs before VNC Scan includes them into the latest build?

The binary files for each supported distribution are located in c:\fastpush\vnc7.  Each folder under there represents a distribution of VNC. 

Simply download the latest binaries from the owners of each distribution and replace the files in the respective folders.

Why do I need psexec to push VNC to remote computers in some situations but not in others?

Take a look at this post for some insight on this.  Apparently, there have been some changes in WMI with XP SP2 where remote calls like this operate under the guest account.  PSEXEC gets around this by remotely installing the psexec service and running the commands under the context of the administrator account that you supply.

Can I share my VNC Scan data between all of our administrators?

Click on the main Tools menu, then Global Options.  Check the Support Files tab for the portions of VNCScan that are movable to alternate locations.  Moving the groups.xml also moves all of the other support XML files that are involved.

What do I need to back up in order to restore gracefully from a total hard drive crash?

The version of VNCScan currently versioned 2005.11.26 beta has backup built into it.  You can manually start a backup by clicking the main File menu and choosing to initiate a manual backup point.

You can set the number of automatic backups to store before overwriting.  This setting is in the main global settings. 

The backups are stored in a subfolder of the VNCScan program folder named "backups".

Why doesn't VNCScan have an integrated VNC viewer?

The main reason for this is out of respect for the open source VNC developers and to remain in compliance with the GNU Public License under which the VNC source code is covered.

We recognize that other VNC based products have modified the open source VNC viewer, renamed it as their own brand, and have openly refused to freely give back their modified source code. 

We want to be absolutely sure that we are set apart from this practice and would like to appeal to the conscience of those companies who use VNC source code in their applications without complying with the GPL.  It's not fair to the community and highly unethical.

The other reason for using the standard VNC viewers is because we recognize that we would be reinventing the wheel so to speak every time that there was a new release of VNC for each supported flavor. We would much rather put that programming power into new innovations.