On Mon, Jun 4, 2012 at 11:30 AM, David Burgess <apt....@gmail.com> wrote: > On Thu, May 31, 2012 at 1:46 PM, David Burgess <apt....@gmail.com> wrote: > >> So it looks like xfreerdp is running (twice?) with my option, but >> still no evidence of a connection. Any suggestions?
Thanks to Alkis' suggestion in another recent thread, I have some new information on this issue, and using xterm on the client to start xfreerdp, I learned some things: 1) I need to use the following xfreerdp switches in xterm to get an immediate connection without prompts in the terminal: --ignore-certificate, otherwise I get a certificate error and no connection until I hit "y" --no-nla, otherwise I get a password prompt before connecting to the terminal server So by typing at the xterm on the client something like: xfreerdp --ignore-certificate --no-nla -d gprc -u dburgess 172.21.34.1 I get a Windows logon screen as expected. 2) The options that work in xterm do not work for me when plugged straight into lts.conf along with SCREEN_07=xfreerdp. So using the above options as an example, none of the following configuration produce anything other than a black screen on the client, sometimes with a mouse pointer present: [sample:config:1] HOSTNAME=virtual-tc SCREEN_07=xfreerdp -f --ignore-certificate --no-nla -d gprc -u dburgess 172.21.34.1 [sample:config:2] HOSTNAME=virtual-tc SCREEN_07=xfreerdp RDP_OPTIONS=-f --ignore-certificate --no-nla -d gprc -u dburgess 172.21.34.1 [sample:config:3] HOSTNAME=virtual-tc SCREEN_07=xfreerdp RDP_OPTIONS=-f --ignore-certificate --no-nla -d gprc -u dburgess RDP_SERVER=172.21.34.1 Besides the common black screen, all three of these configs produce the same output in an ssh terminal: root@virtual-tc:~# ps aux | grep rdp root 1646 0.0 0.0 3560 652 tty7 S+ 10:15 0:00 xinit /usr/share/ltsp/xinitrc xfreerdp -f --ignore-certificate --no-nla -d gprc -u dburgess 172.21.34.1 -- :7 vt7 -depth 16 root 1681 5.6 0.0 2216 668 tty7 S 10:15 0:33 /bin/sh /usr/share/ltsp/xinitrc xfreerdp -f --ignore-certificate --no-nla -d gprc -u dburgess 172.21.34.1 root 22384 0.0 0.0 4364 836 pts/0 S+ 10:24 0:00 grep --color=auto rdp By contrast, the same command when run on a client that is successfully connected to a terminal server logon screen via xterm looks like this: root@virtual-tc:~# ps aux | grep rdp root 1718 2.0 0.1 18536 3852 pts/0 Sl+ 10:27 0:00 xfreerdp -f --ignore-certificate --no-nla -d gprc -u dburgess 172.21.34.1 root 1751 0.0 0.0 4364 832 pts/1 S+ 10:28 0:00 grep --color=auto rdp So my guess is that there is something wrong with the script in /usr/share/ltsp/screen.d/xfreerdp, but it's beyond my skillset at this point to troubleshoot it effectively. db ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
