We couldnt connect to the remote desktop gateway because of an internal error mac

Fix for Error Message 0x3000064 after Remote Desktop mote update to 10.5.0 on Mac

After installing the most recent 10.5.0 update, I am now receiving an error code 0x3000064 and am unable to gain access to my remote desktop with my organization. Does anyone have a fix for this or now how I can get the previous version back?

remote-desktop-services
Comment
Comment · Show 2
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ElevenYu-MSFT · Dec 08, 2020 at 03:09 AM

Hi,

Please check below two answers to see if they can help you.

If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

0 Votes 0 ·
MLL-1439 ElevenYu-MSFT · Dec 22, 2020 at 02:29 PM

Thank you so much for posting your solution. I had all but given up on using my MacBook Pro to connect to my IBM-based office, as had my IT team. I was actually shopping for a new non-Mac laptop which is comparable to my Mac when I came across your post. Thankfully, deleting the current MS Remote Desktop app and replacing it with v. 10.4.1 (1825), per your instructions, did the trick. Thank you, Thank you!

0 Votes 0 ·
ElevenYu-MSFT answered Dec 7, '20 | KTISM-6962 commented Dec 11, '20

Hi,

We received several users' posts to report the same error you have encountered. This might be an issue of the latest version of remote desktop app for mac, but there is no related official document at the moment since the update was just released several days ago.

If you would like to get back to the previous version, please try to uninstall the current app and then check if you can download and install previous versions from below link.
https://install.appcenter.ms/orgs/rdmacios-k2vy/apps/microsoft-remote-desktop-for-mac/distribution_groups/all-users-of-microsoft-remote-desktop-for-mac

Also, we suggest that you could post this error to the uservoice and let others vote for it to see if there will be any feedback from the product team.
https://remotedesktop.uservoice.com/forums/287834-remote-desktop-client-for-mac

Thanks,
Eleven


If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

Comment
Comment · Show 5
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MagnusOlsson-4962 · Dec 08, 2020 at 11:12 AM

Many user have posted this to uservoice. And now this must be taken seriously! Many are working remotely because of the covid.
Br,
Magnus

0 Votes 0 ·
RichardKrstrm-6602 · Dec 08, 2020 at 12:57 PM

Locked out from all my clients systems thanks to this. Working from home due to COVID. Need a fix asap.

0 Votes 0 ·
KTISM-6962 · Dec 09, 2020 at 02:09 AM

I uninstalled the 10.5 and reinstalled this link version provided and it is not to the previous version but rather to a Beta 10.5 version which doesn't work either.

0 Votes 0 ·
ElevenYu-MSFT KTISM-6962 · Dec 09, 2020 at 02:22 AM

Hi,

You need to scroll down the web page to find the previous version. If you install the version such us Version 10.4.1 (1825), is it still not to the previous verison?

We couldnt connect to the remote desktop gateway because of an internal error mac


0 Votes 0 ·
image.png (50.1 KiB)
KTISM-6962 ElevenYu-MSFT · Dec 11, 2020 at 01:33 AM

Thank you. I didn't scroll down far enough and after uninstalling 10.5.0 and reinstalling the 10.4.1 (1825), I am able to access it again! Yahoo!

0 Votes 0 ·
HESDINJeanFranois-1859 answered Dec 7, '20

Hello,

We are facing the same issue since 10.5.0 arrived. We have about 20 users impacted using MAc client. PC clients are not impacted. After several tests we have determined that the fault is related to RPC over HTTPS implementation that seems to be broken.

The only workaround I have found is to use DNAT on our firewall instead of the reverse proxy to be fully transparent between the client and the RDS GW.

Last year we faced the same issue with v10.3.4 and was fixed with version 10.3.5

Regards

J.F

Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HESDINJeanFranois-1859 answered Dec 8, '20

Hello,

By using apple store applications like MS Remote Desktop Client, downgrade is impossible.

As this feature was working fine before release 10.5.0, I cannot understand why we should wait for other people to vote to have a feedback from dev team.

Regards

Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MagnusOlsson-4962 answered Dec 8, '20

We have the same issue.
Downgraded manually to version 10.4.0. (could not find newer stable version)
Turned of auto update manually on 120 + mac computer.
Please roll out a fix asap.
And, if you check uservoice there are more and more users reporting the same issue.

Br,
Magnus

Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RichardKrstrm-6602 answered Dec 8, '20 | RichardKrstrm-6602 published Dec 8, '20

