![]() ![]() Socket 12: AF_INET6 connection received from ::1 port 50932 *** from boot log: rvice: Can't open PID file /run/xrdp/xrdp.pid (yet?) after start: Operation not permitted xrdp channel server for display 10 (pid 32583) exit code 0 and signal number 0Īfter just updating my Debian install (from sid), I am getting the exact same symptom (=black screen upon rdping from a Win7 machine) with the exact same logs (/xrdp.log and /xrdp-sesman.log). X server on display 10 (pid 32579) returned exit code 1 and signal number 0 Terminating the xrdp channel server (pid 32583) on display 10 Terminating X server (pid 32579) on display 10 Calling auth_stop_session and auth_end from pid 32577 This could indicate a window manager config problem Window manager (pid 32578, display 10) exited quickly (0 secs). Timed out waiting for X server on display 10 to startup Session in progress on display 10, waiting until the window manager (pid 32578) exits to end the session Starting the xrdp channel server for display 10 Window manager (pid 13340, display 10) exited quickly (0 secs). A fatal error has occured attempting to start the window manager on display 10, aborting connection There is no X server active on display 10 ![]() I don't recall if I ever was able to enable a logging session (If I did I don't recall how I enabled logging the connection attempt).Timed out waiting for X server on display 10 to startup If Remote Login is enabled, then you may first need to establish an SSH tunnel before being able to connect using VNC. When using the command line I am prompted for the Mac's VNC password before it launches a window for the remote GUI session. I have also enabled "Observe" & "Control" found on the "Options" button for the authorized user. ![]() On the Mac I have enabled a VNC password (click on "Computer Settings" button under Remote Management). On Linux I use the following command to connect to a Mac using VNC (xtightvncviewer is being used - I believe you can just use the tightvncviewer command as well): vncviewer Plus different versions of macOS seem to behave differently. I don't have these issues when connecting to a Linux remote system. Even when I connected to the remote Mac the graphics in the session were very slow to load and both computers are on the same LAN. When I was having trouble I was able to enter my VNC password, but a VNC window never opened. After disconnecting from the VNC session I was unable to access the remote Mac via VNC for a while. I had to try multiple times before I was able to connect. I actually was having trouble connecting to a Mac using VNC myself. ![]() So, my question is: is there a way to get the Mac to start listening on the Screen Sharing port (5900, I believe) and accept screen sharing requests after the machine boots up and before anyone logs into it? I don't want to disable File Vault and I don't want to leave the Mac running all the time. I suspect I could work around this issue by enabling auto login on the Mac, but to do that I would have to disable File Vault, which I'd rather not do. The VNC error I get before logging into the Mac seems to indicate that before that initial login the Mac is not listening on the Screen Sharing port. Once I login, I *can* access the Mac via Bonjour or the Address Book entry I made in VNC. However, I've discovered that VNC Viewer cannot connect with the Mac after it's turned on or rebooted until after someone logs into it. How to make VNC Viewer on iPad connect with Mac (Big Sur) Screen Sharing before someone logs in? I would like to use my iPad with VNC Viewer via Screen Sharing to control my Mac Mini. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |