tcnsltd

Hi Andre,

We're using the exact same version, 4.3.6563.5232 in our environment

Hi Andre,

Our screenconnect installation is set on port 80 - it seems somewhat pointless to have it on a custom port when using it for remote support and meetings!

Also for future reference, there are no firewalls whatsoever between the PCs and screenconnect server in this testing phase.

Hi guys,

Any update on this? Don't expect to wait 2 weeks just for at least a *response* of some kind other than someone will look into it.

Hello,

We're evaluating both the latest version of RDM, and ScreenConnect 4.3 to use in our environment. We have various windows devices added to screenconnect as unattended sessions, and are hoping to integrate these into RDM so that we can organise and manage them in our team effectively, without having to create hundreds of session groups in screenconnect.

The problem we're currently facing is that as soon as we provide the Host, Username and Password to the RDM Session, and attempt to select a ScreenConnect Session name, RDM alerts that it cannot connect to the server:

The server address, username and password are most definitely correct, and adding a RDM Session of type Web and going to the screenconnect server url, it loads correctly:

Any assistance on resolving this matter would be much appreciated.

Thanks

edited by tcnsltd on 6/2/2014