Just updated to Version 8.0.13 (Build 25377) and now receive the following message

" Failed to establish RDG/HTTPS out channel"

Was fine prior to update

Any ideas ?

Running OSX 10.10.2

Just updated to Version 8.0.13 (Build 25377) and now receive the following message

" Failed to establish RDG/HTTPS out channel"

Was fine prior to update

Any ideas ?

Running OSX 10.10.2

Same problem here. Upgraded to version 8.0.13 (Build 25377). 

Hello,

same for me:

• OSX 10.10.2
• updated from Microsoft Remote Desktop 8.0.12 to 
• Version 8.0.13 (Build 25377)

Any attempt to connect to one of the remote servers fails with message:

"Unable to connect to remote PC. Please verify Remote Desktop is enabled... and try again"

Error Log:

[2015-Feb-05 15:41:57] RDP (0): --- BEGIN INTERFACE LIST ---
[2015-Feb-05 15:41:57] RDP (0): lo0 af=18  addr= netmask=
[2015-Feb-05 15:41:57] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2015-Feb-05 15:41:57] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0
[2015-Feb-05 15:41:57] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2015-Feb-05 15:41:57] RDP (0): gif0 af=18  addr= netmask=
[2015-Feb-05 15:41:57] RDP (0): stf0 af=18  addr= netmask=
[2015-Feb-05 15:41:57] RDP (0): en0 af=18  addr= netmask=
[2015-Feb-05 15:41:57] RDP (0): en0 af=30 (AF_INET6)  addr=fe80::225:4bff:fed6:5712%en0 netmask=ffff:ffff:ffff:ffff::
[2015-Feb-05 15:41:57] RDP (0): en0 af=2 (AF_INET)  addr=10.20.0.15 netmask=255.255.0.0
[2015-Feb-05 15:41:57] RDP (0): en1 af=18  addr= netmask=
[2015-Feb-05 15:41:57] RDP (0): fw0 af=18  addr= netmask=
[2015-Feb-05 15:41:57] RDP (0): p2p0 af=18  addr= netmask=
[2015-Feb-05 15:41:57] RDP (0): --- END INTERFACE LIST ---
[2015-Feb-05 15:41:57] RDP (0): correlation id: 37b0124f-30d7-640b-10c7-c73a0b730000
[2015-Feb-05 15:41:57] RDP (0): Resolved '10.10.0.03' to '10.10.0.03' using NameResolveMethod_DNS(1)
[2015-Feb-05 15:41:57] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2015-Feb-05 15:42:05] RDP (0): Exception caught: Exception in file '../../librdpclient/asiosocketendpoint.cpp' at line 558
    User Message : Unable to connect to remote PC. Please verify Remote Desktop is enabled, the remote PC is turned on and available on the network, and then try again.
[2015-Feb-05 15:42:05] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
[2015-Feb-05 15:42:05] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2015-Feb-05 15:42:05] RDP (0): ------ END ACTIVE CONNECTION ------

Remote Servers are WinServer 2003/2008/2012, connecting account is administrative (worked perfectly until version 8.0.12).

DNS and routing flawless and everything worked perfectly yesterday before this update.

Since this is for administrative work, it's a serious problem for me.

If anyone could recommend an alternative for the meantime this gets hopefully fixed, this would also help. "Remote Desktop Connection for Mac 2.1.1" is not a n alternative, as just verified.

Best

kent

Try CoRD.  http://cord.sourceforge.net/

I am having the same issue.  I depend on connecting to work servers from my home Mac when on call.  This is not good.  Microsoft.  Do you have any updates or recomendations?

Hello,

thanks a lot for this very nice find, looks very promising. Didn't know it and will check it next days how it handles in daily use. Would meet my preference for open source software and since it seems to do all i need i would switch then.

Even works on 10.10.2, although reports had been sceptical...

Back and fixed:

I checked the behaviour under a different account (fresh, never used) and found it operable - with the very same configuration/constellation as the other account.

Switched back to problematic account, removed all preferences, which did NOT help.

Erased the entire container, rebooted and reinstalled from Appstore and now it works flawless.

BUT: strange still: still encounter the same previous error:

[2015-Feb-05 20:05:27] RDP (0): --- BEGIN INTERFACE LIST ---
[2015-Feb-05 20:05:27] RDP (0): lo0 af=18  addr= netmask=
[2015-Feb-05 20:05:27] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
[2015-Feb-05 20:05:27] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0
[2015-Feb-05 20:05:27] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
[2015-Feb-05 20:05:27] RDP (0): gif0 af=18  addr= netmask=
[2015-Feb-05 20:05:27] RDP (0): stf0 af=18  addr= netmask=
[2015-Feb-05 20:05:27] RDP (0): en0 af=18  addr= netmask=
[2015-Feb-05 20:05:27] RDP (0): en0 af=2 (AF_INET)  addr=10.20.0.15 netmask=255.255.0.0
[2015-Feb-05 20:05:27] RDP (0): en1 af=18  addr= netmask=
[2015-Feb-05 20:05:27] RDP (0): fw0 af=18  addr= netmask=
[2015-Feb-05 20:05:27] RDP (0): p2p0 af=18  addr= netmask=
[2015-Feb-05 20:05:27] RDP (0): --- END INTERFACE LIST ---
[2015-Feb-05 20:05:27] RDP (0): correlation id: ae4d1952-1c1c-5167-8607-13300e320000
[2015-Feb-05 20:05:27] RDP (0): Resolved '10.10.0.03' to '10.10.0.03' using NameResolveMethod_DNS(1)
[2015-Feb-05 20:05:27] RDP (0): Exception caught: Exception in file '../../librdp/itotlayer.cpp' at line 875
    User Message : Security negotiation Error: NotAllowed(2)
