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

rdesktop.org's client supports RDP5, so it must be that it does not support
ALL of the RDP5 spec.

Any word on when MS is going to update the Mac RDP client? I can't believe
that I am the first person to run into this. Is this a known issue?

"Jim Vierra" wrote:

> 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: SSL/TLS & renegotiation and Internet Explorer
    ... When IE closes the connection with the server and prompts the user to choose ... recovery logic the SSL session is discarded. ... If the user only has one suitable client certificate, ...
    (microsoft.public.security)
  • Re: RDP Printing by station
    ... flagged as non-printing stations can not print for ANY users. ... multiple NIC's on the terminal server. ... I'd then just have to ensure that the client stations that are ... session is limited to NIC # 1. ...
    (microsoft.public.windows.terminal_services)
  • SSL and IPS (was RE: ssh and ids)
    ... How many simultaneous SSL sessions can be tracked?" ... I assume you're talking about a case in which the client constantly ... If you walk the possible session id space and ... The server chooses the session ID, ...
    (Focus-IDS)
  • Trying to setup FreeNX
    ... I've installed FreeNX server and the NX client from ... Below is a copy of the failure as recorded by my NX client trying to ... NX> 103 Welcome to: bhf user: bob ... NX> 703 Session type: unix-kde ...
    (alt.os.linux.suse)
  • Re: Working around UAC for AccessCheck API, how?
    ... I have a client server solution that uses RPC in order to talk from the ... this is how restricted tokens and UAC ... Use the impersonated user's token and call AccessCheck. ...
    (microsoft.public.win32.programmer.kernel)