Conrad Sallian's community posts

Hi Paul,

So far the only idea that comes to mind is that either your new ISP and/or your router somehow blocks either the outbound ports used by our Internet-ID connection or public server destination addresses.

The outbound ports used by Internet-ID connection are 5655 and 443 https://www.remoteutilities.com/support/docs/ports-used-by-remote-utilities/#Public_server .

Hello Aaron,

Could you please check if you have either "Auto" or "Custom server security" (in fact I recommend you try both as part of the testing/troubleshooting process) value in the field below in connection properties for the Host in question:



Looking forward to your reply.

Hello Bart,

Thank you for the contribution. We, in turn, will consider adding the functionality into Remote Utilities in the future.

Hello Paul,

Thank you for your message.

Am I right assuming that the issue is on the Viewer side? I.e. you changed ISP on the side where the Viewer is and your remote Hosts are not visible anymore?

Before looking further into the problem could you please flush your DNS cache on the Viewer computer just in case. You can use this command:

ipconfig /flushdns

in the command line interface.

Hello Drideanu,

Thank you for your message.

Also I read on the forum that the I can't add multiple starter licences to one viewer.

Actually, you can. However, this won't increase the number of remote computers you can control. In order to be able to control more machines you need to change the license type. For example, in order to control 20-50 machines your license type should be Mini, not Starter.  

So if you are the only admin working the software at a time and you have more than 20 and less than 50 computers to control then you need a 1-tech Mini license. You can get a quotation from us using this form https://www.remoteutilities.com/buy/request-quote.php

Hope that helps.

Hello Rob,

The Internet-ID settings (including the server details) are located on each Host machine. It is possible to update them without actually re-installing the Host. However, this will need to be done one-by-one for each Host (e.g. using the remote settings).

Alternatively, you can use the re-installation method - you don't necessarily have to have GPO environment for that. You can use the Remote Install tool and update the Host using that tool.  Here is the process:

1. Build your custom Host installer ("Standard" option, i.e. an .msi file) with which to update your remote Hosts. Make sure that you specify your server details during configuration. To avoid changing your existing internet-ID codes your configuration window in Step 3 should look like this:



2. Use the Remote Install tool to "push" the Host update file to your existing Hosts and replace them. You must have connectivity with your remote Hosts. Your Remote Install window should look like this:



In the "Specify Host msi package" specify the path to your newly configured msi package. Then click "Process action".

Note, that you can also select multiple Hosts to be updated. However, I highly recommend that you first try this procedure with one non-critical Host to make sure that you use correct settings. Even after that I suggest you only update your Hosts in small groups, preferably no more than 10 hosts in a group.

3. Update your Viewer connection properties accordingly for each Host. You'll need to change the Internet-ID server details from "default" to your server details. Again, you can multiple-select connections in your address book and update server details for all of them.

Hope that helps.

Hello Jeff,

We apologize for that overreaction. Of course you can post links to Microsoft documentation, as well as to any other non-competing tools.

Thank you for helping other users here in the community.

Hello Matti,

Thank you for your message.

No, there is no limit. The 1000 hosts limit that you mention is currently only an interface limitation which will be fixed soon.

Let me know if you have other questions.

Hello David,

We do our best to release an updated mobile client as soon as possible and the work is now in progress.

Hello Ian,

In connection properties please try switching to Unicode input and let us know if it solves the problem.



Thanks.