Forum Replies Created
-
AuthorPosts
-
Britgirl
KeymasterIt certainly is not abandoned, we have had other priorities, mainly NoMachine Network, for NoMachine 9. Developers are currently working on HiDPI support, so that NoMachine can capture the screen of the server at native pixel resolution on such displays.
A note about the links you mention, you should see a page informing you that our road map is no longer in the public domain when you click on a feature request link.
Britgirl
KeymasterHi, I was just about to write to you for the logs and then found that you had replied with a workaround. Did you switch to Wayland on the client side or on the server side?
Would you be willing to help us debug? It would mean temporarily reverting to X11 and sending us the logs.
From the server machine, please follow the instructions here: https://kb.nomachine.com/DT07S00243
From the side you are connecting from:
– launch the NoMachine UI on the user’s computer from Programs or Menu
– click on Settings -> Player -> Security
– check Don’t delete log files on exit option
– Connect to the server and reproduce the problem.
– Compress the user’s home/.nx directory containing logs.Britgirl
KeymasterHi, thanks for the additional information. We confirm what we said before. Use this link to monitor the bugfix, https://kb.nomachine.com/TR05V11141. For the time being use x.org rather than Wayland.
December 12, 2024 at 18:59 in reply to: Black Screen in remote after cudnn install Ubuntu 24.04.1 LTS #51101Britgirl
KeymasterHi, we need the complete logs. Please follow the instructions in the guide here which explains how to gather the right logs for debugging: 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. Thanks!
Britgirl
KeymasterHi, we’ve never seen this before. Can you send the logs from the server? Please gather them using this command:
$ sudo tar -cvp --exclude 'cache*' --exclude 'images' --exclude 'temp' $HOME/.nx | gzip -c >user_nxdir.tar.gz
Britgirl
KeymasterWhat do you mean “it seems to connect”. Can you show us a screenshot of what you are seeing when you start the connection? What is shown instead of the login screen?
Britgirl
KeymasterHi, there are some similar topics asking the same question about using a static url. Take a look at:
A successful story in setting up NoMachine with Nvidia driver on AWS
Britgirl
KeymasterHi, it’s a known issue and a fix will be in the next update, you can track its status in our knowledge base:
https://kb.nomachine.com/TR10V11232
The workaround, as written in the TR:
modify file /usr/NX/share/src/nxusb/nxusb-vhci-hcd.c and replace line 1351: remove = vhci_hcd_remove, with: remove = (void *) vhci_hcd_remove,
Britgirl
KeymasterIf you are starting hyprland through the command line, you should restart the nxserver,
sudo /etc/NX/nxserver --restart
Britgirl
KeymasterHi, about your question concerning the icons, I’ll answer what I wrote in a similar topic (https://forum.nomachine.com/topic/explain-machines-icons-please) 🙂
The pipe icon, in your image it’s the first icon (located through local discovery), represents computers which are found on the same LAN. You can turn this off if you don’t want your server machines to advertize themselves on the LAN. See more about this here:
https://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network
You can also turn off LAN computers from being shown in your local Player if you want as well, this is also explained in the above tutorial. It has a label (in the edit panel) which explains what it is: “Located through local discovery service”.
The other icon (!M) represents an nxs file, i.e a connection you created manually. It shows when you create a connection to a computer. This connection file can also be from previous installations as it is stored in the .nx/cache folder. Unlike LAN-discovered machines, connections can be deleted. If you want to delete the LAN-discovered machine, disable the service as I described earlier.
Instead, about the icon that you say is “not working” and specifically “no mouse response on guest”, please provide the exact steps to reproduce and additionally:
– are you connecting to a physical or virtual display?
– what desktop environment are you connecting to (Mate, XFCE, something else)?Britgirl
KeymasterPlease tell us:
– client OS version
– server OS version
– what “CAD system” is on the server
– is it a virtual or physical desktop session?
– steps to reproduceDecember 10, 2024 at 18:23 in reply to: NX connection window disappears immediately after successful logging in #51048Britgirl
KeymasterOK thanks for letting us know, most likely caused by some corrupt file in Gnome, and not NoMachine.
December 10, 2024 at 10:23 in reply to: ED25519 and ECDSA for NX protocol produce “Authentication Failed” error #51042Britgirl
KeymasterThanks for clarifying the links. We are not quite sure why you are encountering this difference when connecting from the standalone Enterprise Client/Android app but not when connecting from the Free Edition because the implementation is the same code shipped in all cases.
Can you tell us if you are importing the key in the connection file when connecting from the EC and mobile clients?
There is a Trouble Report already open which affects importing the private key, the error shown is “Failed to read private key. Error: Failed to read private key.”
https://www.nomachine.com/TR05S10271
Try not importing the key at all inside the connection file, but instead placing the key on the device. Sometimes also generating new keys is helpful, as the problem is due to the characters used by base64 encoding for padding, breaking XML parsing. A new key has a different base64 encoding and thus can just work.
Britgirl
KeymasterI am not trying to get to the ubuntu pc from outside my network, just from this pc to my ubuntu.
It’s not clear how you are using NoMachine. Are you trying to connect to a NoMachine host on the same LAN as you, or over the Internet? It’s not clear from what you wrote previously. What I suggest you do is remove traces of other remote desktop products that you have installed. They could be interfering with NoMachine services and access to the ports that NoMachine requires in order to function correctly.
Then temporarily disable the firewall to see if it is that which is blocking the connection. On LAN you should be able to see the computer (pipe icon) you want to connect to in the NoMachine UI “Machines” panel provided you have “advertizing on the network” enabled on the server in the NoMachine server settings. Are you able to connect?
Edit, see this post from a user describing a similar issue https://forum.nomachine.com/topic/no-route-to-the-network-or-to-the-host#post-50575
December 6, 2024 at 18:57 in reply to: Black Screen in remote after cudnn install Ubuntu 24.04.1 LTS #51017Britgirl
KeymasterSend them over to forum[at]nomachine[dot]com, please use the title of the topic in the subject 🙂
-
AuthorPosts