[2015-Feb-05 20:05:27] RDP (0): correlation id: ae4d1952-1c1c-5167-8607-13300e320000
[2015-Feb-05 20:05:27] RDP (0): Resolved '10.10.0.03' to '10.10.0.03' using NameResolveMethod_DNS(1)
[2015-Feb-05 20:05:27] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2015-Feb-05 20:05:27] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2015-Feb-05 20:05:27] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
[2015-Feb-05 20:05:27] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
[2015-Feb-05 20:05:29] RDP (0): **** User ACCEPTED connection to basic security host
[2015-Feb-05 20:05:29] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
[2015-Feb-05 20:05:29] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2015-Feb-05 20:05:29] RDP (0): Protocol state changed to: ProtocolActive(5)
[2015-Feb-05 20:05:29] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2015-Feb-05 20:05:29] RDP (0): Protocol state changed to: ProtocolActive(5)
[2015-Feb-05 20:05:47] RDP (0): Disconnect initiated by server
[2015-Feb-05 20:05:47] RDP (0): Protocol state changed to: ProtocolInactive(4)
[2015-Feb-05 20:05:47] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
[2015-Feb-05 20:05:52] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
[2015-Feb-05 20:05:52] RDP (0): ------ END ACTIVE CONNECTION ------
[2015-Feb-05 20:06:00] RDP (0): *** Application terminated ***

Thus no clue what finally has been the problem...

Best, kent

 

bb2bb, CoRD looks good but unless I have missed something it works for RDP but not for RDS ?

Kent, will try what you have done and report back

cheers all

Paul

Nope, full/complete removal, download & reconfigure - same result.

Schmitty1970  - I run Windows on my MAC via 'Parallels' on which I have a Remote Desktop Connection. This works very well and has proved useful in many situations like this. Its cheap too.

http://www.parallels.com/uk/products/desktop/

 

Uninstalled again, downloaded a previous version care of the Link from post by wvdpost Unable to connect after update to 8.0.13 and all back to normal.

thank you

• Edited by A_name_that_is_not_taken Thursday, February 05, 2015 9:32 PM

Uninstalled again, downloaded a previous version care of the Link from post by wvdpost Unable to connect after update to 8.0.13 and all back to normal.

thank you

• Edited by A_name_that_is_not_taken Thursday, February 05, 2015 9:32 PM

Same...

Every time I install a new version this thing breaks. Do they even test it?

I think they don't even open it.  They misspelled Yosemite as "Yosemity" on the previous update, and that's the first thing seen when you run the app the first time.

can you give me the link to previous version. Searched for the post title that you have written but was unable to find it.

I am stuck with this new version . I guess shouldn't have upgraded. Why can't they at least give links to prior 2 versions.

If you have a Time Machine backup you can restore the previous version from there.

I don't have the backup unfortunately. So getting an external link is my only chance.

The same problem here!!

• Proposed as answer by M.Derkaoui 2 hours 3 minutes ago

  +1  

I also have the same problem! Can anyone please post a link with a previous version

• Edited by M.Derkaoui 20 hours 48 minutes ago
• Proposed as answer by M.Derkaoui 2 hours 4 minutes ago

Did you solve the issue? I have the same problem and need to connect in order to work.

• Proposed as answer by M.Derkaoui 13 hours 48 minutes ago

can you share the link to the previous version please?

When looking in the Remote Gateway server i get the following messages:

An account failed to log on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0

Logon Type: 3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: <Gateway/ Broker Servername>
Account Domain: IT2ASP

Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064

Process Information:
Caller Process ID: 0x0
Caller Process Name: -

Network Information:
Workstation Name: <Gateway/ Broker Servername>
Source Network Address: IPV6 ADRESS
Source Port: 55804

Detailed Authentication Information:
Logon Process: NtLmSsp 
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

• Edited by Ferdi_Lankhaar 19 hours 4 minutes ago

The same problem here!!

• Proposed as answer by M.Derkaoui Tuesday, February 10, 2015 9:21 AM

I also have the same problem! Can anyone please post a link with a previous version

• Edited by M.Derkaoui Monday, February 09, 2015 2:36 PM
• Proposed as answer by M.Derkaoui Tuesday, February 10, 2015 9:20 AM

Did you solve the issue? I have the same problem and need to connect in order to work.

