Britgirl

[Britgirl]

Are you seeing the local cursor and the remote cursor?

Is it just you connecting to the remote desktop or are there other users? When there are multiple users connected, the remote cursor will show regardless of what is set in that option.

It would be useful to know the macOS version and whether it’s a headless Mac. Please also tell us the specific Mac model.

[Britgirl]

Hi,

please provide some more details about the cursor problem. What is happening exactly? Can you submit a screenshot or two showing the issue?

[Britgirl]

Hi, are you able to send us complete logs, from both the player and server sides? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. For the player session logs you need to refer to “Fourth step” in that document. Also, system logs (journalctl) would be useful as well.

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

One thing worth noting here because it’s not been mentioned is that if you want to start SSH connections from the Mac machine to your Ubuntu host with NoMachine, on the server you need to have a product from the Enterprise family. If you have NoMachine free version installed on the server side, it cannot accept SSH connections. I think Guro assumed that you did (e.g Enterprise Desktop is the same as the free version but provides SSH support, web-based connections and other features) when he suggested trying an SSH connection.

[Britgirl]

The attachment you sent us from the Windows machine does not contain the player logs from the Windows machine.

Are you enabling the box in the Player (don’t delete logs upon exit) ?

To debug a problem which causes a session freeze or a disconnect, be sure that the Don’t delete log files on exit checkbox is selected in UI -> Settings -> Player -> Security panel before launching the client to reproduce the problem. Start the session, do not close the Player window once problem has been reproduced.

On Windows the .nx folder is hidden. To find it, write the following in the address bar or the file browser:
%USERPROFILE%\.nx

Or navigate through the computer folder till the user’s home and digit .nx in the navigation toolbar to reach it. Path can be similar to: C:/Users/nomachine/.nx.

Thanks.

 

[Britgirl]

Hi,

In order to see the fullscreen on all screens button, the client needs to detect that there are multiple displays available.

While using the Kubuntu Machine with dual monitors, I wish to connect to the Windows Desktop and have both monitors be displayed across both monitors on the Kubuntu Desktop on a separate Virtual Desktop. I have not been able to get this to work.

Strange. I understand that you are connecting to your Windows machine and there are two physical monitors there. Your Kubuntu also has dual physical monitors as well. Have I understood right?

Can you try a connection in the opposite direction? So from your Windows client to the Ubuntu machine? What happens?

Please send us the output of the xrandr command on the Kubuntu machine. Is the Kubuntu using Wayland or Xorg?

[Britgirl]

Thanks for submitting those and we can see there are many attempts to connect. The problem appears to be in the nx daemon, but the logs you sent didn’t include the daemon logs. If possible, please restart nxserver, reproduce the issue and send a new set of logs.

[Britgirl]

The first article (https://kb.nomachine.com/AR10M00866) is about identifying client devices. It’s an additional layer of security, to limit number of devices from where user can connect. It doesn’t replace user authentication which is still mendatory.

The second article, the one I linked in my reply (https://kb.nomachine.com/AR02L00785) is about using keys instead of passwords for user authentication. It removes the need to provide a password but the user still has to identify himself with a proper username. In that case you have to create at least one key pair for each user. The private key has to be securely stored on each client device from where a given user is connecting. The public key has to be distributed to all the server side hosts where that user needs to be able to log in.

[Britgirl]

That article is dedicated to configuring the device. Please check this article instead:

https://kb.nomachine.com/AR02L00785 which is for user authentication.

[Britgirl]

Hi, this is a known issue and a Trouble Report has already been opened. You can track its status using the following link: https://kb.nomachine.com/TR08V11198

[Britgirl]

Yes, visudo.

[Britgirl]

Try this instead

nx ALL=(ALL) NOPASSWD: /usr/bin/systemctl start lightdm.service, /usr/bin/systemctl stop lightdm.service

We tested on our Debian with XFCE. Nx will have permission to execute sudo without password but only to start/stop lightdm service.

[Britgirl]

Hi, send that file to forum[at]nomachine[dot]com.  Maximum file size is 1024 KB.

[Britgirl]

Strange. Our tests on default Fedora don’t reproduce any problems. We set this:

export PATH=”$PATH:/usr/NX/bin”

in .bashrc, and it works.

[Britgirl]

You mentioned that you had tried disabling HW decoding, but the crash report indicates that HW decoding is still being loaded. You need to “Quit NoMachine player” before changing it, edit the key to<option key=”Enable hardware accelerated decoding” value=”disabled” /> and save. Open NoMachine and start the session.

Please refer to this article for reference:

https://kb.nomachine.com/AR07U01202

[Author]

Posts