Find the answer to your Linux question:
Results 1 to 9 of 9
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    Xrdp Shows Blank Screen, Then it Turns Black, and then it Disconnects


    Hi all,


    I hadn't tried remote access from my Windows boxes to my Fedora Xrdp servers for about 4-5 months. It worked fine then.

    When I tried for the first time this evening, after the login, I got a blank light blue screen, then it turned black, and then it disconnected. I am using Windows Server 2008 R2 and Windows 10 mstsc as the rdp clients.

    I have both Fedora 25 and 26 - and have the same problem with both. I uninstalled and re-installed xrdp, and it didn't help.

    The 2 Fedoras can successfully remote to each other using a vinagre rdp client.


    systmctl status xrdp:
    Jul 21 02:23:18 lavie022.lavie.org xrdp[6323]: ssl_tls_print_error: SSL_shutdown: I/O error
    Jul 21 02:23:18 lavie022.lavie.org xrdp[6323]: [20170721-02:23:18] [DEBUG] Closed socket 12 (AF_INET 192.168.1.3:3389)
    Jul 21 02:23:18 lavie022.lavie.org xrdp[6323]: xrdp_mcs_disconnect - socket closed
    Jul 21 02:23:18 lavie022.lavie.org xrdp[6323]: [20170721-02:23:18] [DEBUG] xrdp_mm_module_cleanup
    Jul 21 02:23:18 lavie022.lavie.org xrdp[6323]: [20170721-02:23:18] [DEBUG] VNC mod_exit
    Jul 21 02:23:18 lavie022.lavie.org xrdp[6323]: [20170721-02:23:18] [DEBUG] Closed socket 19 (AF_INET 127.0.0.1:36060)
    Jul 21 02:23:18 lavie022.lavie.org xrdp[6323]: [20170721-02:23:18] [DEBUG] Closed socket 20 (AF_UNIX)
    Jul 21 02:23:18 lavie022.lavie.org xrdp[6323]: xrdp:xrdp_encoder [1649412391]: xrdp_encoder_delete:
    Jul 21 02:23:18 lavie022.lavie.org xrdp[6323]: [20170721-02:23:18] [ERROR] Listening socket is in wrong state, terminating listener
    Jul 21 02:23:18 lavie022.lavie.org xrdp[6323]: [20170721-02:23:18] [CORE ] shutting down log subsystem...


    systemctl status xrdp-sesman.service
    Jul 21 02:06:06 lavie022.lavie.org xrdp-sesman[6322]: (6322)(140405073602368)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:5910)
    Jul 21 02:06:06 lavie022.lavie.org xrdp-sesman[6322]: (6322)(140405073602368)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:0)
    Jul 21 02:06:06 lavie022.lavie.org xrdp-sesman[6322]: (6322)(140405073602368)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:5914)
    Jul 21 02:06:06 lavie022.lavie.org xrdp-sesman[6322]: (6322)(140405073602368)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6014)
    Jul 21 02:06:06 lavie022.lavie.org xrdp-sesman[6322]: (6322)(140405073602368)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6214)
    Jul 21 02:06:06 lavie022.lavie.org xrdp-sesman[6322]: (6322)(140405073602368)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:5916)
    Jul 21 02:06:06 lavie022.lavie.org xrdp-sesman[6322]: (6322)(140405073602368)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6016)
    Jul 21 02:06:06 lavie022.lavie.org xrdp-sesman[6322]: (6322)(140405073602368)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6216)
    Jul 21 02:12:28 lavie022.lavie.org xrdp-sesman[1015]: rdpSaveScreen:
    Jul 21 02:22:28 lavie022.lavie.org xrdp-sesman[1015]: rdpSaveScreen:

    I'd really appreciate any help.

    Regards,
    Lavie
    Last edited by mlavie; 07-21-2017 at 08:19 AM.

  2. #2
    Just Joined!
    Join Date
    Apr 2007
    Location
    Milwaukee, WI
    Posts
    27
    have you tried using a windows machine to rdp into this machine? Are you attempting to remote into a windows 7 OS? I'm quite positive that when you use a Windows machine to remote into this Windows machine, you will experience the same issue.... therefore this is a windows issue and not a Linux issue

    LMGTFY

  3. #3
    Hi Trippinshrumes,

    Sorry - I should have been clearer.

    I am RDP-in from Windows Server R2 and Windows 10 mstsc clients to Fedora 25 and 26 Xrdp servers.

    Any ideas?

  4. $spacer_open
    $spacer_close
  5. #4
    Some more info:
    This could be due to a change in the MS mstc client itself.
    I just installed a Fedora 25 from original media, and installed the old version of xrdp (9.0.6).
    I got the same problem.

  6. #5
    Just Joined!
    Join Date
    Apr 2007
    Location
    Milwaukee, WI
    Posts
    27
    My mistake, I thought you were remoting in to a windows machine.

    make a cert and key with
    Code:
    $ sudo openssl req -x509 -newkey rsa:2048 -nodes -keyout key.pem -out cert.pem -days 365
    Then update xrdp.ini file like so
    Code:
    certificate=/path/to/cert.pem
    key_file=/path/to/key.pem
    security_layer=negotiate
    Then restart xrdp and let me know if it worked for you.

  7. #6
    Quote Originally Posted by Trippinshrumes View Post
    My mistake, I thought you were remoting in to a windows machine.

    make a cert and key with
    Code:
    $ sudo openssl req -x509 -newkey rsa:2048 -nodes -keyout key.pem -out cert.pem -days 365
    Then update xrdp.ini file like so
    Code:
    certificate=/path/to/cert.pem
    key_file=/path/to/key.pem
    security_layer=negotiate
    Then restart xrdp and let me know if it worked for you.
    Thanks for the response!

    I actually had a legit commercial cert from a recognized CA specified, but not the "security_layer" parameter. I'll try this later - I've already put about 10 hrs. into this issue, and my girlfriend said that if I put one more hour into it today that I hade better find some open source software which can locate a new girlfriend for me...

    Will try later - again, thanks!

  8. #7
    Quote Originally Posted by Trippinshrumes View Post
    My mistake, I thought you were remoting in to a windows machine.

    make a cert and key with
    Code:
    $ sudo openssl req -x509 -newkey rsa:2048 -nodes -keyout key.pem -out cert.pem -days 365
    Then update xrdp.ini file like so
    Code:
    certificate=/path/to/cert.pem
    key_file=/path/to/key.pem
    security_layer=negotiate
    Then restart xrdp and let me know if it worked for you.
    Hi Trippinshrumes,

    I tried what you suggested, including creating a new key pair. No joy.

    Thanks in any case.
    Lavie

  9. #8
    Just Joined!
    Join Date
    Apr 2007
    Location
    Milwaukee, WI
    Posts
    27
    can we get log files with the security_layer parameter, please use the certs you just created. logs should be different than your first post and may give us the answer we need.

  10. #9
    -->
    Quote Originally Posted by Trippinshrumes View Post
    can we get log files with the security_layer parameter, please use the certs you just created. logs should be different than your first post and may give us the answer we need.
    xrdp:
    Jul 26 15:52:25 lavie022.lavie.org xrdp[18629]: (18629)(140338979321984)[DEBUG] VNC error before receiving server init
    Jul 26 15:52:25 lavie022.lavie.org xrdp[18629]: (18629)(140338979321984)[DEBUG] VNC error before receiving pixel format
    Jul 26 15:52:25 lavie022.lavie.org xrdp[18629]: (18629)(140338979321984)[DEBUG] VNC error before receiving name length
    Jul 26 15:52:26 lavie022.lavie.org xrdp[18629]: (18629)(140338979321984)[DEBUG] VNC error before receiving name
    Jul 26 15:52:26 lavie022.lavie.org xrdp[18629]: (18629)(140338979321984)[DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
    Jul 26 15:52:26 lavie022.lavie.org xrdp[18629]: (18629)(140338979321984)[DEBUG] Closed socket 19 (AF_INET 0.0.0.0:5838
    Jul 26 15:52:26 lavie022.lavie.org xrdp[18629]: (18629)(140338979321984)[DEBUG] xrdp_wm_log_msg: some problem
    Jul 26 15:52:26 lavie022.lavie.org xrdp[18629]: (18629)(140338979321984)[DEBUG] xrdp_mm_module_cleanup
    Jul 26 15:52:26 lavie022.lavie.org xrdp[18629]: (18629)(140338979321984)[DEBUG] VNC mod_exit
    Jul 26 15:52:26 lavie022.lavie.org xrdp[18629]: (18629)(140338979321984)[DEBUG] Closed socket 18 (AF_INET 127.0.0.1:32926)


    xrdp-sesman:
    Jul 21 21:51:03 lavie022.lavie.org xrdp-sesman[1089]: (1089)(139671872710464)[INFO ] starting xrdp-sesman with pid 1089
    Jul 21 21:51:03 lavie022.lavie.org xrdp-sesman[1089]: (1089)(139671872710464)[INFO ] listening to port 3350 on 127.0.0.1
    Jul 26 15:52:21 lavie022.lavie.org xrdp-sesman[1089]: (1089)(139671872710464)[INFO ] A connection received from 127.0.0.1 port 32926
    Jul 26 15:52:22 lavie022.lavie.org xrdp-sesman[1089]: (1089)(139671872710464)[INFO ] ++ created session (access granted): username root, ip 82.166.229.5:47286 - socket: 12
    Jul 26 15:52:22 lavie022.lavie.org xrdp-sesman[1089]: (1089)(139671872710464)[INFO ] starting Xvnc session...
    Jul 26 15:52:22 lavie022.lavie.org xrdp-sesman[1089]: (1089)(139671872710464)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:5910)
    Jul 26 15:52:22 lavie022.lavie.org xrdp-sesman[1089]: (1089)(139671872710464)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:0)
    Jul 26 15:52:22 lavie022.lavie.org xrdp-sesman[1089]: (1089)(139671872710464)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:5911)
    Jul 26 15:52:22 lavie022.lavie.org xrdp-sesman[1089]: (1089)(139671872710464)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6011)
    Jul 26 15:52:22 lavie022.lavie.org xrdp-sesman[1089]: (1089)(139671872710464)[DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6211)

    Please let me know if you need more info - and thanks!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •