Community
WIndows Version: All computers showing OFFLINE however are all still accessible.
Links used in this discussion
Links used in this discussion
- https://www.remoteutilities.com/download/viewer/
- https://www.remoteutilities.com/download/
- https://www.remoteutilities.com/product/release-notes.php
- https://www.remoteutilities.com/support/docs/setting-up-relay-server/
- https://docs.microsoft.com/en-us/windows/win32/winsock/windows-sockets-error-codes-2?redirectedfrom=MSDN
- https://www.remoteutilities.com/download/beta.php
Conrad,
Support (Posts: 3061)
Mar 28, 2017 12:53:33 pm EDT
Hi Martin,
Thank you!
Thank you!
John Wilson,
User (Posts: 7)
Mar 28, 2017 1:36:43 pm EDT
Support level: Free or trial
No go. I uninstalled 6.6.02. Installed 6.6.03 from the .zip file. (I did this twice just to make sure). Erased the config file. But, when I try to "Sign in", I get the same RSA error as before:
Error report - Remote Utilities Viewer
---
Class: Exception
Text: RSA decoding error: Invalid block type.
Version: 66003 (0)
Id: {3C78FA58-EDD1-438E-A882-19E6FAF9E307}
Date: 28-03-2017 13-30-53
---
Public server connections are working fine. Also, FYI, my remote server setup was gone from the viewer and I had to re-add it the the system. I assume that was because I had to delete the config file?
I have not had a chance to upgrade the server to 6.6.03, I'll do that later today.
John
Error report - Remote Utilities Viewer
---
Class: Exception
Text: RSA decoding error: Invalid block type.
Version: 66003 (0)
Id: {3C78FA58-EDD1-438E-A882-19E6FAF9E307}
Date: 28-03-2017 13-30-53
---
Public server connections are working fine. Also, FYI, my remote server setup was gone from the viewer and I had to re-add it the the system. I assume that was because I had to delete the config file?
I have not had a chance to upgrade the server to 6.6.03, I'll do that later today.
John
Conrad,
Support (Posts: 3061)
Mar 28, 2017 1:42:28 pm EDT
Hello John,
You should update the server to 2.6 then. Its installer is in the same zip file.
Thanks!
You should update the server to 2.6 then. Its installer is in the same zip file.
Thanks!
Larry Glusman,
User (Posts: 7)
Mar 28, 2017 2:00:23 pm EDT
Support level: Pro
The new version fixed the offline issue for me, but any newly created remote machines with a new Inernet ID, which is now 12 digits, will not work. All my older 9 digit machines are fine.
Conrad,
Support (Posts: 3061)
Mar 28, 2017 2:02:50 pm EDT
Hello Larry,
Do you use our public server or a self-hosted one. If the latter, please update the server too.
Do you use our public server or a self-hosted one. If the latter, please update the server too.
Larry Glusman,
User (Posts: 7)
Mar 28, 2017 2:04:07 pm EDT
Support level: Pro
I am using your public server.Conrad wrote:
Hello Larry,
Do you use our public server or a self-hosted one. If the latter, please update the server too.
Conrad,
Support (Posts: 3061)
Mar 28, 2017 2:18:58 pm EDT
Larry, we have just tested with a couple of different Hosts in different parts of the globe, no issues.
Did you update the Viewer too? Not just the Hosts.
Also, anyone else having issues connecting to new Hosts with the 12-digit ID? Please report .
Thanks.
Did you update the Viewer too? Not just the Hosts.
Also, anyone else having issues connecting to new Hosts with the 12-digit ID? Please report .
Thanks.
Larry Glusman,
User (Posts: 7)
Mar 28, 2017 2:21:49 pm EDT
Support level: Pro
I updated the viewer, not the hosts. I will update a host and see what happens.
Larry Glusman,
User (Posts: 7)
Mar 28, 2017 2:28:30 pm EDT
Support level: Pro
That worked. I will need to update the host on any machine with the new 12 digit ID. The machines with the 9 digit ID are working fine with the older version.
Thanks!
Thanks!
Conrad,
Support (Posts: 3061)
Mar 28, 2017 2:39:00 pm EDT
Hello Larry,
Yes, there is backward compatibility. That is, if you just update a Host and don't erase/touch its settings - it will retain the old ID. The old ID will still work indefinitely so you don' t have to change it. But if you change it, the new ID will be 12-digit and you'll also have to update the corresponding record in your Viewer address book (otherwise you will be connecting by the old ID code).
To sum it up, you can simply update your remote Hosts when you have time to do so - either manually or remotely through the Viewer and don't bother with the IDs at all. Performance-wise there is no difference if a given Host has an old or new-format ID code so long as the Host itself is updated to the latest version.
Hope that helps.
Yes, there is backward compatibility. That is, if you just update a Host and don't erase/touch its settings - it will retain the old ID. The old ID will still work indefinitely so you don' t have to change it. But if you change it, the new ID will be 12-digit and you'll also have to update the corresponding record in your Viewer address book (otherwise you will be connecting by the old ID code).
To sum it up, you can simply update your remote Hosts when you have time to do so - either manually or remotely through the Viewer and don't bother with the IDs at all. Performance-wise there is no difference if a given Host has an old or new-format ID code so long as the Host itself is updated to the latest version.
Hope that helps.
* Website time zone: America/New_York (UTC -5)