Im totally locked out from my clients systems thanks to this update, tried the link posted above to the beta, but to no avail.
@ElevenYu-MSFT - we need update about this asap. I cant downgrade from Big Sur either.

Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JorgeRaigoza-7972 answered Dec 8, '20 | JorgeRaigoza-7972 edited Dec 8, '20

We updated to the Beta version of the app and everything started working again. This was suggested by a MS Engineer in a different post.

Beta: https://install.appcenter.ms/orgs/rdmacios-k2vy/apps/microsoft-remote-desktop-for-mac/distribution_groups/all-users-of-microsoft-remote-desktop-for-mac
Post: https://docs.microsoft.com/en-us/answers/questions/187935/error-0x3000064-microsoft-remote-desktop.htmlerror-0x3000064-microsoft-remote-desktop.html
MacOS: 10.15.7 (Catalina)

  • Jorge Raigoza
    The Computer Support People


Comment
Comment · Show 2
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RichardKrstrm-6602 · Dec 08, 2020 at 02:40 PM

Hello Jorge,
This did not work for me, same issue even when beta is used.

Using Big Sur and got problem after update.

0 Votes 0 ·
JorgeRaigoza-7972 RichardKrstrm-6602 · Dec 08, 2020 at 06:42 PM

That's unfortunate, Richard. My client is on MacOS 10.15.7 (Catalina).

0 Votes 0 ·
ElevenYu-MSFT answered Dec 9, '20 | MicahWallace-0679 published Nov 15, '21

Hi,

Thanks for all of you to post this issue. We have also submitted this issue to our Product Team, so that they can investigate the issue as soon as possible. However, we cannot guarantee the fix date since it it out of forum's control. Appreciate your understanding.

If Beta version cannot work for you, please also try below to see if it helps.

Go to Microsoft Remote Desktop > preferences > General Tab> uncheck “use system proxy configurations “ and
Also uncheck “Use hardware acceleration ”

Thanks,
Eleven


If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

Comment
Comment · Show 2
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KTISM-6962 · Dec 09, 2020 at 02:13 AM

Nope doesn't work either.

0 Votes 0 ·
MicahWallace-0679 · Nov 15, 2021 at 09:57 PM

This worked, thanks a lot!

0 Votes 0 ·
VincentRobinson-7935 answered Jan 23, '21

10.5.1 was released 2 days ago (Jan. 19), but it doesn't solve the issue either. It does work to remote through a Gateway and to an individual PC, but fails when remoting through the same Gateway to an RDP cluster. Prior to 10.5.x, it worked well.

This continues to be a widespread issue and is identifiable enough for MS to have figured something out -- it's approaching 2 months now. We appreciate the resources MS has put into the Mac client in recent years (it languished for a long time prior to that), but this has become problematic.

Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ReidGuanti-7730 answered Mar 10, '21 | ReidGuanti-7730 edited Mar 10, '21

10.5.2. was released on March 7 2021 and explicitly stated in the release notes:

"Fixed an issue where RD Gateway connection would fail with a 0x3000064 error code."

However, I am still getting the error when a user account is selected in the server's connection settings. I am connecting to a load balanced, RD Gateway cluster.

Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Kvan-5371 answered Sep 28, '21 | Kvan-5371 published Sep 28, '21

Even in 10.6.8 this is not fixed.
Does anybody have a solution for M1 books? I am not sure if I can go back to 10.4.1.

Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

What is the error code 0x3000079

I tried to access my PC from my tablet PC. I installed "remote desktop" application and insert information.
But it showed me 0x3000079 error. It tell me "Unable to connect. couldn't connect to Remote Desktop Gateway because of an internal error"

How can I solve it?

remote-desktop-client
Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Jingruihan-MSFT answered May 20, '21

Hi,

Thank you for contacting us.

For better clarity and to assist you better I would require more information regarding this:

Please provide the Microsoft Remote Desktop Version.

Best regards

Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GreenGhost-6598 answered May 23, '21

Not the original poster, but I'm getting the same error trying to access my PC from my Android phone (0x3000079).

The version of the Android app that I'm using is 10.0.110.1129, however I am not sure if that's what you're asking for, or if you're referring to the version number of something on the host PC. If it's the latter, please provide instructions on how to find the version number that you're looking for.

Hopefully we can solve this.

Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Jingruihan-MSFT answered May 25, '21

Hi,

Haven't received your message a few days, was your issue resolved?

