Conrad Sallian's community posts

Hi Salam,

Is the computer on the same LAN/VPN as the Viewer? Perhaps you could simply utilize direct connection instead of trying to make ID work.

I'm still thinking that something's hindering ID connection on that specific PC. There's no other explanation, off the top of my head at least  :)

By the way, make sure that "default" internet ID server checkbox is selected in Settings for Host -> Internet ID connection Settings -> Advanced -> "Select Internet ID server" dialog.

Salam ELIAS wrote:
Conrad, I am not sure what is needed to be done as I have no active firwall, it is disabled on all levels.

In the KB it is indicated to open specific ports, so as far as win firewal is disabled, what should i do?

Thanks

It's not necessarily the firewall right on the PC itself. You said that it was a VM. The hypervisor machine for the VM can work as a router/NAT or as a bridge, depending on how you configure it. You need to check the settings on it, namely whether it allows the guest machine to send packets to and fro using the ports the RU Host needs for Internet ID connection.  

So it's certainly a network issue, but not necessarily on the VM machine itself. Check the hypervisor and your network router too, perhaps you have some firewall rules enabled on them.

Hello,

Thank you! We received this suggestion previously. It's on our wishlist.

Hello Salam,

The grey circle can only mean that the Internet ID packets cannot go through some obstacle. Something is definitely getting in the way of Host trying to establish remote connection with our server.

See what ports must be open for ID connection.

Hi Larry,

Thanks for the info. We'll be testing it then and see if we can reproduce the issue in our laboratory.

Hi Jean-Marc,

I solved the problem with Avira another way this time (which doesn't solve the original problem with Avira and RUT Viewer 5.6.0.6). I simply installed version 6.0 and that solved the problem with Avira false positive. Maybe version 6 has the 'trojan' more hidden and Avira doesn't recognizes it anymore. I wish they'll keep it that way.

Yes, we are getting better at hiding trojans, no doubt  :D  [sarcasm] Seriously, I think Avira have just reconsidered the detection and updated its signature databases.

A small translation correction in Viewer 6.0: under 'File --> Options', the Dutch version says "Other" on the tab next to "Sneltoetsen", but that should be "Overig". It simply isn't translated into Dutch. I assume that has slipped through while translating and it's not a critical update worth. Somewhere in a next version, priority somewhere-at-the-bottom-of-the-list is OK for this.

Thanks for the info. Actually, the localized interface files are not yet fully updated. Usually, the English version is our first priority and within a month since a big release we also update everything else including the translations.

Hello Larry,

Thank you for your report. Couple of questions.

1. What is the operating system on the local and remote end?

2. What is the version of Remote Utilities used? The latest one as of this writing is 6.0.0.4. Both Viewer and Host should be the latest version installed.

3. Do other keys work?

Thanks.

Hi Mike,

-If we upgrade our 2 viewer installations to version 6, can we still connect to all our existing v5 hosts while they have not been upgraded yet?

Yes, you can. Newer Viewers can connect to older Hosts. So our recommendation is that you first upgrade the Viewer and from within the Viewer - remotely update the Hosts.

-Are there any issues migrating v5 to v6 hosts AND changing to our own GMS? Can we do this all at once or better in stages?

For the program, there's no difference whatsoever what ID server you use. It's just a matter of updating ID settings on the Host and in Connection Properties on the Viewer.

But there is a caveat. The ID and the ID server are two settings that are closely interconnected. You cannot configure the MSI installer so that it changes one of them (ID server in this case) and leaves the other one (ID) intact. In other words, if you update your ID server address on all your remote Hosts you will have to also re-generate IDs and update your address book.

You can do in reverse though. That is:

1. Change the ID server manually on the Hosts that you want to communicate via your GMS. You can do so remotely using the Remote Settings command in the context menu in Viewer when you right-click on a remote connection. New changes will apply only after you restart the Host, see the next step.

2. Upgrade the remote Hosts using the vanilla installer and Remote Install tool. Don't build any MSI package.

3. Once the upgrade is over and the remote Host will restart it  will be available via your GMS rather than via our default server.

Try this with one of the Hosts first. The downside of this strategy is that you'll have to manually change the ID server for each Host, because so far you can't change Host settings en masse other than using an MSI file. And using a custom built MSI file might not work in this case because if you change your ID server your ID (code) will reset too.

-Bring up our new local GMS
-Install v6 viewers to replace existing v5 viewers
-Build our new MSI installer and Agent (that points to our GMS)
-Upgrade hosts via v6 viewer

Good plan. Only back up your address book using the Export Connections feature. You don't want to lose your address book if something goes wrong. And also, see my previous paragraph since the order in which you perform these actions might be different. Again - you can't change the ID server without changing also the ID itself. So you need to think beforehand, how you are going to connect to those computers after you make changes/upgrade.

If you have any questions, I'm here.

Hello Salam,

Thank you for your message.

Always offline in internet id mode. is RU free version for 10 is compatible with Windows 2012

Yes, there is no difference between free and paid license in terms of program features and compatibility.

Are both Viewer machine and Host (Win2012 machine) located on the same LAN? When you use an ID connection but there is direct accessibility of the Host, the program will use direct connection even if you choose ID connection. For direct connection you need to have incoming port 5650 open on the remote Host. Please, check if that port is open on your Win2012 Host.

To add security, you can change the default port to something else. See Settings for Host -> Options -> Network.

I also recommend you taking a look at this KB article.

Hope that helps.

Hello Carlo,

Our security system and RDP security system are two different independent things. What you are trying to do is impossible with Remote Utilities.

As for saving Windows password for the remote PC in Remote Utilities - we do have such wish on our wish list and perhaps will implement it in one of the future versions.