cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Bug with Mac Remote Desktop 10.9.0, cannot remote in without manually logging in first

Bug with Mac Remote Desktop 10.9.0, cannot remote in without manually logging in first
5

Upvotes

Upvote
 Aug 30 2023
10 Comments (10 New)
New

Now when I try to Remote Desktop into a vm that is on a domain, it will not let me connect because of a security error. This used to connect just fine. The only way to get around this is to manually log in. Once a user has logged into the computer, I can then remote into it like normal. Every time the vm is restarted though, I once again have to manually login to get remote access.

 

The error I receive:

We couldn't connect to the remote PC because of a security error. If this keeps happening, contact your network administrator for assistance. Error code: 0x1807

 

Comment
Comments
wayneataylor
Copper Contributor
‎Sep 19 2023 10:25 AM
‎Sep 19 2023 10:25 AM

I get exactly the same behaviour, did you sort it??

TylerBerry
Copper Contributor
‎Sep 19 2023 01:44 PM
‎Sep 19 2023 01:44 PM

I think it's an issue Microsoft will have to acknowledge and fix. The only workaround I have is finding a previous version of Mac Remote Desktop and going back to 10.8.4

t_tate
Copper Contributor
‎Sep 20 2023 05:44 PM
‎Sep 20 2023 05:44 PM

Please le me know download of 10.8.4.
And, I have same issue 10.9.2 and 10.9.3beta.

I found URL of download for some beta.

https://install.appcenter.ms/orgs/rdmacios-k2vy/apps/microsoft-remote-desktop-for-mac/distribution_g...

jikuja
Brass Contributor
‎Oct 20 2023 06:44 AM
‎Oct 20 2023 06:44 AM

I have same issue even I have turned on NLA on server-side

* NLA turned OFF

* First RDP login attempt fails

* After logging in locally once, RDP works.

 

This issue started after summer, maybe even when the client was updated to 1.9.x

 

Does MSFT have any better feedback channels for bug reports?

Help => Submit feedback open this forum but for me it looks like MSFT does not monitor messages sent here.

 

I can send more information and log files if requested

jikuja
Brass Contributor
‎Oct 24 2023 11:39 AM
‎Oct 24 2023 11:39 AM

Update for support:

 

Environment:

"Server":

* Windown 10 Pro, 22H2: [Version 10.0.19045.3570]

* On same LAN segment than client

 

Client:

* OS X 13.6 (22G120)

* Microsoft Remote Desktop: Version 10.9.3 (2158) and Version 10.9.4 (2161)

* Support ID: D1D8E640-1610-4BB5-9EBB-801576816CA9

 

 

The error dialog on first RDP login after server reboot:

jikuja_0-1698172244959.png

 

After logging in once on "Server" RDP connection works.

jikuja
Brass Contributor
‎Oct 31 2023 01:41 AM
‎Oct 31 2023 01:41 AM

Support on Twitter escalated this internally but looks like nobody bothers to write here or update status of the thread.

TylerBerry
Copper Contributor
‎Oct 31 2023 09:18 AM
‎Oct 31 2023 09:18 AM

Microsoft doesn't seem to make it easy to report or escalate issues. Maybe that's their way of prioritizing what to work on. This seems like such an obvious issue I don't know how the team who develops the mac client didn't run into this right away. This seems to be an issue if you use a newer version of mac remote desktop to connect.

 

Not much to be done from our end until they decide to fix it. Only workaround I know is to use an older version of the client before 10.9.0.

mmillerjdx
Copper Contributor
‎Nov 25 2023 02:39 AM
‎Nov 25 2023 02:39 AM

This is happening to me as well. How in the world was this not caught in testing?

jikuja
Brass Contributor
‎Nov 25 2023 04:03 AM
‎Nov 25 2023 04:03 AM

> How in the world was this not caught in testing?

 

And bigger question is why there iss no zero feedback from the team if issue iss being worked with or not.

JPG_master
Copper Contributor
‎Feb 06 2024 01:08 AM
‎Feb 06 2024 01:08 AM

Hi,

 

I was successful by turning of IPv6 on the remote client.

I found this hint somewhere else and IT WORKED IMMEDIATLEY.

 

I was able to connect to that R-PC with a local ADMIN, BUT NOT WITH a DOMAIN Admin.

ONCE after removing the PC from the Domain and re-itroduce to domain, the DOMAIN Admin loging worked.

Hours later it failed until I turned off IPv6 ... very strange and silly behaviour.

Similar Ideas
No similar ideas