Forum / Remote Desktop Manager Mac - Support

RDM MacOS Version 4.6.0.0 no Connection to Devolutions Server

  • Create an Issue
  • Cancel

Hi,

after the update of the RDM Client for MacOS from Version 4.5.3 to 4.6.0 the client is not able to connect to our Devolutions Server anymore.

Client OS: MacOS 10.13.1, 10.12.6
RDM: 4.6.0.0 Enterprise Edition
DVLS: 4.7.0.0

Here is a excerpt of the Log:


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) [0x00424] in <453df6b1103d4ce4a4d684269bb98739>:0
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSConnectionDataSource.c4fbf2ba562f39b1b6b2d372fbb6d47bd (System.Boolean cd3040496c69eadd433452158ca11b30b, System.String& cb72c9169e711f40c477598ce7c102f30, System.String& c20a45f64caf6be3bb404afc7e28da849, System.Boolean cb57de9c84c4a21c183a458242ccec964) [0x0032b] in <453df6b1103d4ce4a4d684269bb98739>:0
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSConnectionDataSource.cae5bd7eddbd366041c78928a64d0ca0c (System.Boolean cd3040496c69eadd433452158ca11b30b) [0x000a3] in <453df6b1103d4ce4a4d684269bb98739>:0
at A.c1b807d37db2144cd6c319286f4867982.get_c47d7d7b5e1cbd6892c95fb0bd7fbb239 () [0x00085] in <453df6b1103d4ce4a4d684269bb98739>:0

FEHLER unbeaufsichtigt:System.Net.WebException: The request timed out
at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00049] in <f59da151032a4cc38ecf96f0c7b58a7c>:0
at System.Net.HttpWebRequest.GetResponse () [0x0000e] in <f59da151032a4cc38ecf96f0c7b58a7c>:0
at Devolutions.Server.ApiWrapper.RestClient.GetResponse[T] (System.Net.HttpWebRequest request) [0x00000] in <8b83cb601e2e4829bf37f63d8332e67b>:0
at Devolutions.Server.ApiWrapper.RestClient.GetInfoDataRequest[T] (System.String apiUrl) [0x0000d] in <8b83cb601e2e4829bf37f63d8332e67b>:0
at Devolutions.Server.ApiWrapper.RDMSWebClient.GetForcePublicIPValidation () [0x00000] in <8b83cb601e2e4829bf37f63d8332e67b>:0
at A.c1b807d37db2144cd6c319286f4867982.c930bd5b626ba1f9550231e72fd8960a4 () [0x00006] in <453df6b1103d4ce4a4d684269bb98739>:0
at A.c1b807d37db2144cd6c319286f4867982.ce833446862eab232a0c13d24e8de975c[ceaa9d1a76410934033f88a1b7444f6db] (A.c1b807d37db2144cd6c319286f4867982+cf41769b35300b2e72a2a8308d063dd77`1[ceaa9d1a76410934033f88a1b7444f6db] c8be9364c30ccbab7824d5be6f0f71e5e) [0x00006] in <453df6b1103d4ce4a4d684269bb98739>:0
at A.c1b807d37db2144cd6c319286f4867982.c8fef2b2605cac885a4c7d2cb6d93f1cc () [0x00000] in <453df6b1103d4ce4a4d684269bb98739>:0
at A.c1b807d37db2144cd6c319286f4867982.c66e57593687012130fea4e7f58d3956b[ceaa9d1a76410934033f88a1b7444f6db] (A.c1b807d37db2144cd6c319286f4867982+cf41769b35300b2e72a2a8308d063dd77`1[ceaa9d1a76410934033f88a1b7444f6db] c8be9364c30ccbab7824d5be6f0f71e5e, System.Boolean c26620762db9a4e887d5191ac3859d4b3) [0x00073] in <453df6b1103d4ce4a4d684269bb98739>:0


Downgrading to Version 4.5.3 fixes the Problem.

Why is there always a Connection Problem with the server in your new "Major" Releases??

Greetings

Frank

Clock2 yrs

Hi Frank,

There seems to be a regression in the version 4.6.0.0 when it comes to the fixes with Active Directory accounts.

I have no clue what could have happened since we're still building against Mono 4.8.1.0.

We've recently switch architecture for the application, which required us to switch API. This might be the root of the issue.

I'll hopefully have this resolved in the upcoming 4.6.1.0.

Once again, I'm deeply sorry for any inconveniences.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

Hi,

ok, thx for your answer. Any idea when 4.6.1.0 will be available?

Greetings

Frank

Clock2 yrs

Well, I'm hoping to get it out next week.

I intend on building it this week and having it go through QA in the mean time. We'll see how it goes from then on.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

Hi again,

I'm just following on my investigation.

So I've looked into it and it appears that, with the new API, the version gets build against Mono 5.2.0.0 (which has your issue) pretty much against our will. I even tried to delete all frameworks versions other than 4.8.1.0 and it still build against 5.2.0.0 somehow. I've notified Xamarin and waiting for a reply.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

Hi Frank,

Could I ask what address format you use in your DVLS data source configuration that has the issue in 4.6.0.0? What I mean is, do you use the IP address directly (ex.: https://192.168.12.123/{DVLS-Instance}), the host name (ex.: https://hostname/{DVLS-Instance}) or the fully qualified domain name (ex.: https://hostname.domain.loc/{DVLS-Instance})?

In my case, on the server where I can reproduce the issue, it appears to only occurs while using the fully qualified domain name.

If you're using the fully qualified domain name, could you try using just the IP or just the host name and see if this resolves the timeout?

I'd like to confirm if we're having the same issue? If this is the case, I can probably fix this regardless of Mono.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

Hi,

i am using the FQDN. I tried just the hostname or just the IP and the error is the same.

greetings

frank

Clock2 yrs

Maybe your hitting this issue: https://bugzilla.xamarin.com/show_bug.cgi?id=57106

Though, I can't be entirely sure without reproducing it myself.

Until we either get news from Xamarin or find a workaround ourselves, I'd recommend you and any other users connecting to your server to not update beyond RDM 4.5.3.0.

I'll post back on this thread if I get any news (hopefully good ones).

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

Hi,

is this issue fixed in the recently released 4.6.1 Version?

greetings

frank

Clock2 yrs

Hi Frank,

Unfortunately no. I'm keeping an eye on this issue on the Xamarin side.

It'd be safer to wait news from me before updating.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

OK, then we will wait :-)

Clock2 yrs

Hi Xavier,

just checked the Bugzilla Page you mentioned.
The last posts did not sound great "

At the earliest, the feature could possibly be included by mid-to-late 2018."

So we have to wait till the end of 2018 to get a working release of the new RDM?

greetings

frank

Clock2 yrs

Hi Frank,

I'm subscribed to this issue (and a couple others related to the HttpWebRequest). Mono have rewritten their implementation of the related code and changed the behavior. As noted, we can't expect a fix to this in the near future and I can't revert back to the old API. I'd suggest sticking to pre 4.6 versions of RDM for a while.

If you find an issue you can't work around or really want a feature in a newer version of RDM, I'll look into building against an older version of Xamarin.Mac, even though this is less than recommended. This would require a certain level of probing though, through trial and errors, to find a right version of Xamarin.Mac since this is not so clear which version of Xamarin.Mac contains pre 5.0 versions of Mono.

Once again, I'm deeply sorry for any inconveniences.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs