Forum / Remote Desktop Manager Mac - Bug Report

RDM 4.4.0.0 not able to connect to Devolutions Server

  • Create an Issue
  • Cancel

Hi,

since updating to RDM 4.4.0.0 (even tried 4.4.1.0) our clients could not connect to the central Devolutions Server.
Serverversion is 4.5.0.0

The Login doesn´t work anymore.

here are some error messages:


A.c80ba12e4d0dcd22500b279e220e08230: DVLS Server reagiert nicht.

The request timed out
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSConnectionDataSource.cd96829f27d293a743effbe7a3b6ba887 (System.String cb72c9169e711f40c477598ce7c102f30, System.String c20a45f64caf6be3bb404afc7e28da849, System.Boolean c5b0819a95492676dc7db6a305ea020b9, System.Boolean c5e14770608c435408473af306b99bcc2, System.Boolean c28dc07d126c726de19e981a187d0c585) [0x0041d] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSConnectionDataSource.c4fbf2ba562f39b1b6b2d372fbb6d47bd (System.Boolean cd3040496c69eadd433452158ca11b30b, System.String& cb72c9169e711f40c477598ce7c102f30, System.String& c20a45f64caf6be3bb404afc7e28da849, System.Boolean cb57de9c84c4a21c183a458242ccec964) [0x0032b] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSConnectionDataSource.cae5bd7eddbd366041c78928a64d0ca0c (System.Boolean cd3040496c69eadd433452158ca11b30b) [0x000a3] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
at A.c1b807d37db2144cd6c319286f4867982.get_c47d7d7b5e1cbd6892c95fb0bd7fbb239 () [0x0007e] in <91b5f1e8ce424d6380dff7ae80fa23db>:0


If you need any more information to fix this, just ask.

Greetings

Frank

Clock2 yrs