• Proposed as answer by M.Derkaoui Monday, February 09, 2015 9:36 PM

When looking in the Remote Gateway server i get the following messages:

An account failed to log on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0

Logon Type: 3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: <Gateway/ Broker Servername>
Account Domain: IT2ASP

Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064

Process Information:
Caller Process ID: 0x0
Caller Process Name: -

Network Information:
Workstation Name: <Gateway/ Broker Servername>
Source Network Address: IPV6 ADRESS
Source Port: 55804

Detailed Authentication Information:
Logon Process: NtLmSsp 
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

• Edited by Ferdi_Lankhaar Monday, February 09, 2015 4:20 PM

All,

I have uploaded app version 8.0.12 to my website.  it can be downloaded from here;

http://www.mark-poulton.co.uk/MSRemote8012/

I'm not 100% sure I've uploaded it correctly, but give it a try and let me know..

• Proposed as answer by Ryu21 1 hour 58 minutes ago

The same problem here!!

Hello everyone I have arranged a lower version of Microsoft Remote Desktop  8.0.10 .

Send me your email en I will send it...

Greetz,

MD

• Edited by M.Derkaoui 1 hour 58 minutes ago

Hello everyone I have arranged a lower version of Microsoft Remote Desktop  8.0.10 .

Send me your email en I will send it...

Greetz,

MD

All,

I have uploaded app version 8.0.12 to my website.  it can be downloaded from here;

http://www.mark-poulton.co.uk/MSRemote8012/

I'm not 100% sure I've uploaded it correctly, but give it a try and let me know..

Can you create a ZIP file cannot download it this way, it shows appache index.

All,

I have uploaded app version 8.0.12 to my website.  it can be downloaded from here;

http://www.mark-poulton.co.uk/MSRemote8012/

I'm not 100% sure I've uploaded it correctly, but give it a try and let me know..

• Proposed as answer by Ryu21 Tuesday, February 10, 2015 9:26 AM

The same problem here!!

Hello everyone I have arranged a lower version of Microsoft Remote Desktop  8.0.10 .

Send me your email en I will send it...

Greetz,

MD

• Edited by M.Derkaoui Tuesday, February 10, 2015 9:26 AM

Yes, please make a zip version I'm not able to download it as well.

I don't see an option here to send you a pm

I would also like a copy , is there any way you could share again ?

this one seems for power pc .

I've just uploaded it in a zip file..   Give that a try.

There's now a zip file at;

http://www.mark-poulton.co.uk/MSRemote8012/

give it a try..

Try downloading the zip file from here;

http://www.mark-poulton.co.uk/MSRemote8012/

Thank you this helps, at least my clients can login this way.

By the way you do know you can edit a post?

thank you ,

this one works for me. lifesaver !

Thanks Ryu21. I got it working again. You made my day!

I had the same problem. I was able to solve it using an earlier version of RDC. I found it on this link
https://social.technet.microsoft.com/Forums/windowsserver/en-US/aef18b12-7785-46b2-958d-0bbbef78aede/unable-to-connect-after-update-to-8013?forum=winRDc

Best regards,
Alex

Same issue for me.

That's the first use I've had for my Time Machine in 3 years but, damn, it feels good to be a gangster.

Fixed: Reverted back to 8.0.12.  Come on, Microsoft.  What is this, amateur hour?

With 8.0.13, the connection is made to the following address : https://WebSiteName/RemoteDesktopGateway instead of https://WebSiteName/rpc

You must configure a url redirection or translation link on your Web Server. Personally, I Publish my Terminal Server Gateway with Microsoft TMG. I have editing my Web Publihing rule and I add a url translation in 'Link Translation' Tab for https://WebSiteName/RemoteDesktopGateway to https://WebSiteName/rpc . Also I have add 'Access Path' for /RemoteDesktopGateway/* in 'Paths' Tab

The new client only try to connect to SiteWeb/RemoteDesktopGateway instead of SiteWeb/rpc

Now, I am able to connect with 8.0.13 without RDG/HTTPS error



• Proposed as answer by Adm125 Thursday, February 12, 2015 9:57 PM

thanks Patrice1111111

It works for me now

All,

I have uploaded app version 8.0.12 to my website.  it can be downloaded from here;

http://www.mark-poulton.co.uk/MSRemote8012/

I'm not 100% sure I've uploaded it correctly, but give it a try and let me know..

it works. thank you fantastic guy.

Same here. Kind work anymore because I work in a Cloud environment using RDP. This is pretty serious!!! Please fix this yesterday!

We have had the same problem and found a solution.

It looks like 8.0.13 introduced the HTTP protocol instead of RPCHTTP, and the fallback is not working so if your RDG does not support HTTP or is not working it breaks.  The windows RDP8 client successfully falls back to RPCHTTP, but the Mac one doesn't.

In our case the RDG is published by TMG and we had SSL bridging set to HTTPS->HTTPS which appears to break it.  By changing to HTTPS->HTTP on both TMG and RDG it works now.

Hope this helps someone.

nice guide.it works for me.(rdgsrv and tmg)  thx Patrice