Tagged: NoConnection remotelogin login
December 9, 2023 at 23:01 #46268
I can connect to my Kubuntu 23 Linux box just fine from a Windows 10 machine if I am logged in locally on the remote Kubuntu Linux machine.
However if I log out of my session on the Linux machine (whether locally or via the remote connection) my remote NoMachine session on my Windows 10 box stops dead. If I have just restarted my Linux box and it is sitting on the login screen, I cannot login to it remotely from NoMachine on my Windows machine. And that is even if I have changed the security section on the ‘server’ Linux desktop to check the box for: “Make access available when the system is still in the login screen.”
This is on a brand new fresh install of Kubuntu 23. An actual physical box with a monitor/display attached.
NoMachine 8.10.1 On Linux
NoMachine Enterprise Client 8.10.1 on Window 10 x64December 14, 2023 at 18:16 #46350BritgirlParticipant
It could be related to this already known bug:
White screen occurs when connecting to a KDE/Plasma Wayland desktop on Kubuntu
Try disabling Wayland and use X.org instead. Does this help?December 14, 2023 at 19:09 #46352
Bottom left of the login screen says: Desktop Session: Plasma (X11), so I believe I’m already using X11. That is, unless there are elements of Wayland being used behind the scenes.
FWIW, it seems a shame that Wayland would be a problem anyway.December 14, 2023 at 19:22 #46353
- Turn on the remote Linux boxL
- Linux box gets to login screen
- Bottom left indicates X11 session
- Open NoMachine
- NoMachine says no remote hosts found on the network (attached screenshot)
- I log into the remote machine
- I click on search again in NoMachine
- NoMachine finds the remote box.
Attachments:December 16, 2023 at 09:19 #46378
OK, sorted it out. In KDE Settings, need to go into Connections and set the parameters for the network manager to allow wifi to be available even without the user I am connecting with being logged in.
- In Connections, select the wifi interface and go to General Configuration.
- Select/check ‘Connect automatically with priority’ (I left it a 0).
- Select/check ‘All users may connect to this network
- Go to the wif-fi security tab
- below the password text box use the drop down selection to select ‘Store password for all users (not encrypted)
This seems to have been what allows me to connect while the machine is at the login screen on boot and if you log out of the session either manually or by the NoMachine server configuration to log the session out after disconnecting.
It would be nice if there were a way to keep the passwords encrypted, but that is for another day. I can now start using this for what I have in mind.
Now it would be nice to see if I can connect and get dual desktops (which I have on the client machine) even if I only have one monitor local to the ‘server’ machine.
Cheers.December 18, 2023 at 17:42 #46387BritgirlParticipant
We were unable to reproduce this problem of not being advertized on the LAN. Can you send us the logs of the server side? Please follow the instructions here and submit them to forum[at]nomachine[dot]com using the title of this topic as the subject of your email.
You must be logged in to reply to this topic.