> I'm not 100% familiar with RDP protocol, but when I have some spare time > in a few week's time, I'll track down this bug for you. Erick (upstream) > has been too busy to do it himself.
Don't worry, I am even less familiar, it's basically only out of sheer
necessity that I am using it ;)
> Could you please send me a .rdp file (remember to censor saved
> passwords/addresses) that is meant to execute a program on a remote
> machine so that I figure out which field isn't being parsed.
I now changed the startup script to execute
"rdesktop -nLNX.$config{USERNAME}.".$config{'W_TIME'}." -T\"Barco Hydra
Timesheets on $config{'W_HOST'}\" -u$config{USERNAME}
-d$config{WORKGROUP} -f -a8 -rsound -b -4 $config{'W_HOST'}"
which works fine (instead of the tsclient -x). Of course, I am setting a
lot of options myself here and though they might be the same now (as in
the RDP defined, the command line was ripped out of the tsclient code
IIRC), this might not be the case in the future.
Considering that a lot of users are Windows oriented that experiment
with GNU/Linux, being able to use tsclient as a drop in replacement of
the official cliant, would help though...
--
greetz, marc
Who's your daddy? C'mon, you know who your daddy is. Who's your
daddy? D'Argo, tell him who his daddy is.
Crichton - Thanks for Sharing
scorpius 2.6.11 #1 Wed Mar 2 16:38:38 CET 2005 GNU/Linux
CONFIG.rdp
Description: Binary data
signature.asc
Description: Digital signature
