You've broken the ability to connect to an RD Gateway

You've broken the ability to connect to an RD Gateway
5

Upvotes

Upvote

 Dec 17 2021
21 Comments (21 New)
Closed

version 10.7.2 for Mac broke the ability to connect to an RD Gateway.  Rolling back to previous versions restores this ability.

Comments
Senior Member

How were you able to roll back to a previous version? I have the same issue. I attempted to uninstall the app but read that it is not possible to roll back to a previous version.  

Regular Visitor

I installed the most recent release of 10.7.1 from this beta page:  https://install.appcenter.ms/orgs/rdmacios-k2vy/apps/microsoft-remote-desktop-for-mac/distribution_g...

 

It is a beta release but functionally equivalent to the production version of 10.7.1.

Microsoft

@lsorensewere you able to connect to a RD Gateway by downloading the most recent release of 10.7.1 as noted by willahlborn? (https://install.appcenter.ms/orgs/rdmacios-k2vy/apps/microsoft-remote-desktop-for-mac/distribution_g...

Senior Member

No, I received the same error message as when I used the most current version 10.7.2 and 10.7.3. The error message I receive is: 

 

Error connecting to Remote DesktopError connecting to Remote Desktop

Microsoft
Status changed to: Active
 
Microsoft

@lsorense,

Apologies for this inconvenience, the AVD engineering team has been notified of your case. We will follow up with additional questions in the case more information is needed for internal debugging of this error.

Regular Visitor

Screen Shot 2021-12-17 at 10.06.20 AM.png

 That's not the message we were getting--with any version newer than 10.7.1, we were getting "We couldn't connect to the Remote Desktop Gateway because of an internal error.  Error code: 0x300006c"

Microsoft
Status changed to: Tell us more

@willahlborn 

Can you please provide more detail on how this error - Error code: 0x300006c" - occurred. The most informative method would be providing a video to the email alias rdios@microsoft.com (footage from a phone camera works perfectly fine) that demonstrates your experience in the app and providing any configuration details of your Remote Desktop. An alternative if you cannot take a video would be providing detailed steps on how the error occurs and how it can be reproduced. This will help us provide support as quickly as possible. Thanks!

Regular Visitor
Hi, I am experiencing the same issue, and I explain what I encounter after debugging  the issue:

https://techcommunity.microsoft.com/t5/azure-virtual-desktop-feedback/msrdc-10-7-2/idi-p/3042147

Maybe this information is helpful.

Thanks.

 

Note:

be aware that the gateway feature doesn't work for everyone with the latest version of MSRDC, it's urgent.

Visitor

Hi, we are also experiencing this problem. We use a (tcp)loadbalancer/firewall in front of the RD Gateway servers. We noticed when we bypass this loadbalancer everything seems to work, but that is not an option for us.

 

After investigation we found out that the problem is caused by client now opening 2 connections simultaneously. The loadbalancer splits these connections to different RD Gateway's, and that doesn't work. By making the loadbalancer 'sticky', making sure both connections go to the same RD Gateway, the most recent version of the Mac client works again.

 

Visitor

The client does not ask for an upgrade to websockets anymore since 10.7.2 and falls back to legacy connections (hence 2 connections being created). This was confirmed by a wireshark trace. This is a regression.

Microsoft

@_NoLess_ @bolke 

Thank you for your feedback and apologies for the unfortunate timing of this problem as a significant amount of our engineering team is on holiday. I can assure you this is a high priority, and you will receive a response once progress is made. As mentioned previously in the thread, the most informative method would be providing detailed info to the email alias rdios@microsoft.com. Furthermore, in the meantime can always access previous versions of the Beta versions at https://install.appcenter.ms/orgs/rdmacios-k2vy/apps/microsoft-remote-desktop-for-mac/distribution_g...and users who have also faced a similar issue provided that the most recent version of 10.7.1 is stable and does encounter this problem. 

Microsoft
Senior Member

I am still getting the error message with the Beta version. 

Microsoft

@lsorense Are you using a WebSocket gateway or a gateway behind a load balancer? 

Senior Member

The gateway is behind a load balancer

Microsoft

@lsorense 

Ok, let's try to repro the issue with engineers. If possible, can you please reach out to rdios@microsoft.com with a test username and password. Any other information related to your deployment that can I help us repro will be helpful. Thanks!

Senior Member

The remote connections are to my clients and I don't have the authorization or administrative ability to set up a test account to login to my client's environment. I am not certain what other details you need to reproduce except I am running on the MacOS Monterey and downloaded the beta version of 10.7.4 and am getting the error both on 10.7.3 and 10.7.4. 

 

What other options do we have? 

Microsoft

@lsorense 

Sorry that the new update hasn't resolved your issue, based off the comment "No, I received the same error message as when I used the most current version 10.7.2 and 10.7.3." then your issue does appear to unrelated to the load balancer changes in 10.7.2/3 and therefore the resulting patch in 10.7 and unrelated to this current thread.
That said, if we cannot use a test account a repro your issue, a good place to start will be eliminating the possibility the issue is unrelated to macOS, can you please try connecting to your remote resources with the Windows Remote Desktop client and if the behavior is only reproducible on macOS create a new thread. Thanks!
Senior Member

Thanks for the follow-up. I do know they are on a load-balancer gateway but I can also confirm I can successfully connect to the same remote desktop using the same gateway using the Windows Remote Desktop client without issue. I am actually connected to their environment using the Windows Remote Desktop right now. I believe I do have another thread related to this issue that I will update. 

Microsoft
Status changed to: Closed