Re: OS X RDC client does not support Session Directories (read)

RDP 5 is needed. I believe that Microsoft has not updated RDP for Mac since
late 4.x. Direct connections to new sessions should work correctly but you
may have to force logoff for Mac clients to prevent inaccessible sessions..

--
Jim Vierra
http://msdn.microsoft.com/theshow/Episode048/default.asp
"Schley Andrew Kutz" <SchleyAndrewKutz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:40D937EC-71C5-4815-9E69-17E4327AD63E@xxxxxxxxxxxxxxxx
>I tried connecting to my farm with rdesktop 1.4.0 from OS X.
>
> When you make the initial connection (whether you have an existing session
> or not) you get this error:
>
>> NOT IMPLEMENTED: RDP5 opcode 6
>
> I do not know what opcode this is but it probably has something to do with
> the server attempting to map sound, which rdesktop does not support.
>
> Trying to reconnect to a disconnected session is a bit trickier! This is
> because rdesktop actually issues a logoff command when you hit "X" to
> close
> the terminal window. To actually disconnect a rdesktop session you have
> to
> administratively log off the user with TS Manager on the server.
>
> So you are reconnecting to a session on Server A and hit Server B
> initially,
> here is what rdesktop produces:
>
> NOT IMPLEMENTED: data PDU 174
> ERROR: recv: Connection reset by peer
> ERROR: Connection closed
> Broken pipe
>
>> NOT IMPLEMENTED: data PDU 174
>
> AH HA! This makes perfect sense. Microsoft's RDC client for OS X and
> rdesktop 1.4.0 both must be not understanding the "data PDU 174" or
> whatever
> it contains. This must be the "command packet" that is telling the client
> to
> either generate a token (Token Redirection method) or open a connection to
> server B (IP Redirection method).
>
>> ERROR: recv: Connection reset by peer
>> ERROR: Connection closed
>> Broken pipe
>
> The client's connection will be reset because server A has sent its
> "command
> packet" to server B and has closed its connection to the client. It is up
> to
> the client at this point to take the necessary actions to maintain the
> connection to terminal services, which apparently on the Windows RDC
> client
> can.
>
> Ugh ...
>
> "Schley Andrew Kutz" wrote:
>
>> (I am posting this here because it is apparent by the number of posts,
>> 2,
>> that no one reads/posts the client forum)
>>
>> It seems that Microsoft's RDC client for OS X cannot reconnect to a
>> disconnected session on a terminal server that participates in a session
>> directory.
>>
>> Both IP Redirection and Token Redirection have been tried. Token
>> Redirection
>> is not supported by our LB (Netscaler) but we
>> turned it on to watch the traffic anyway.
>>
>> Both configs result in the Mac RDC error "Internal RDC error"
>>
>> Since both methods rely on the backend terminal server sending a "command
>> packet" back to the client either telling it to generate a token to send
>> to
>> the LB (Token Method) or to connect directly to the terminal server that
>> has
>> its session (IP Redirection) it is apparent that the Mac RDC client not
>> only
>> does not understand this "command packet," but the packet also causes the
>> RDC
>> client to fubar.
>>
>> I will also be submitting a feature request to Netscaler asking that they
>> support WTS tokens as it will allow me to firewall the backend servers
>> completely from the outside world. As it is I cannot since the clients
>> have
>> to be able to connect directly to the terminal servers if they are
>> resuming a
>> disconnected session. Using the token method also lets you connect
>> directly
>> to the terminal servers (on allowed networks, yay SP1) bypassing the
>> session
>> directroy since the token that the client receives will be useless since
>> there is no LB to interpret it.


.

Relevant Pages

  • Re: .Net Scalability problem
    ... LoadRunner will peak out a server with a few virtual users. ... To get an idea of load, ... Fire off the test client and watch the number of ... > So I think that the MTC generate concurrent connection and per ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Connection lost at same time every hour (sometimes)
    ... After making the two following alterations on the server the problem seems ... After analyze your ipconfig on SBS and client, ... Then, other connection is good, ...
    (microsoft.public.windows.server.sbs)
  • Re: server disconnection - very often
    ... Reason of permanent popups is VMware server aplication on clients. ... Run CEICW to configure the network of SBS: ... Two network adapters - manual router connection to broadband ... Uninstall VMware on client. ...
    (microsoft.public.windows.server.sbs)
  • Re: Lan setup 2 nic
    ... The external nic only has TCP/IP enabled. ... Ipconfig of the server is looking good, but the client is still missing the ... > connection so we have a 2 nic with router setup now. ...
    (microsoft.public.windows.server.sbs)
  • Re: Regular disconnections from remote web workplace
    ... I can connect to office server and all office clients from home at all times ... be physically working right up until the connection is lost. ... If I enter http://companyip from a client I receive the login screen for the ... Click Services tab and select Hide All Microsoft Services and Disable ...
    (microsoft.public.windows.server.sbs)