Pauline's community posts

Hello Gaz,

Thank you for your message.

Please try enabling the Use legacy capture mode feature in the Host Settings -> Other tab and .
Please make sure to restart Host after enabling the feature in order to apply the changes.

In addition, please also try enabling the Capture alpha-blending windows feature in the Connection Properties -> Additional properties tab and see if this helps to resolve the issue.

Hope that helps.

Hello Carl,

Thank you for your message.

PLease note that it's expected behavior for both RU Server and Viewer not to fully exit when clicking the "X" button - in order to fully close the program and stop its respective processes, you need to close it via the File -> Exit menu command.

As for the administration program that can't be launched while RU Server is running - could you please specify the exact program? Do you mean Windows PowerShell, Remote Server Administration Tools or something else?

Looking forward to your reply.

Hello Jeff,

Yes, you need to have port 443, 5655 or any other custom port opened and not used by another software on your RU Server machine. For more information please also see this page.

Hope that helps.

Hello Jeff,

I have read both articles that you linked to and it appears to me that that type of IP filtering is referring to the IP addresses of viewers, hosts and agents that connect to the RU server. Is my assumption correct?

Not exactly - please note that you can set the IP filter to listen to a range of IP addresses, not only one specific Host/Viewer at a certain IP address. However, you can set the filter to a specific IP address as well - it doesn't have to be an IP of a specific Host machine, just that the Server would be restricted to this address and a Host with another IP address wouldn't be able to connect.
Please also note that you can set up both global IP filters that would apply to all Server's communication as well as individual IP filters for each port used by your custom RU Server. For example, you can achieve the initial scenario that you've described by setting up your RU Server communication port to 443 and then add your preferred single IP address to a white list in a Global IP filter - this way your RU Server won't allow Viewers or Hosts to connect from other IP addresses.

Hope that helps.

Hello Mark,

Thank you for your message.

We apologize once again for keeping everyone waiting for so long. We'll do our best to release an update with implemented improvements as soon as we can.

Please let us know if you have other questions.

Hello Jeff,

Thank you for your message.

The port-level IP filter is a new feature that was introduced in Remote Utilities starting version 7. It allows you to assign individual IP filters for each port and also assign different roles for each port, i.e. you can set up different ports on your RU Server for the address book sync, authentication and even assign different ports for Viewers and Hosts connecting to your Server.

I want the RU server to listen on port 443 but I want to bind the RU server to a single IP address. I do not want RU server listening on all IP addresses, on the Windows server. Can this be done? I have other services that listen on port 443, on specific IP's.

Yes, you can set up your RU Server to listen on a preferred port to a single IP address or even a range of addresses. For more information please see this blog post that introduces the feature in details. In addition, this guide on setting up IP filters might also be useful.

Hope that helps.

Hello John,

Thank you for your message.

Unfortunately, we couldn't reproduce the issue in our environment. Could you please try updating your Host and Viewer to the latest version 7.1.5.0 and see if the issue still persists when using the latest version? Please make sure to update both Host and Viewer to the same version in order to avoid version mismatch that can lead to performance issues or some features not working/not working as expected. You can update your Viewer and Host via the Simple Update feature.
In addition, please make sure that you click the Apply button in the connection properties window after changing the cursor shape to a point in order to submit the changes.

Please let us know if you have more questions.

Hello Nijel,

Thank you for the provided feedback! We're happy to hear that the latest beta works well for you!

As for the address book related issue - it was already fixed in the latest beta version update. Please let us know if the issue persists.

Please let us know if you have more questions or need our assistance.

Hello John,

Thank you for your message and provided feedback.

We'll see what can be done about this issue in our future updates. Meanwhile, please try switching your Viewer to the View Only connection mode - this will ensure that the cursor is not moving on the Viewer's side when you need to work at the Host's machine.
You can quickly switch to the View Only mode directly within the remote session window using the corresponding icon on the Toolbar as described here or use the Alt + F12 keyboard shortcut to switch between modes.

Hope that helps.

Hello,

Thank you for your message.

Please try checking Viewer log files to see if they contain the Host information in the preferred format. The Viewer logs are stored locally on your Viewer machine and contains connection events. Here's how you can enable the logging feature in your Viewer.
Alternatively, Host log files contain IP addresses and Internet-ID codes as well. Host logging is enabled by default and the log files are stored on the Host machine.

Please let us know if you have more questions.