Conrad Sallian's community posts

Hello Brian,

Thank you for your message.

We can only recommend that you try the latest beta version (Viewer, Host and Server) and see if it fixes the issue. There have been a lot of improvements in this beta including fixes to connectivity issues on RU Server etc, see release notes.

You can download the beta from here https://www.remoteutilities.com/download/beta.php

Hello Victor,

If multiple authentication methods are enabled on the remote Host (e.g. Single password, AND RU Security etc.) the program still uses one of them during a connection. Which one depends on your settings on the Viewer side -> Connection properties -> Authentication tab.



If Auto is set the Viewer uses the first available authentication method according to this order:

Custom Server Security (CSS)
Windows Security
Remote Utilities Security
Single password

As you can see, since you have enabled RU Security and Single password and have your auth method set to Auto, Viewer will always force RU Security when you authenticate.

To override this behavior for specific Hosts you just need to select the desired authentication method in the drop down list and Viewer will always use that. In your example just select Single password to override the automatic sequence check.

Hope that helps.

Hi Rob,

It's the regular 443.

Could it be that you have a proxy in between the Internet and your network from where you are trying to access the configuration server?

Hi Rob,

Does it show any specific error?

Also, you should make sure that you allow *.remoteutilities.com on your perimeter firewall for Viewer app.

Hello Rob,

Thank you for your message.

I have just checked the work of MSI configurator (Viewer 6.10 stable, if that's the version that you mean). It works.

Or maybe you meant something else by the configuration server?

Vasilis Lourdas wrote:
The relay still remains in b2. I cannot upgrade the software at the moment, since there are many users connected and it has solved our initial issues with the stable 2.8.2.0 release. I'd like to keep it to b2 at the moment.

We will test this configuration in our testing laboratory and let you know if we manage to reproduce the issue.

Thanks.

Vasilis Lourdas wrote:

Still the same error as before.

Hi Vasilis,

Are you connecting to RU Server beta 2 or to RU Server beta 3?

Vasilis Lourdas wrote:

Hi Conrad,

I used the portable viewer. Should I still try it again with the portable zip?

Yes, the portable Viewer has also been updated.

Hi Vasilis,

If you still experience issues please try the following:

- Uninstall Viewer (using Windows settings -> Apps)
- Download the beta Viewer installer from the site (Download -> Windows (beta) and install it

There was a very minor issue with licensing/trial so we just updated the installer without updating beta version number.

Thanks.

Hello Vasilis,

Vasilis Lourdas wrote:

Does the b3 host work correctly with the relay server in b2? I'm asking because I have installed b3 of host in a Windows XP PC, which is registered to connect to the b2 relay server, but using the b3 viewer, I cannot logon to the host PC, I get a "No response from server".

If you decided to use/test beta version we recommend that you update all modules rather than just some of them. For example, if you use Viewer and Host beta 3 we highly recommend that your server is also beta 3. We cannot guarantee correct work if there is version mismatch, even in the case of beta. Besides, the beta version per se is supposed to have bugs (hence it's beta) which need to be revealed and fixed by the final release.

As far as beta testing we also recommend that you always keep it separate from your production environment and not entirely rely on beta for mission-critical tasks. For example, if you want to test new beta features you could run another self-hosted server with beta installed and test it with Viewers and Hosts of the same beta.  

Thanks.