none
RDP from Mac to Win7 fails RRS feed

  • General discussion

  • Hello all,

    I'm having another Mac to PC compatibility issue - this time between the Remote Desktop Connection 2.0 client on MacOS X 10.5.6 to the Windows 7 machine.  On the Windows side, the event viewer says:

    Event 50, TermDD
    The RDP protocol component MCS detected an error in the protocol stream and has disconnected the client.

    I've tried changing settings in the Remote tab in System between 'Allow connections from computers running any version of Remote Desktop (less secure)' and 'Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)'.  This happens under both 32bit and 64bit Win7.

    Thanks!

    -- Brielle Bruns
    Wednesday, January 14, 2009 3:00 AM

All replies

  • I have the same problem:

    OSX 10.4.11 RDC 2.0.0 -> Windows7 64bit

    Setting 'Allow connections from computers running any version of Remote Desktop (less secure)' doesn't resolv the problem, but let me successfully use RDC 1.0.3.

     

    Sunday, February 8, 2009 5:56 PM
  • I don't (for hopefully obvious reasons) have a way to reproduce this issue, but I will check our bug DB when I get back in the office tomorrow and see if this has already been reported.

    More news when I have it, thanks for this feedback folks.
    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team
    Sunday, February 8, 2009 8:32 PM
  • Thank you Ned! 

    This is one of those show stoppers for me - I ended up having to put VNC on the desktop which isn't exactly a viable solution due to the lack of spiffy RDP specific features (like remote printers).

    -- Brielle Bruns
    Sunday, February 8, 2009 8:40 PM
  • Hi guys,

    in both of your cases, are you running PowerPC Mac's, or do you both have x86/x64 processors? I've found this bug being filed a few times, but the only reported repros were when the Mac's were PowerPC.

    Thanks,
    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team
    Monday, February 9, 2009 7:50 PM
  • The machines in question are both G4 PowerPC systems (one a 12in 1.5ghz Powerbook G4, the other a PowerMac G4 dual 1.25ghz MDD).  I'll try it from my partner's Macbook Pro tonight.  Thanks for looking into this for us, Ned!


    Brielle

    -- Brielle Bruns
    • Edited by Brielle Jillian Monday, February 9, 2009 7:54 PM Fixing slight error
    Monday, February 9, 2009 7:53 PM
  • Cool. We're working on a repro here. More news on workarounds or otherwise when I have some.
    Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team
    Monday, February 9, 2009 9:26 PM
  • Same problem here, hoping for a fix soon :)
    Thursday, February 26, 2009 11:29 AM
  • Still nothing?
    Monday, March 9, 2009 1:41 PM
  • Bump
    Monday, March 16, 2009 10:08 AM
  • Hi Ned,

    I am using Mac OS X 10.5.6 on a PowerMac G4 Dual 1GHz (QuickSilver) -> Windows XP SP3.
    I see the same event log error on my PC when connecting with RDC 2.0 on this Mac.

    Procedure:
    On the PC, create a reverse SSH tunnel to your Mac. I use PuTTY, redirecting my remote Mac's port 23389 to 127.0.0.1:3389 on the PC. Enable "Local ports accept connections from other hosts" and "Remote ports do the same (SSH-2 only)" in PuTTY.

    Using PuTTY on the PC, log into the Mac.

    Run RDC 2.0 on the Mac. Enter 127.0.0.1:23389. The windows login screen appears, I can enter my username and password. If entered incorrectly, an error is properly displayed. But, when entered correctly, the windows login box remains on screen, and the session goes unresponsive until a cannot connect dialog is displayed on the Mac.

    Regessions:
    However, when I create a tunnel using Cisco VPN or Gator VPN (with no ssh tunnel), this problem does not exist.

    When I use RDC 1.0.3 over the reverse SSH tunnel, the same problem exists, in this case no error dialog appears on the Mac, rather RDC on the Mac quits without any error message.

    Please let us know the status of this issue.

    Thank you for your time,
    --Mike


    Event Log Error Information:
    The RDP protocol component MCS detected an error in the protocol stream and has disconnected the client.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    0000: 00 00 06 00 02 00 54 00   ......T.
    0008: 00 00 00 00 32 00 0a c0   ....2..À
    0010: 00 00 00 00 32 00 0a c0   ....2..À
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........
    0028: 68 00 00 00 80 21         h...€! 
    Wednesday, April 8, 2009 12:48 PM
  • I have this same issue with Server 2008 and MacOS X 10.5.6.  This issue seems to happen randomly.  We are using the Cisco VPN client and RDC 2.0 on a MacBook Pro.  Any updates would be great.
    Wednesday, May 6, 2009 7:51 PM
  • The issue still persists in the new RDC Version 2.0.1 for me as well.  PPC Mac > Windows 7 always kicks me off as soon as I hit any key on the keyboard.
    Friday, September 4, 2009 9:11 PM
  • Try TSclientX instead, it uses the RDP protocol as opposed to sluggish VNC.  That's what I've been using for the time being, and it's working great.


    http://desktopecho.com/tsclientx/
    Friday, September 4, 2009 9:13 PM
  • Hi,

    I'm having exactly the same problem here with an Intel-based MacBook Pro. Running RDC 2.01 and Snow Leopard (10.6.1).
    Saturday, September 12, 2009 7:36 PM
  • Exactly the same here as well with the latest intel macbook pro running RDC 2.01 and Snow Leopard.
    Tuesday, September 15, 2009 5:14 PM
  • I had the same problem with a ppc-based Mac computer with OS X 10.4. The remote desktop connection from this computer to a Windows 2008 server could be established, but it disconnected as soon as any key was hit. After a long research I found a solution: A Java-based remote desktop client  is working well on PPC-based computers (and other OS as well). You may download the Java-Jar file from http://www.elusiva.com/opensource/. It needs Java 1.1 runtime environment (or later) on your machine and can be integrated in a script file. The program call will look like:

    java -jar JavaRDP14-1.1.jar -T YourWindowTitle -d YourDomain -u YourUsername -g YourWindowSize -m YourKeyboardMapping YourServerName

    Saturday, November 27, 2010 12:00 PM
  • I'm having a similar issue.  But a different error.

    I've got a Mac user that we're trying to set up an SSL-VPN connection for.  I've installed the Microsoft Remote Desktop Connection for Mac version 2.1.0 on her machine.  

    While physically connected to the network, I try to connect to a Windows XP machine and it works just fine.  However, when I try to connect to her Windows 7 machine, it comes back with the following error:

    "Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.  Try reconnecting to the Windows-based computer, or contact our administrator."

    Everything on the RDC preferences is set at its default.  Under the Security tab, it is set to "Warn me if authentication fails."

    On the Windows 7 machine, the user is in the Remote Desktop Users group.  The machine's remote desktop settings are configured for "Allow connections from computers running any version of Remote Desktop (less secure)" via group policy.  

    Can anyone tell me what I'm missing here?  This is happening regardless if I'm using standard user creds or domain administrator creds.

    The user is using OS X version 10.6.6 on an Intel Core2Duo Macbook.

     

    Tuesday, March 15, 2011 2:57 PM
  • Found the problem.  Apparently Macs don't like having the domain name in the domain field.  Took that out and it's working fine now.
    Tuesday, March 15, 2011 8:50 PM
  • The issue still persists in the new RDC Version 2.0.1 for me as well.  PPC Mac > Windows 7 always kicks me off as soon as I hit any key on the keyboard.

    Two years later, still having the exact same problem (as EXrider), and no would-be RDC v2.0.2 (only v2.1, which is for 10.5 and up and totally rocks, but this machine is an old G4; so, not worth investing money in an OS upgrade from 10.4).  Tried RDC v1.0.3, which totally works, but kinda sluggish (yes, like VNC); and, I didn't try your tsclientx suggestion below, because it needs X11 and doesn't have a good showing on download.com.

    Also, U Silicara, nice find on the open source java based RDC.  Note to people who are reading this: could only find v1.4 on http://www.elusiva.com/opensource, but this will give you an error: "Wrong modulus size! Expected64+8got:264" when connecting to a Windows 7 machine; so, you might want to risk downloading the v1.6 version from here (but this was a blind download on my part), which doesn't throw you that error, but gives you another error: "Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file", which makes sense because 10.4 only has Java 1.5; i.e. this would work for 10.5 and up (and thinking you even need intel for v1.6), but that's moot because you would just use RDC v2.1, agh!  Another drawback (if you could get it to work for 10.4), is that it shows keystrokes in the Terminal window; i.e. it would show your password or anything else you typed (not that you couldn't "history -c" or just close the Terminal windows when done).

    A little verbose; so, the bottom line: if you have 10.4 and want to connect to a Windows 7 machine, just use the old RDC v1.0.3.

     


    "All things are possible, but not all things are permissible"








    Friday, June 17, 2011 4:51 PM
  • Found the problem.  Apparently Macs don't like having the domain name in the domain field.  Took that out and it's working fine now.
    Thank you. That was all I needed to change. Been bugging me for weeks.
    Dave Tschoepe Beenanza, LLC
    Wednesday, November 16, 2011 8:05 PM
  • Found the problem.  Apparently Macs don't like having the domain name in the domain field.  Took that out and it's working fine now.

    Thanks a lot!

    This solved for me.

    Sunday, March 18, 2012 8:39 AM