When I try to login to my hosts via a Windows 10 PC (with RU 184.108.40.206) an on-line host immediately goes off-line/unknown.
This should be temporary , only for a second or two when the Viewer tries to connect. If connection is successful, the connection thumbnail converts to the Logged on status. More about connection statuses.
As well I am usually repeatedly prompted for username and password despite entering them correctly.
If you repeatedly receive a password prompt this can mean either (or both) of the following:
- The typed in password is incorrect - The password is not set on the Host side
In either case you need to re-set your password. Right-click on the Host icon in the system tray, select Settings for Host, then Security. In the security dialog click Change password, enter a new password and confirm it and close the settings windows.
The black screen issue may be caused by different reasons by usually it's either "Host restart required" (after the installation, that is) or graphics card/drivers issue in which case the driver should be updated.
Is this OK; that is, is he telling me the correct ID?
Yes, the 12-digit IDs are now the current format. However, 9-digit IDs are also supported for backward compatibility. That is, you can still connect to older Host installations from newly updated Viewer.
Just realized that the "Check for Updates" button on my current version doesn't work! So manually downloaded and installed new version.
Automatic download of an update file was implemented only recently. That's why it's not available in version 6.3 and earlier.
P.S. We try to improve update-related features with each release. Now you can automatically update both Viewer and Hosts, meaning that you just need to click a button and the program will do the rest. This tutorial explains how, see "Updating Viewer Method 1" and "Updating Hosts Method 1".
Note that the word "automatic" here doesn't mean that the program updates on its own without the user's consent. It is the user who makes a decision and initiates the update process.
It is hard to figure out exactly what might be causing this behavior. I can only say that our team is going to revamp the code related to dragging and dropping and make it more robust and feature-rich.