Remote Desktop Connection Dropped upon typing.
in [Terminal Services]
|
From: Eric Wood on 27 Oct 2009 17:15 Hello, I have three PowerPC G4 based Workstations running Tiger (10.4.11) and Microsoft Remote Desktop Connection Client for Mac 2.0.1. I can connect and login to an account on the server running Microsoft Server 2008 R2 Enterprise if I save the username and password in the client. Once connected I can use the mouse to start applications and control the machine as needed. If I type (a-z,A-Z,0-9) or press any modifier key I receive the following message and I am dropped. You were disconnected from the Windows-based computer. Someone with access to the Windows-based computer may have ended the connection, or the Windows-based computer has dropped the connection. Try reconnecting to the Windows-based computer, or contact your administrator. Cancel / Reconnect This occurs on any valid account on the server. From the lowliest user to the Domain Administrator. CoRD 0.4.3 (The last version to support Tiger) has been tried. It will not connect to Microsoft Server 2008 R2 Enterprise and upgrading these workstations to Leopard is not an option at this time. I have gutted RDC Client for Mac as best as I know how and installed it fresh. I removed the following: rm -rvf /Users/blahblah/Documents/RDC\ Connections/ rm -rvf /Users/Shared/Microsoft/RDC\ Crucial\ Server\ Information/ The clients without being modified running the Microsoft RDC Client for Mac 2.0.1 can connect to various Microsoft Windows Server 2003 Standard Edition boxes around the organization. I do not have any Microsoft Windows Server 2008 (non-R2) machines to test against. This issue is only affecting my PowerPC based workstations running Tiger or Leopard. All of my Intel based workstations running Tiger or Leopard can connect without issue using the 2.0.0-2.0.1 client version. I fired up tsconfig.msc and looked at the various settings. Nothing was set in an odd manner. I tried lowering encryption requirements and disabling clipboard and other such things. I tried limiting the connections to 15bit, 16bit, 24bit, and 32bit color depth. It made no difference. Still can connect and control with the mouse but if you type you are dropped. I installed a fresh copy of Apple OS X Leopard on a PowerPC based 12" iBook G4. I updated to 10.5.8 and then installed Microsoft RDC Client for Mac 2.0.1. I can control the session with the mouse but I am dropped immediately upon typing. So I am down to blaming Microsoft's PPC version of RDC because the Intel version of RDC works without issue on Tiger or Leopard. The PPC version fails on all machines I have tried using either Tiger or Leopard. I tried 1.X versions of Microsoft RDC Client for Mac for the heck of it. As stated on the www.microsoft.com/mac website they do not support Windows Server 2008. I too experienced the inability to connect to the server at all with the 1.0.3 client on any machine. Eric Wood Technology Assistant MSAD #72 Fryeburg, ME US
From: Claudio Rodrigues on 29 Oct 2009 09:45 Eric Wood wrote: > Hello, > > I have three PowerPC G4 based Workstations running Tiger (10.4.11) and > Microsoft Remote Desktop Connection Client for Mac 2.0.1. > > I can connect and login to an account on the server running Microsoft > Server 2008 R2 Enterprise if I save the username and password in the > client. > > Once connected I can use the mouse to start applications and control the > machine as needed. > > If I type (a-z,A-Z,0-9) or press any modifier key I receive the > following message and I am dropped. > > You were disconnected from the Windows-based computer. > > Someone with access to the Windows-based computer may have ended the > connection, or the Windows-based computer has dropped the connection. > > Try reconnecting to the Windows-based computer, > or contact your administrator. > > Cancel / Reconnect > > This occurs on any valid account on the server. From the lowliest user > to the Domain Administrator. > > CoRD 0.4.3 (The last version to support Tiger) has been tried. It will > not connect to Microsoft Server 2008 R2 Enterprise and upgrading these > workstations to Leopard is not an option at this time. > > I have gutted RDC Client for Mac as best as I know how and installed it > fresh. > > I removed the following: > > rm -rvf /Users/blahblah/Documents/RDC\ Connections/ > > rm -rvf /Users/Shared/Microsoft/RDC\ Crucial\ Server\ Information/ > > > > The clients without being modified running the Microsoft RDC Client for > Mac 2.0.1 can connect to various Microsoft Windows Server 2003 Standard > Edition boxes around the organization. I do not have any Microsoft > Windows Server 2008 (non-R2) machines to test against. > > This issue is only affecting my PowerPC based workstations running Tiger > or Leopard. All of my Intel based workstations running Tiger or Leopard > can connect without issue using the 2.0.0-2.0.1 client version. > > I fired up tsconfig.msc and looked at the various settings. Nothing was > set in an odd manner. I tried lowering encryption requirements and > disabling clipboard and other such things. I tried limiting the > connections to 15bit, 16bit, 24bit, and 32bit color depth. It made no > difference. Still can connect and control with the mouse but if you type > you are dropped. > > I installed a fresh copy of Apple OS X Leopard on a PowerPC based 12" > iBook G4. I updated to 10.5.8 and then installed Microsoft RDC Client > for Mac 2.0.1. I can control the session with the mouse but I am dropped > immediately upon typing. > > So I am down to blaming Microsoft's PPC version of RDC because the Intel > version of RDC works without issue on Tiger or Leopard. The PPC version > fails on all machines I have tried using either Tiger or Leopard. > > I tried 1.X versions of Microsoft RDC Client for Mac for the heck of it. > As stated on the www.microsoft.com/mac website they do not support > Windows Server 2008. I too experienced the inability to connect to the > server at all with the 1.0.3 client on any machine. > > Eric Wood > Technology Assistant > MSAD #72 > Fryeburg, ME > US Hi Eric, I will forward this to some people I know on the TS group in Redmond as it seems like a bug. -- Claudio Rodrigues CEO, WTSLabs Inc. http://www.wtslabs.com "WebTS: TSWeb the way it should have been done since day one" Citrix CTP Provision Networks VIP Make sure you download our free guide about Terminal Services. An A to Z guide, explaining everything, from setting it up to enabling group policies. A must read and again, completely free.
From: Claudio Rodrigues on 30 Oct 2009 16:57 Eric Wood wrote: > Hello, > > I have three PowerPC G4 based Workstations running Tiger (10.4.11) and > Microsoft Remote Desktop Connection Client for Mac 2.0.1. > > I can connect and login to an account on the server running Microsoft > Server 2008 R2 Enterprise if I save the username and password in the > client. > > Once connected I can use the mouse to start applications and control the > machine as needed. > > If I type (a-z,A-Z,0-9) or press any modifier key I receive the > following message and I am dropped. > > You were disconnected from the Windows-based computer. > > Someone with access to the Windows-based computer may have ended the > connection, or the Windows-based computer has dropped the connection. > > Try reconnecting to the Windows-based computer, > or contact your administrator. > > Cancel / Reconnect > > This occurs on any valid account on the server. From the lowliest user > to the Domain Administrator. > > CoRD 0.4.3 (The last version to support Tiger) has been tried. It will > not connect to Microsoft Server 2008 R2 Enterprise and upgrading these > workstations to Leopard is not an option at this time. > > I have gutted RDC Client for Mac as best as I know how and installed it > fresh. > > I removed the following: > > rm -rvf /Users/blahblah/Documents/RDC\ Connections/ > > rm -rvf /Users/Shared/Microsoft/RDC\ Crucial\ Server\ Information/ > > > > The clients without being modified running the Microsoft RDC Client for > Mac 2.0.1 can connect to various Microsoft Windows Server 2003 Standard > Edition boxes around the organization. I do not have any Microsoft > Windows Server 2008 (non-R2) machines to test against. > > This issue is only affecting my PowerPC based workstations running Tiger > or Leopard. All of my Intel based workstations running Tiger or Leopard > can connect without issue using the 2.0.0-2.0.1 client version. > > I fired up tsconfig.msc and looked at the various settings. Nothing was > set in an odd manner. I tried lowering encryption requirements and > disabling clipboard and other such things. I tried limiting the > connections to 15bit, 16bit, 24bit, and 32bit color depth. It made no > difference. Still can connect and control with the mouse but if you type > you are dropped. > > I installed a fresh copy of Apple OS X Leopard on a PowerPC based 12" > iBook G4. I updated to 10.5.8 and then installed Microsoft RDC Client > for Mac 2.0.1. I can control the session with the mouse but I am dropped > immediately upon typing. > > So I am down to blaming Microsoft's PPC version of RDC because the Intel > version of RDC works without issue on Tiger or Leopard. The PPC version > fails on all machines I have tried using either Tiger or Leopard. > > I tried 1.X versions of Microsoft RDC Client for Mac for the heck of it. > As stated on the www.microsoft.com/mac website they do not support > Windows Server 2008. I too experienced the inability to connect to the > server at all with the 1.0.3 client on any machine. > > Eric Wood > Technology Assistant > MSAD #72 > Fryeburg, ME > US Just to let you know the Mac group at Microsoft is now looking into the issue. Just got an email from someone at the TS group in Redmond. -- Claudio Rodrigues CEO, WTSLabs Inc. http://www.wtslabs.com "WebTS: TSWeb the way it should have been done since day one" Citrix CTP Provision Networks VIP Make sure you download our free guide about Terminal Services. An A to Z guide, explaining everything, from setting it up to enabling group policies. A must read and again, completely free.
From: rdmp205 on 16 Nov 2009 10:22 "Claudio Rodrigues" wrote: > Eric Wood wrote: > > Hello, > > > > I have three PowerPC G4 based Workstations running Tiger (10.4.11) and > > Microsoft Remote Desktop Connection Client for Mac 2.0.1. > > > > I can connect and login to an account on the server running Microsoft > > Server 2008 R2 Enterprise if I save the username and password in the > > client. > > > > Once connected I can use the mouse to start applications and control the > > machine as needed. > > > > If I type (a-z,A-Z,0-9) or press any modifier key I receive the > > following message and I am dropped. > > > > You were disconnected from the Windows-based computer. > > > > Someone with access to the Windows-based computer may have ended the > > connection, or the Windows-based computer has dropped the connection. > > > > Try reconnecting to the Windows-based computer, > > or contact your administrator. > > > > Cancel / Reconnect > > > > This occurs on any valid account on the server. From the lowliest user > > to the Domain Administrator. > > > > CoRD 0.4.3 (The last version to support Tiger) has been tried. It will > > not connect to Microsoft Server 2008 R2 Enterprise and upgrading these > > workstations to Leopard is not an option at this time. > > > > I have gutted RDC Client for Mac as best as I know how and installed it > > fresh. > > > > I removed the following: > > > > rm -rvf /Users/blahblah/Documents/RDC\ Connections/ > > > > rm -rvf /Users/Shared/Microsoft/RDC\ Crucial\ Server\ Information/ > > > > > > > > The clients without being modified running the Microsoft RDC Client for > > Mac 2.0.1 can connect to various Microsoft Windows Server 2003 Standard > > Edition boxes around the organization. I do not have any Microsoft > > Windows Server 2008 (non-R2) machines to test against. > > > > This issue is only affecting my PowerPC based workstations running Tiger > > or Leopard. All of my Intel based workstations running Tiger or Leopard > > can connect without issue using the 2.0.0-2.0.1 client version. > > > > I fired up tsconfig.msc and looked at the various settings. Nothing was > > set in an odd manner. I tried lowering encryption requirements and > > disabling clipboard and other such things. I tried limiting the > > connections to 15bit, 16bit, 24bit, and 32bit color depth. It made no > > difference. Still can connect and control with the mouse but if you type > > you are dropped. > > > > I installed a fresh copy of Apple OS X Leopard on a PowerPC based 12" > > iBook G4. I updated to 10.5.8 and then installed Microsoft RDC Client > > for Mac 2.0.1. I can control the session with the mouse but I am dropped > > immediately upon typing. > > > > So I am down to blaming Microsoft's PPC version of RDC because the Intel > > version of RDC works without issue on Tiger or Leopard. The PPC version > > fails on all machines I have tried using either Tiger or Leopard. > > > > I tried 1.X versions of Microsoft RDC Client for Mac for the heck of it. > > As stated on the www.microsoft.com/mac website they do not support > > Windows Server 2008. I too experienced the inability to connect to the > > server at all with the 1.0.3 client on any machine. > > > > Eric Wood > > Technology Assistant > > MSAD #72 > > Fryeburg, ME > > US > Just to let you know the Mac group at Microsoft is now looking into the > issue. Just got an email from someone at the TS group in Redmond. > > -- > Claudio Rodrigues > CEO, WTSLabs Inc. > > http://www.wtslabs.com > "WebTS: TSWeb the way it should have been done since day one" > > Citrix CTP > Provision Networks VIP > > Make sure you download our free guide about Terminal Services. > An A to Z guide, explaining everything, from setting it up to enabling > group policies. A must read and again, completely free. > . > Do you know if there is any fix for this yet? I am experiencing the same issue. Thanks, Rob
From: skorpian23 on 25 Nov 2009 17:18
I am also having this problem. I have a clean install of Windows Server 2008 R2 (VMWare Guest under ESXi 4) and I am trying to connect using 2.0.1 RDC For Mac OS X on a Powerbook G4 Power PC. As soon as you type or any letter or keystrock you get disconnected. Please advise. Thanks Chris "rdmp205" wrote: > > > "Claudio Rodrigues" wrote: > > > Eric Wood wrote: > > > Hello, > > > > > > I have three PowerPC G4 based Workstations running Tiger (10.4.11) and > > > Microsoft Remote Desktop Connection Client for Mac 2.0.1. > > > > > > I can connect and login to an account on the server running Microsoft > > > Server 2008 R2 Enterprise if I save the username and password in the > > > client. > > > > > > Once connected I can use the mouse to start applications and control the > > > machine as needed. > > > > > > If I type (a-z,A-Z,0-9) or press any modifier key I receive the > > > following message and I am dropped. > > > > > > You were disconnected from the Windows-based computer. > > > > > > Someone with access to the Windows-based computer may have ended the > > > connection, or the Windows-based computer has dropped the connection. > > > > > > Try reconnecting to the Windows-based computer, > > > or contact your administrator. > > > > > > Cancel / Reconnect > > > > > > This occurs on any valid account on the server. From the lowliest user > > > to the Domain Administrator. > > > > > > CoRD 0.4.3 (The last version to support Tiger) has been tried. It will > > > not connect to Microsoft Server 2008 R2 Enterprise and upgrading these > > > workstations to Leopard is not an option at this time. > > > > > > I have gutted RDC Client for Mac as best as I know how and installed it > > > fresh. > > > > > > I removed the following: > > > > > > rm -rvf /Users/blahblah/Documents/RDC\ Connections/ > > > > > > rm -rvf /Users/Shared/Microsoft/RDC\ Crucial\ Server\ Information/ > > > > > > > > > > > > The clients without being modified running the Microsoft RDC Client for > > > Mac 2.0.1 can connect to various Microsoft Windows Server 2003 Standard > > > Edition boxes around the organization. I do not have any Microsoft > > > Windows Server 2008 (non-R2) machines to test against. > > > > > > This issue is only affecting my PowerPC based workstations running Tiger > > > or Leopard. All of my Intel based workstations running Tiger or Leopard > > > can connect without issue using the 2.0.0-2.0.1 client version. > > > > > > I fired up tsconfig.msc and looked at the various settings. Nothing was > > > set in an odd manner. I tried lowering encryption requirements and > > > disabling clipboard and other such things. I tried limiting the > > > connections to 15bit, 16bit, 24bit, and 32bit color depth. It made no > > > difference. Still can connect and control with the mouse but if you type > > > you are dropped. > > > > > > I installed a fresh copy of Apple OS X Leopard on a PowerPC based 12" > > > iBook G4. I updated to 10.5.8 and then installed Microsoft RDC Client > > > for Mac 2.0.1. I can control the session with the mouse but I am dropped > > > immediately upon typing. > > > > > > So I am down to blaming Microsoft's PPC version of RDC because the Intel > > > version of RDC works without issue on Tiger or Leopard. The PPC version > > > fails on all machines I have tried using either Tiger or Leopard. > > > > > > I tried 1.X versions of Microsoft RDC Client for Mac for the heck of it. > > > As stated on the www.microsoft.com/mac website they do not support > > > Windows Server 2008. I too experienced the inability to connect to the > > > server at all with the 1.0.3 client on any machine. > > > > > > Eric Wood > > > Technology Assistant > > > MSAD #72 > > > Fryeburg, ME > > > US > > Just to let you know the Mac group at Microsoft is now looking into the > > issue. Just got an email from someone at the TS group in Redmond. > > > > -- > > Claudio Rodrigues > > CEO, WTSLabs Inc. > > > > http://www.wtslabs.com > > "WebTS: TSWeb the way it should have been done since day one" > > > > Citrix CTP > > Provision Networks VIP > > > > Make sure you download our free guide about Terminal Services. > > An A to Z guide, explaining everything, from setting it up to enabling > > group policies. A must read and again, completely free. > > . > > > > Do you know if there is any fix for this yet? I am experiencing the same > issue. > > Thanks, > > Rob |