- Edited by Meshah81 Friday, August 28, 2015 4:08 PM
Same here, can't connect with .19! And I checked that i can connect via other means.
I am connecting through a remote connection gateway. But was able to do it just fine until .19 came along. Now upon connection all i see is a WHITE screen and nothing else. (Yeah I would like to het .18 back for the moment).
Thats for starting it in full screen. When I start without fullscreen enabled, the connection window appears and immediately closes.
Can you please advise?
- Edited by Vitalijs Krjacko Saturday, August 29, 2015 9:24 PM more info
Same problem here! Since 8.0.19 can't connect anymore to my Windows machine....
Try to connect from Mac OS X 10.11 beta to Windows 10.
- Edited by PeteLes Sunday, August 30, 2015 1:44 AM
Hallo.
Same issue here.
The Microsoft Remote Desktop BETA solved the Problem for me.
http://go.microsoft.com/fwlink/?LinkID=619698&clcid=0x409
- Proposed as answer by sietecFAST Enterprise Technologies, Inc Saturday, September 05, 2015 12:31 PM
I faced the same issue "connection reset by peer" with ver .19
Using Windows rdp clients works normally.
The only way I resolve this is to change the server connection security down from SSL to RDP Security Layer. I was using self-signed cert.
- Edited by Jonn N Tuesday, September 01, 2015 6:18 AM
Hello Brad,
Features in the beta will be added over time. Visit our UserVoice forum to vote or suggest for features that you would like to see in the beta earlier: aka.ms/uservoice-rdmac
Do not forget to set the category to beta.
- Proposed as answer by Eva SeydlMicrosoft employee, Moderator Friday, September 04, 2015 4:58 PM
Same for me. I was connecting fine until the first of September when I upgraded to .19. Can still use the client on my iPhone from the same network.
Problem config:
iMac running MRD v8.0.19 connecting over VPN to Windows 8 machine.
Worked with previous Mac client.
Still works with iPhone client.
Resolved by using feature-poor beta.
Same issue, Remote Desktop App for MAC Version 8.0.19 (Build 26665) - Broken/a Bug. Windows Home Server no longer accessible.
Windows 7 Systems work fine. Here is an excerpt of the LOG FILE:
NOTE: Just like other users I was able to do a workaround by using: A) An Old Version of MS RDP, and by downloading the new "BETA" version of MS RDP. Fact remains, MS broke something in the 8.0.19 release. I just can't be arsed to go looking for it in detail. An annoyance, as usual.
[2015-Sep-12 00:28:46] RDP (0): Resolved '192.168.1.110' to '192.168.1.110' using NameResolveMethod_DNS(1) [2015-Sep-12 00:28:46] RDP (0): Exception caught: Exception in file '../../librdpclient/asiosocketendpoint.cpp' at line 380 User Message : Connection reset by peer [2015-Sep-12 00:28:46] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1) [2015-Sep-12 00:28:46] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2) [2015-Sep-12 00:28:46] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3) [2015-Sep-12 00:28:46] RDP (0): Protocol state changed to: ProtocolDisconnecting(7) [2015-Sep-12 00:28:46] RDP (0): Protocol state changed to: ProtocolDisconnected(8) [2015-Sep-12 00:28:46] RDP (0): ------ END ACTIVE CONNECTION ------ [2015-Sep-12 00:33:54] RDP (0): *** Application terminated ***