I note that you have mentioned that "Unable to connect. couldn't connect to Remote Desktop Gateway because of an internal error". Let's consider whether there are protection settings between Remote Desktop Gateway and client (such as TMG, firewall). If there is one, it may be set by rule or block. Moreover, can you share the configuration details of your RDS environment, including how many RDS server and their versions, which roles are configured.

Looking forward your reply.

Best regards

Comment
Comment Show 0
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

tarlok-5007 answered May 31, '21 | tarlok-5007 commented Jun 5, '21

I have same error code while trying to connect pc at remote location please anyone have answers how to fix it does iPhone app supported for remote pc or it work at local network only

Comment
Comment · Show 1
Comment
5 |1600 characters needed characters left characters exceeded
  • Visible to all users
  • Visible to the original poster & Microsoft
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Visible to all users

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

tarlok-5007 · Jun 05, 2021 at 08:49 PM

Anyone have idea how to fix above error code

0 Votes 0 ·

Question: Q: Microsoft RDP client for Mac receiving "Unable to connect" error code 0x5000007 from Microsoft RD Gateway

We have an RD Gateway server setup and running well. All of our Windows clients can use MS RDP client from outside of the LAN, but Mac users continue to receive and error; "Unable to connect Your session ended because of a protocol error while communicating with the Remote Desktop Gateway. If this keeps happening, contact your network administrator for assistance."


I can successfully connect a Mac running MS RDP client to computers on the network, but fail when accessing from outside of the firewall, through the gateway server.


i'm so so so stuck. help please.

More Less

Posted on Apr 2, 2020 5:10 PM

Reply I have this question too(54) I have this question too Me too(54) Me too

Apr 3, 2020 4:17 AM in response to RichardVisageMe In response to RichardVisageMe

This forum is for Apple's Remote Desktop and therefore not for you. Microsoft's Remote Desktop forum is here:


https://remotedesktop.uservoice.com/forums/287834-remote-desktop-client-for-mac


You should have a word with your network administrator and ask them the question. FWIW I think there's a certificate or a protocol setting that needs to be configured somewhere that will allow your Mac to 'pass-through'. This could be something built-in on a PC or pre-configured when your IT department roll out the setting to their PC clients. Be patient and persistent and don't let them fob you off simply because you're on a Mac and not a PC. They should be supporting you properly irrespective of platform. It's their job after all


More Less

Apr 3, 2020 4:17 AM

Reply Helpful
Thread reply - more options
  • Link to this Post

Apr 3, 2020 1:43 PM in response to RichardVisageMe In response to RichardVisageMe

If you have a good rapport with your IT support team then ask them if you need to install an SSL certificate on your Mac. My understanding is the RD Gateway requires this for RD clients to connect successfully. The other aspect of this is whether you have to establish a VPN first. Now this may or may not be a requirement prior to using MRD but its worth asking.


I've had another look and found this:


https://remotedesktop.uservoice.com/forums/925639-remote-desktop-beta-client-for-ios/suggestions/39205006-rd-gateway-error-0x3000066


Ask if TLS v1.2 is enabled and make sure you're on the latest macOS. Worth a try?


Good luck!

More Less

Apr 3, 2020 1:43 PM

Reply Helpful
Thread reply - more options
  • Link to this Post

12 Replies

· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pure Capsaicin
OP
DragonsRule
We couldnt connect to the remote desktop gateway because of an internal error mac
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
Jun 4, 2020 at 20:29 UTC
Microsoft Remote Desktop Services expert
102 Best Answers
339 Helpful Votes

terrencet wrote:

After soliciting help from my network administrator, we were still unable to resolve the issue.

You are not in the IT department, then?

1
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Mace
OP
Best Answer
Justin1250
We couldnt connect to the remote desktop gateway because of an internal error mac
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
Jun 4, 2020 at 20:29 UTC

Are the subnets the same? Wifi 2 and your corporate office that you are VPNing into?

If yes, changing the subnet on wifi2 should fix the issue.

1
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pimiento
OP
terrencet Jun 4, 2020 at 20:36 UTC

I am a developer, not an administrator, and I do not profess to be one.

1
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pure Capsaicin
OP
DragonsRule
We couldnt connect to the remote desktop gateway because of an internal error mac
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
Jun 4, 2020 at 20:37 UTC
Microsoft Remote Desktop Services expert
102 Best Answers
339 Helpful Votes

terrencet wrote:

I am a developer

Well, a dev would mean you work in IT, yes?

0
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pimiento
OP
terrencet Jun 4, 2020 at 20:55 UTC

