locked
Remote Desktop Client for Mac 8.0.32 - Connection Fails with Local External Display RRS feed

  • Question

  • Hi There, 

    I recently updated Remote Desktop client to 8.0.32 and since then I am not able to use the client if i have my external display connected on my local machine. Works fine if I detach it and just run it on my MPB screen.

    I have 2010 15inch MBP and am using a 23 inch Apple Cinema Display.

    Previous versions of the Remote Desktop Client worked fine on either screen and i could move the session between them no problems.

    Below are log extracts from a successful connection without the Cinema Display connected and then an unsuccessful connection attempt made with the Cinema Display connected.

    It appears from the log, that the connection is being terminated by the remote server.. why would this happen just because i have an external display connected on my local machine, and why only since updating the client to 8.0.32?

    ****************************

    [2016-Jul-07 13:44:26] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2016-Jul-07 13:44:28] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2016-Jul-07 13:44:29] RDP (0): Client requests RAIL
    [2016-Jul-07 13:44:29] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2016-Jul-07 13:44:29] RDP (0): Server supports RAIL
    [2016-Jul-07 13:44:30] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2016-Jul-07 13:44:32] RDP (0): Server hides cursor
    [2016-Jul-07 13:44:32] RDP (0): Server shows cursor
    [2016-Jul-07 13:44:43] RDP (0): HeartBeat: connection monitoring started
    [2016-Jul-07 13:44:46] RDP (0): Server hides cursor
    [2016-Jul-07 13:44:48] RDP (0): Server shows cursor
    [2016-Jul-07 13:44:50] RDP (0): Server hides cursor
    [2016-Jul-07 13:44:50] RDP (0): Server shows cursor
    [2016-Jul-07 13:44:50] RDP (0): Server hides cursor
    [2016-Jul-07 13:44:50] RDP (0): Server shows cursor
    [2016-Jul-07 13:44:56] RDP (0): Server hides cursor
    [2016-Jul-07 13:44:56] RDP (0): Server shows cursor
    [2016-Jul-07 13:45:01] RDP (0): *** Application terminated ***

    ****************************

    [2016-Jul-07 13:41:28] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)
    [2016-Jul-07 13:41:30] RDP (0): Protocol state changed to: ProtocolConnectingRDP(3)
    [2016-Jul-07 13:41:30] RDP (0): Client requests RAIL
    [2016-Jul-07 13:41:30] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2016-Jul-07 13:41:31] RDP (0): Server supports RAIL
    [2016-Jul-07 13:41:31] RDP (0): Protocol state changed to: ProtocolActive(5)
    [2016-Jul-07 13:41:34] RDP (0): HeartBeat: connection monitoring started
    [2016-Jul-07 13:43:33] RDP (0): Disconnect initiated by server
    [2016-Jul-07 13:43:33] RDP (0): Protocol state changed to: ProtocolInactive(4)
    [2016-Jul-07 13:43:33] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
    [2016-Jul-07 13:43:38] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2016-Jul-07 13:43:38] RDP (0): ------ END ACTIVE CONNECTION ------
    [2016-Jul-07 13:43:44] RDP (0): *** Application terminated ***

    Any help would be appreciated.

    Thanks, Mike

     
    Thursday, July 7, 2016 4:09 AM

Answers

  • Hi,

    I suggest you check terminal services related logs on remote system to see whether disconnect reason can be found, which are under:

    Event Viewer -> Applications and Services Logs\ Microsoft\ Windows.

    Best Regards,

    Amy


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Edited by Amy Wang_ Friday, July 8, 2016 12:13 PM
    • Proposed as answer by Amy Wang_ Wednesday, July 13, 2016 5:47 AM
    • Marked as answer by Amy Wang_ Wednesday, July 20, 2016 8:00 AM
    Friday, July 8, 2016 12:13 PM