Pauline's community posts

Hello Graham,

Thank you for the clarification.

It looks like the ISP of the network where the Hosts are located can be blocking access to our servers by mistake. Could you please double-check if you're able to ping id.remoteutilities.com? In addition, please try moving the Host that can't connect to our servers from its current network to another network (for example, you can even try mobile internet) and see if the Host can connect to our servers this way.
Last but not least, please feel free to send us the Host logs for examination. You can send them to support@remoteutilities.com, so that we can check if they contain any error entries that can point us to what's causing the issue.

Looking forward to your reply.

Hello George,

Thank you for your message.

Please note that Direct connection does not use relay servers as it's used when the remote Host is directly accessible for Viewer. Do you, perhaps, mean the Internet-ID connection in this case?

Is this some kind of policy change on your behalf or is there a technical problem stopping me fr om accessing your servers?

We haven't implemented any restricting policies that could prevent our users from accessing our Internet-ID servers, so this might be caused by some other factor. Perhaps, something is mistakenly blocking Remote Utilities or access to our servers — it might be caused by some antivirus or firewall software activity or even if your ISP is blocking access to our servers by mistake (hence why the servers are accessible for the remote Host in Greece).

Here's what we can do in order to resolve the issue:
1. First, please refer to this Internet-ID troubleshooting guide and see if the solutions listed there help to resolve the issue.
2. In case if the guide above doesn't help, please double-check the following:
- Make sure that required ports are opened on both sides of the connection.
- If you have any antivirus/firewall software installed on your machines, please check if it's not blocking Remote Utilities or access to our servers. If it does, then please try adding Remote Utilities to the exception list as described here as well as adding the DNS name id.remoteutilities.com to the exception list.
- Double-check if you have the same ISP for all the networks wh ere your Hosts cannot connect to our servers. If this applies, please refer to the ISP and ask them if they're blocking the access to our servers. You can also try switching one Host from such network to another network (for example, mobile internet) and see if the Host can connect to our servers this way.
- Last but not least, you can also try setting your DNS servers to Google Public DNS servers instead of your ISPs in your TCP/IP properties and see if this helps to resolve the issue.

Hope that helps.

Hello Graham,

Thank you for your message.

Could you please double-check if the Proxy settings on both sides of the connection are matching and set up correctly as described here? In addition, could you please clarify if both Host and Viewer are updated to the latest version 7.1.2.0 and if you have any other Host machines located in the same network that you cannot connect to as well?

Looking forward to your reply.

Hello Christopher,

Could this be a bug in that the message should only display when a remote connection is made? Are there some log files or something like that I can share with you?

Could you please send us the most recent Host log file and the screenshot of the connection warning being displayed when there's no remote session running? In addition, please let us know what are the OSs running on both sides of the connection. You can send all the information to support@remoteutilities.com - we will try to reproduce the issue to see if we can implement a fix for it.

Looking forward to your reply.

Hello Patrick,

In this case, could you please provide us the Host log file for examination? You can send it to support@remoteutilities.com.
In addition, please let us know what OS is running on both sides of the connection.

Looking forward to your reply.

Hello Nijel,

Thank you for the kind words and I'm glad to hear you've found a temporary workaround for the issue.

We'll let you know as soon as the update for Viewer for Linux with the implemented fix is available.

Hello Patrick,

Could you please try updating your Host to the latest version 7.1.2.0 as well and see if the issue persists? The latest version is available for download on this page or via the self-update feature. Updating Host to the latest version might help since version mismatch sometimes might lead to performance issues or some features not working.

Please let us know if the issue persists.

Hello Patrick,

Thank you for the clarification.

Could you please let us know what version of Remote Utilities is used on both sides of the connection?
In addition, please see this forum thread where one of our users has provided an extensive guide on how to remotely start a Host machine from a full shutdown via the WoL feature by sending magic packets.

Looking forward to your reply.

Hello David,

Thank you for your message.

Please try updating your Remote Utilities to the latest version 7.1.2.0 which is available for download on this page or via the Self-update feature. When updating please make sure that your Viewer and Host are updated to the same version as the version mismatch might lead to performance issues or some features not working.

In addition, please try enabling the Use legacy capture mode feature in the Host Settings -> Other tab and see if this helps to resolve the issue. After enabling the feature please make sure to restart Host in order for the changes to be applied.

Hope that helps.

Hello Nijel,

Thank you for your patience.

I've checked on the issue with our developers and this is a known issue that will be fixed in the next update for Viewer for Mac/Linux systems. Sorry for the inconvenience.

Please let us know if you have more questions.