Forum Replies Created
-
Posts
-
You have the same overlapping issue like in the other topic mentioned above. To fix the overlap you can move the second screen to not overlap the other. For example, arandr will let you do this.
An easy way to fix the overlap is to do
sudo apt install arandrand run that application. It lets you organize the screens and you can fix the overlapping.Hi, adding the possibility to disable clipboard from the client side is already planned. It’s currently in our development roadmap for version 9.x.
Indeed this looks similar to https://forum.nomachine.com/topic/no-fullscreen-across-all-monitors-option-for-dual-screen-setup
Can you send us the output of the xrandr command on the Kubuntu machine?
We noticed that the monitors overlap by 1 pixel.
Screen 0: minimum 320 x 200, current 3839 x 1080
DisplayPort-1 connected 1920×1080+0+0
DisplayPort-2 connected primary 1920×1080+1919+0We are checking on our side what improvements can be done, but if you fix the overlapping of the monitors’ position, it should be OK.
You can login to the server as any other user provided the account is valid on the server. So, there could be users John, Jack and Jill. NoMachine handles key authentication in the same way as SSH. The keys are set per system user account. So, if the desktop on the server is owned by John, the user which connects should login as John. If you login with another valid system user (Jack or Jill), user John will have to authorize the connection.
We’re not able to reproduce it. Can you send us the server-side logs so we can check them? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Or you can attach the zip archive here. Thanks!
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.
Hi,
please provide some more details about the cursor problem. What is happening exactly? Can you submit a screenshot or two showing the issue?
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!
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, 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.
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%\.nxOr 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.
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?
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.
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.