> Ok, at this point it seems to be a xrdp problem (not sesman problem).
> I suggest you (as you compiled all with --enable-xrdpdebug) to run
> xrdp in foreground (./xrdp -nodaemon >> logfile) to see what's
> happening.
>
> Note1: xrdp-sesman.log is actually only written by sesman, so is
> sesman log only!
> Note2: xrdp -nodaemon will generate a *huge* log file writing down
> every function called and what is happening inside.
>
> --
> Nicola
Thank you. I think I have this thing mostly working! It took me a long time,
but I finally figured out that I still had some old remnants of previous
versions of xrdp still on the server. I hunted down every xrdp file and binary
I could find and removed them. Then I re-installed the cvs version with your
compiler fix added, and now it's mostly working.
On SLES, the libraries that were installed into /usr/local/lib/xrdp were not
being found by xrdp at runtime. I fixed that via:
echo /usr/local/lib/xrdp/ > /etc/ld.so.conf.d/xrdp.conf
ldconfig
I can now connect to the X11rdp backend via both rdesktop as well as mstsc.
However, the cursor never appears anywhere, which is a new problem.
Now, in the case of the Xvnc backend, it now throws an error when I connect by
either rdesktop or mstsc:
connecting to sesman ip 127.0.0.1 port 3350
sesman connect ok
sending login info to sesman
xrdp_mm_process_login_response: login successful for displa
started connecting
connecting to 172.0.0.1 5913
tcp connected
security level is 2 (1 = none, 2 = standard)
error - problem connecting
However, the processes are all created and running.
xrdp-sesman
`-xrdp-sessvc 16527 16526
|-Xvnc :13 -geometry 1280x980 -depth 16 -rfbauth
/home/cwheeler/.vnc/sesman_cwheeler_passwd -bs -ac -nolisten tcp
|-startwm.sh /etc/xrdp/startwm.sh
| `-startkde /opt/kde3/bin/startkde
| `-kwrapper ksmserver
`-xrdp-chansrv
`-{xrdp-chansrv}
In fact, if I just reconnect, then everything works.
So, to summarize, mstsc and rdesktop can connect via X11rdp backend, except for
the cursor issue, and it fails the first time when connecting to the Xvnc
backend, and works after that. I'd like to clear up these last problems, but
not sure how to do so.
Thanks so much for your help.
Regards,
Rich
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
xrdp-devel mailing list
xrdp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xrdp-devel