Justin1250​ in fact the subnet for Wifi2 is the same as the subnet for the office machine. How do I change the subnet?

  • We couldnt connect to the remote desktop gateway because of an internal error mac
    Justin1250
    Mace
0
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pure Capsaicin
OP
DragonsRule
We couldnt connect to the remote desktop gateway because of an internal error mac
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
Jun 4, 2020 at 20:57 UTC
Microsoft Remote Desktop Services expert
102 Best Answers
339 Helpful Votes

Most likely you are getting your IP from your home router. You'll need to login to that and find the Wifi setup. There, you can change the IP subnet that's in use.

1
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pimiento
OP
terrencet Jun 4, 2020 at 20:58 UTC

DragonsRule​ FWIW, I work in IT but that is not my role.

  • We couldnt connect to the remote desktop gateway because of an internal error mac
    DragonsRule
    Pure Capsaicin
1
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pure Capsaicin
OP
DragonsRule
We couldnt connect to the remote desktop gateway because of an internal error mac
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
Jun 4, 2020 at 20:59 UTC
Microsoft Remote Desktop Services expert
102 Best Answers
339 Helpful Votes

terrencet wrote:

DragonsRule​ FWIW, I work in IT but that is not my role.

Understood. Very few of us do everything there is to do in IT :)

The only reason I asked is that your initial wording made it hard to tell if you were in IT at all, or if you were just a computer user having trouble and the people in IT weren't helping you for some reason.
0
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pimiento
OP
terrencet Jun 4, 2020 at 21:06 UTC

DragonsRuleJustin1250that was the issue. I was able to change the subnet mask in my home router settings and was able to resolve the issue. Thank you.

  • We couldnt connect to the remote desktop gateway because of an internal error mac
    DragonsRule
    Pure Capsaicin
  • We couldnt connect to the remote desktop gateway because of an internal error mac
    Justin1250
    Mace
1
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pure Capsaicin
OP
DragonsRule
We couldnt connect to the remote desktop gateway because of an internal error mac
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
Jun 4, 2020 at 21:07 UTC
Microsoft Remote Desktop Services expert
102 Best Answers
339 Helpful Votes

Great! Make sure you make fun of your network admin for not figuring that out :)

0
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pimiento
OP
terrencet Jun 4, 2020 at 21:13 UTC

DragonsRule​ that's fair. I do front end and back end development but not much networking. Fortunately I'm able to work from home.

  • We couldnt connect to the remote desktop gateway because of an internal error mac
    DragonsRule
    Pure Capsaicin
2
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pimiento
OP
terrencet Jun 4, 2020 at 21:21 UTC

lol I'm slacking him right now

2

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

5 Replies

· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Cayenne
OP
Best Answer
Lumpyone
We couldnt connect to the remote desktop gateway because of an internal error mac
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
Jan 30, 2018 at 20:42 UTC

I'm not familiar with RDP Wrapper, so this may not help. However, when you setup your RDP session on the Mac, are you using your static IP address for your Gateway or for the Computer? I've had users with Macs try to place the RDP server address into the Gateway field and that won't work unless you are running an RDP Gateway.

I hadn't realized, until now, that Windows 10 Home doesn't allow for setting up RDP access. Is there a reason you may not use something like Google's Remote desktop, or Teamviewer, LogMeIn, etc? They would be safer than leaving port 3389 open for RDP on your home system.

1
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pimiento
OP
BobbyinQueens Jan 30, 2018 at 21:54 UTC

Thanks for the reply Lumpyone,

I have a static IP for my computer. For my gateway it's not static, but it rarely changes. Just to be sure I'm setting it up correctly - I have my external IP as my gateway address, and my computer IP as my PC Name.

Thanks for your suggestions. This is the first time I'm attempting to remote in to a home computer from the outside. I just assumed Microsoft Remote Desktop would be the way to og. But is Google Desktop, or the other ones you mentioned, better/easier/more secure?

1
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Jalapeno
OP
freezx Jan 31, 2018 at 04:56 UTC

I think rdp warper is just extend windows pc's remote desktop session host's capablity not a Remote Desktop Gateway.

Remote Desktop Gateway is the Remote Desktop Gateway role installed in windows server.It enables you connect to other remote desktop session host on the same network as Remote Desktop Gateway server through it without expose other remote desktop session host to the public. It doesn't seems you are using it.

You should connect to your windows pc using router public ip as PC Name and add port after it if it's not default port. leave Gateway setting as No gateway.

