you should check if any proccess/sub-proccess of xrdp-sessvc is binding the port (should use sudo netstat -apn). that was a bug in xrdp-sesman, which fixed recently (https://github.com/FreeRDP/xrdp/commit/75f4c3ca584b30b6e7f44dfec0da0845de43a166)
-- View this message in context: http://xrdp-devel.766250.n3.nabble.com/Xrdp-devel-Port-tp4025144p4025153.html Sent from the XRDP Devel mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
