Forum Replies Created
-
Posts
-
Please consult the connection menu guide, Display section:
https://kb.nomachine.com/DT09T00267#5.1
Also the following tutorial might be of help:
https://www.nomachine.com/switching-the-view-between-multi-monitors-during-a-remote-desktop-session
We’re not able to reproduce this behaviour.
What applications are you using when you perform the copy and paste?
It looks similar to this Trouble Report we’ve already opened
Black screen when connecting to Wayland using two monitors
https://forums.nomachine.com/topic/one-of-two-monitors-is-black-and-mouse-pointer-is-uncalibratedThe workaround is to change the following key in node.cfg to:Â WaylandModes drm,compositor,egl
So, in other words removing NoMachine from the picture you cannot make a pure ssh connection to the Mac host from outside the network.
When you’ve got your networking set-up sorted, carry out the simple tests I suggested again and if you can’t connect with NoMachine in test 2 or 3 come back to us with the logs as requested.
Could you try disabling hardware decoding on the machine you are connecting from?
Follow the instructions :
1. Quit the Player and disable hardware decoding in the player.cfg ->
option key="Enable hardware accelerated decoding" value="disabled". Restart the Player. Try connecting again. If that doesn’t help, go to point 2.2. Disable hardware encoding on your Linux machine ->
option key="EnableHardwareEncoding” key to 0in node.cfg on the server side. Restart the server.3. Try connecting again.
Does this help? Does anything change if you update to 8.3.1?
When we release NoMachine Network in the future port-forwarding won’t be necessary, and it will be possible to connect without knowing the IP address of the computer you want to connect to 🙂
You can see more about this feature on our website here:Â https://www.nomachine.com/network
You could try connecting with ssh and:
sudo /etc/NX/nxserver --history | grep Connected sudo /etc/NX/nxserver --disconnect <session ID>We reproduced it 🙂
Here is the link to the Trouble Report: https://kb.nomachine.com/TR01U10748The workaround is to enter the connection menu Ctrl-Alt-0 and add from there.
1. Forwarding mouse and keyboard from client side:
session settings -> devices -> connect a USB device -> forward local mouse and keyboard
2. Activating remote cursor:
session settings -> input -> keyboard and mouse -> check option “always show remote cursor pointer”
Majkl,
Thanks for the logs. They were useful but why it’s happening is still not clear. We’re still trying to reproduce your issue.
In the meantime, could you send us the contents of C:\Program Files\NoMachine\etc\nxdb? Just zip up and send like you did the logs. Thanks!
On another note, you asked about NoMachine and how data travels between client and server. Please see our articles here for more about this:
Default ports used by NoMachine 4 or later – https://kb.nomachine.com/AR01L00770
NX and the use of UDP protocol https://kb.nomachine.com/AR10T01174