1
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Pimiento
OP
BobbyinQueens Jan 31, 2018 at 05:17 UTC

Thanks freezx, I'll give it a try. But I just installed Chrome Remote Desktop as #Lumpyone suggested, and it works very well. Thanks!!

1
· · ·
We couldnt connect to the remote desktop gateway because of an internal error mac
Cayenne
OP
Lumpyone
We couldnt connect to the remote desktop gateway because of an internal error mac
This person is a verified professional.
Verify your account to enable IT peers to see that you are a professional.
Jan 31, 2018 at 17:33 UTC

BobbyinQueens wrote:

Thanks freezx, I'll give it a try. But I just installed Chrome Remote Desktop as #Lumpyone suggested, and it works very well. Thanks!!

Glad it worked for you! I use it on my home machine occasionally and yes, I overall it will be more secure. If you don't already, I'd highly recommend 2 factor authentication on your Google account now that you are using Google Remote Desktop. Every extra layer of protection you can provide yourself is good :)

0

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

How to fix Unable to Connect – Error Code 0x3000064 (RDP from macOS)

We couldnt connect to the remote desktop gateway because of an internal error mac

Earlier this week, we received a call from a client stating that they could not longer connect to their Windows device at their office using their personal MacBook. The client was receiving an error message “Unable to Connect” with the error code 0x3000064. This error is related to the latest version of the Windows Remote Desktop application in macOS.

Below is not an exhaustive list of connection errors, it’s just a some things that have tripped me up. If you have a nasty error that you have fixed, feel free to drop me a line, send me some screenshots and the fix, and I’ll add them as well.

Remote Desktop connection not working /can’t connect [Fixed]

We couldnt connect to the remote desktop gateway because of an internal error mac
by Ivan Jenic
Troubleshooting Expert
Passionate about all elements related to Windows and combined with his innate curiosity, Ivan has delved deep into understanding this operating system, with a specialization in drivers and driver troubleshooting. When he's not tackling... Read more
Affiliate Disclosure
  • Remote Desktop is a very useful feature, which allows us to control our computer from another device.
  • Some factors can cause Remote Desktop to stop working but read the article below to find plenty of solutions.
  • We wrote a lot more about Remote Desktop Connection so it would be useful for you to bookmark the page.
  • If you experienced any other Windows 10 errors you have to check out our Windows 10 errors hub.
We couldnt connect to the remote desktop gateway because of an internal error mac

Remote Desktop is a very useful Windows 10 feature, which allows us to control our computer from another device.

Of course, it requires an internet connection to work, so if your computer is not properly connected to the internet, you won’t be able to use this feature.

However, even some other factors could cause Remote Desktop to stop working, and we’re going to talk about these issues and solutions for them in this article.

Speaking of issues, many users reported the following problems:

  • Remote Desktop can’t connect to the remote computer for one of these reasons Windows 10
    • Sometimes you might get this error message on your PC. If you encounter this problem, be sure to try all the solutions from this article.
  • Windows 10 RDP client not working
    • Sometimes RDP client won’t work at all on your PC. This can be due to your system configuration. To fix that, make sure that you’re using a private network.
  • RDP this computer can’t connect to the remote computer
    • This is another common problem with RDP. To fix this issue, be sure to check both your antivirus and firewall.
  • Remote Desktop not working after Windows 10 upgrade
    • Sometimes issues with Remote Desktop can occur after installing a Windows update. To fix the issue, simply remove the update and the problem will be fixed.
  • Unable to connect to remote PC, please verify Remote Desktop is enabled
    • This is another common problem with Remote Desktop. However, you should be able to fix the problem using one of our solutions.
  • Windows 10 Remote Desktop credentials did not work
    • If you encounter this error on your PC, you might be able to fix it simply by removing your saved credentials.
  • Remote Desktop cannot connect error, certificate expired invalid, in the time allotted
    • There are various errors that can appear while trying to use the Remote Desktop feature. However, you should be able to fix them using one of our solutions.
  • Remote Desktop won’t connect over the Internet
    • This is another problem related to the Remote Desktop feature. If Remote Desktop can’t connect, be sure to check your firewall and antivirus settings.

The remote desktop can’t connect to the remote computer for one of these reasons:

  • Remote access to the server is not enabled
  • The remote computer is turned off
  • The remote computer is not available on the network

These can be caused by a limited network connection, not enough memory, and wrong firewall settings.

So, if you can’t connect to Remote Desktop in Windows 10, make sure your computer doesn’t have any of the above-mentioned issues.