[26.07.2017 12:09:18]ERROR SILENT System.Net.WebException: The request timed out
at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00049] in <5afdc70d980c4033b3878286f754d091>:0
at System.Net.HttpWebRequest.GetResponse () [0x0000e] in <5afdc70d980c4033b3878286f754d091>:0
at Devolutions.Server.ApiWrapper.RestClient.GetResponse[T] (System.Net.HttpWebRequest request) [0x00000] in <75f6f508c8d24af08b4af760769c45e7>:0
at Devolutions.Server.ApiWrapper.RestClient.GetInfoDataRequest[T] (System.String apiUrl) [0x0000d] in <75f6f508c8d24af08b4af760769c45e7>:0
at Devolutions.Server.ApiWrapper.RDMSWebClient.GetForcePublicIPValidation () [0x00000] in <75f6f508c8d24af08b4af760769c45e7>:0
at A.c1b807d37db2144cd6c319286f4867982.c83f4198aadc938a18e7b198a950c56e8 () [0x00006] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
at A.c1b807d37db2144cd6c319286f4867982.c66e57593687012130fea4e7f58d3956b[ceaa9d1a76410934033f88a1b7444f6db] (A.c1b807d37db2144cd6c319286f4867982+cf41769b35300b2e72a2a8308d063dd77`1[ceaa9d1a76410934033f88a1b7444f6db] c8be9364c30ccbab7824d5be6f0f71e5e) [0x0006c] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
[26.07.2017 12:13:17 - 4.4.1.0]ERROR System.NullReferenceException: Object reference not set to an instance of an object
at A.c1b807d37db2144cd6c319286f4867982.c83f4198aadc938a18e7b198a950c56e8 () [0x00006] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
at A.c1b807d37db2144cd6c319286f4867982.c7d243ecdeab60be31ace174fecff1a85[ceaa9d1a76410934033f88a1b7444f6db] (A.c1b807d37db2144cd6c319286f4867982+cf41769b35300b2e72a2a8308d063dd77`1[ceaa9d1a76410934033f88a1b7444f6db] c8be9364c30ccbab7824d5be6f0f71e5e, System.String cded30e1458beea22980c99c2b20c7dff) [0x0003b] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
at A.c1b807d37db2144cd6c319286f4867982.c66e57593687012130fea4e7f58d3956b[ceaa9d1a76410934033f88a1b7444f6db] (A.c1b807d37db2144cd6c319286f4867982+cf41769b35300b2e72a2a8308d063dd77`1[ceaa9d1a76410934033f88a1b7444f6db] c8be9364c30ccbab7824d5be6f0f71e5e) [0x001cb] in <91b5f1e8ce424d6380dff7ae80fa23db>:0

[26.07.2017 12:13:17]ERROR SILENT System.NullReferenceException: Object reference not set to an instance of an object
at A.c1b807d37db2144cd6c319286f4867982.c83f4198aadc938a18e7b198a950c56e8 () [0x00006] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
at A.c1b807d37db2144cd6c319286f4867982.c7d243ecdeab60be31ace174fecff1a85[ceaa9d1a76410934033f88a1b7444f6db] (A.c1b807d37db2144cd6c319286f4867982+cf41769b35300b2e72a2a8308d063dd77`1[ceaa9d1a76410934033f88a1b7444f6db] c8be9364c30ccbab7824d5be6f0f71e5e, System.String cded30e1458beea22980c99c2b20c7dff) [0x0003b] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
at A.c1b807d37db2144cd6c319286f4867982.c66e57593687012130fea4e7f58d3956b[ceaa9d1a76410934033f88a1b7444f6db] (A.c1b807d37db2144cd6c319286f4867982+cf41769b35300b2e72a2a8308d063dd77`1[ceaa9d1a76410934033f88a1b7444f6db] c8be9364c30ccbab7824d5be6f0f71e5e) [0x001cb] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
[26.07.2017 12:18:33]ERROR SILENT WebAPI.c83f4198aadc938a18e7b198a950c56e8 returned null.
[26.07.2017 12:20:16 - 4.4.1.0]ERROR A.c80ba12e4d0dcd22500b279e220e08230: DVLS Server reagiert nicht.

The request timed out
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSConnectionDataSource.cd96829f27d293a743effbe7a3b6ba887 (System.String cb72c9169e711f40c477598ce7c102f30, System.String c20a45f64caf6be3bb404afc7e28da849, System.Boolean c5b0819a95492676dc7db6a305ea020b9, System.Boolean c5e14770608c435408473af306b99bcc2, System.Boolean c28dc07d126c726de19e981a187d0c585) [0x0041d] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSConnectionDataSource.c4fbf2ba562f39b1b6b2d372fbb6d47bd (System.Boolean cd3040496c69eadd433452158ca11b30b, System.String& cb72c9169e711f40c477598ce7c102f30, System.String& c20a45f64caf6be3bb404afc7e28da849, System.Boolean cb57de9c84c4a21c183a458242ccec964) [0x0032b] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSConnectionDataSource.cae5bd7eddbd366041c78928a64d0ca0c (System.Boolean cd3040496c69eadd433452158ca11b30b) [0x000a3] in <91b5f1e8ce424d6380dff7ae80fa23db>:0
at A.c1b807d37db2144cd6c319286f4867982.get_c47d7d7b5e1cbd6892c95fb0bd7fbb239 () [0x0007e] in <91b5f1e8ce424d6380dff7ae80fa23db>:0

Clock2 yrs

Hi Frank,

I thought at first this might be a compatibility issue between RDM Mac 4.4.0.0 and DVLS 4.5.0.0, but I do not seem to reproduce the issue.

I'll look into the logs you've sent us and come back to you if I need more information.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

Hi Frank,

I'm still unable to reproduce your issue. While one of the error in the log has now been fixed, this is most likely not the cause of your issue. And I'm still puzzled by the timeout one.

You said this started in the last version of RDM (4.4.0.0), right? To make sure this is a client only issue, could you download the previous version (4.3.0.0) and tell me how it goes? Here it is: https://cdn.devolutions.net/download/Mac/Devolutions.RemoteDesktopManager.Mac.4.3.0.0.dmg.

Is there anything particular about your users account you could tell me? Are they set up with a Two Factor? What's the authentication type of your users account?

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

Hi,

i have already downgraded (a collegue of mine also) and it works. The 4.3.0.0 Version worked before the update to 4.4.0.0 and also after the downgrade.
The useraccounts are our active directory accounts. Nothing special like 2 factor or so.
When i try to connect via webbrowser to the devolutions server then he prompts me for a client certificate, before the login window. When i manually present my client machine certificate the server shows the login page.
Perhaps there is a problem with the rdm not presenting the certificate to the server? I have checked my keychain and all apps have access to the cert and the corresponding key.

greetings

frank

Clock2 yrs

Hi Frank,

I think I've reproduced your issue. This seems to have something to do with the Active Directory accounts. I'll investigate further and come back to you when I make some progress.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

Hi Frank,

I'm pretty sure I fixed the issue. The issue lies with our development framework. I've reverted to an earlier version of that framework and I no longer have the issue. This was also the cause of another known issue related to web request.

Could you confirm by testing this version: https://www.dropbox.com/s/nlug87wvbbulac1/Devolutions.RemoteDesktopManager.Mac.4.4.1.0%20-%20Mono%204.8.1.0.dmg?dl=0.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

WOW, thats fast. Yes it is working now. Launching takes some time (acceptable) and it connects to the server.

thx a lot for the fix!!

Greetings

Frank

Clock2 yrs

Glad to hear it!

Don't hesitate if you find any other issues.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs