Conrad Sallian's community posts

The hosts and Relay server are all located internally.

It looks like your Hosts cannot connect to your server. In order to verify that, you can check the Host logs located in C:\Program Files\Remote Utilities - Host\Logs\.

I assume that the reason why your Hosts cannot connect is perhaps that you use the external IP address of your server in the Host's Internet-ID connection settings. Try using the internal/local server address so long as the server is accessible to your Hosts via LAN.

Hi Lars,

I guess that your Viewers and Hosts are located outside of the network where your server is. That is, Viewers and Hosts communicate with the server over the Internet?

Or is it so that either Viewers or Hosts reside in the same network as the server?

Hello Lars,

Thank you for your message.

And we have checked that the port is responding.

You performed the check as described  here and received "Success", correct?

Hello,

Thank you for your post.

Is there a way to assign a static local port for a connection?

No, you cannot specify a static port, it should be dynamically assigned.

My hope was to be able to save a Windows RDC session with saved settings and launch it from an RDC shortcut on the desktop after Viewer is launched.

Create an RU connection, right click on it and select Properties. Navigate to the RDP section.

Click Configure, set your options and click Save. Close the properties window. Now you can right click on the connection and select Create shortcut on the desktop. You will be able to create a shortcut for a specific connection and specific connection mode (in this case RDP).

Hope that helps.

Hello Rogier,

First I thought it was a connection problem or some program freeze... And therefor I was restarting my client all the time.

The session should unpause when you bring forward the Full Control window? Does it stay paused in your case?

Can you make this feature optional?

That might be possible, but provided that it should pause/unpause automatically, it doesn't make much sense. By the way, the reason behind pausing a session when its window is minimized is to save traffic/bandwidth, which for some users may be an important factor.

Hello John,

Will you add some kind of server side manual validation for hosts or viewer to prevent unauthorized use or some other kind of mechanism ?

We'll see if we can implement something more automatic, so to say.

Thanks!

Hello  John,

Thank you for your post.

Currently, yes, it is possible, although it cannot lead to any breach of the server or other harm. Besides, the probability that someone knows exactly at which IP address (or DNS name) and port your server service is running is very low.

However, in the near future we will implement features that will prevent such unauthorized use of the relay function. As for the nearest server update, we will add the ability to specify different communication ports for Viewers and Hosts that they use to talk to the server.

Don't hesitate to ask me if you have other questions.

Hello Rogier,

Yes, the Viewer pauses the connection if you minimize the Full Control window. This is normal behavior.

However, there shouldn't be any messages like "Current session on hold". Are you sure you are using Remote Utilities' own Full Control mode, and not the RDP mode?

Sorry, I managed to view the image now.  So you mean the Pause function, correct? Did you mean that RU entered the paused state on its own, or did you just click the Pause menu item yourself?

I'm just trying to figure out the issue at hand. Thanks.

The image won't load. Could you please upload it elsewhere or just send it as attachment to support@remote-utilities.com?

Thank you!