An error occurred while communicating with the Remote Desktop Gateway

An error occurred while communicating with the Remote Desktop Gateway

4 ngày trước
  • Windows
    • Windows 10
    • Active Directory
    • PowerShell
    • Sysprep
    • Windows Server
  • Hardware
    • Hard Drives
    • Printers
    • Routers
  • Mobile
    • Android
    • iPhone
    • iOS
  • Office
    • Outlook
    • Office 365
  • Drivers
  • Browsers
  • Reviews
  • Others
    • Adobe
    • Internet
    • Linux
    • ConfigMgr
    • CRM
    • Browsers
    • Gmail
    • VMWare
    • SQL
Type your search query and hit enter:
All Rights ReservedView Non-AMP Version
Type your search query and hit enter:
  • About the Authors
  • Contact Us
  • Homepage
  • Windows Featured
Miscellaneous

Getting Error Code: 0x3000069

Archived Forums
>
Remote Desktop clients
  • Question

  • 0
    Sign in to vote

    Hi All,

    Seems for some reason that any users we have using a Mac OS Device no longer can connect to Windows RDS remotely. On the internal corporate wifi they work fine. But once there out of the office they get the following message: An error occurred while communicating with the Remote Desktop Gateway. if this keeps happening, contact your network administrator for assistance. Error Code: 0x3000069.

    There has been no changes to the environment, expect a new public certificate, So not sure if somehow this has changed the security to not allow the mac's device to talk remotely. We have no issues with IOS, Windows or Android devices.

    Both Microsoft and Apple have no answer and lost for options and thought i could try here.

    We have different versions of Mac OS and Remote Desktop client and all get the same error.

    The logs on the Rds show the following:The user "xxxx", on client computer "xxxx", has initiated an outbound connection. This connection may not be authenticated yet. Event ID: 312.

    We are currently running Windows Server 2012 R2 for RDS.

    Thanks kindly


    Monday, December 17, 2018 3:23 AM
  • 0
    Sign in to vote

    Hi Eve,

    We have removed the feed and re added it again. with either the fqdn and ip we still get the same error message. screen shot shows the vent log message as advised. thanks for assisting.


    -

    312
    0
    0
    3
    30
    0x4000000000000000

    227234


    Microsoft-Windows-TerminalServices-Gateway/Operational
    XXXXX.portauthoritynsw.com.au


    -
    -

    172.xx

    .xxx.xx:49807



    Monday, December 17, 2018 10:54 PM
  • 0
    Sign in to vote

    Hi Eve,

    Made the changes but no luck, the Apple Mac devices still get the same error, all other platforms have no issue.

    not sure where to go from here or if i have to look at building out a new RDS on 2019.

    i see that windows devices get this message when they connect from outside: "met connection authorization policy requirements and was therefore authorized to access the RD Gateway server. The authentication method used was: "NTLM" and connection protocol used: "HTTP"." Event ID 200

    thanks kindly

    George



    • Edited by George Tzikas Tuesday, December 18, 2018 7:43 PM
    Tuesday, December 18, 2018 7:31 PM
  • 0
    Sign in to vote

    i see alot of people have had issue with this Error Code: 0x204. still haven't been able to get it going.

    Thursday, January 10, 2019 2:53 AM

Error Trying to Connect to my work Windows PC via RD on my Mac

I have MacOS Catalina and I keep getting error no: 0x300006a. It says: An error occurred while communicating with the remote desktop gateway.

I am able to connect to the remote work servers via a windows laptop, so I know the address and credentials are not the problem. Everyone else from work have been connecting to the work servers fine also but I am the only one with MAC.

My VPN connection is set-up and running. I added a gateway and added a PC. The instructions online have been all straightforward. What is missing? Do I need to do additional configuration on Mac preferences?

Thanks in advance.

remote-desktop-servicesremote-desktop-client
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.

KarlieWeng-MSFT · Feb 01, 2021 at 05:57 AM

Hi @MaryBrit-8761

1.Is the macOS client latest version?
2. With and without gateway selected has the same issue?


3.please check the certificates and firewall ports 443

Best regards
Karlie

0 Votes 0 ·
image.png [45.5 KiB]
MaryBrit-8761 answered Feb 1, '21 | KarlieWeng-MSFT commented Feb 25, '21

Hi @KarlieWeng-MSFT , thank you so much for your reply.

1-My O.S. is Catalina, I haven't upgraded to Big Sur yet because some of the vital softwares I am using have not updated for compatibility. Could that be the issue? Big Sur is fairly new though so it would be odd if that's the case!

2-Without gateway I get the below error.



which seems understandable since I put "pc-2" in the pc name box which is not a full address. If I change it to the vpn server's address, then it gives a different error, which is again understandable since the computer name is not put.

3- I don't have any DNS servers set up on my computer and I don't see a certificate issue either.


screen-shot-2021-02-01-at-115617-am.png [115.5 KiB]
Comment
Comment · Show 3
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.

KarlieWeng-MSFT · Feb 02, 2021 at 01:58 AM

How about the version of remote desktop client?

test whether whether port 443 is open, telnet [domain name or ip] [port]

0 Votes 0 ·
image.png [1.9 KiB]
MaryBrit-8761 KarlieWeng-MSFT · Feb 02, 2021 at 02:43 AM

Remote Desktop is up-to-date. I have a mac so do I type this in the Terminal?

0 Votes 0 ·
KarlieWeng-MSFT MaryBrit-8761 · Feb 25, 2021 at 01:47 AM

this is tested on your MAC

0 Votes 0 ·

Question: Q: An error occurred while communicating with the remote desktop gateway mac

an error occurred while communicating with the remote desktop gateway mac ox300005f


issues facing while taking remote of windows machine from a

mac with help of Microsoft remote desktop

More Less

Posted on Mar 17, 2021 10:38 PM

Reply I have this question too[17] I have this question too Me too[17] Me too

Question: Q: An error occurred while communicating with the Remote Desktop Gateway. If this keeps happening, contact your network administrator for assistance. Error code: 0x300005f

Hello, i am trying to connect to my work PC running Microsoft Windows 7, which is a part of domain server at my office from my Mac OS Mojave. I have downloaded the newest Microsoft Remote Desktop application for Mac. i can connect to the FortiClient but not the RDP - it gives me error code 0x300005f



More Less

iMac 27" 5K, macOS 10.14

Posted on Nov 1, 2019 6:18 AM

Reply I have this question too[270] I have this question too Me too[270] Me too

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.

Video liên quan

Chủ Đề