Forum Replies Created
-
Posts
-
Hi, the logs from the server side would be useful. Please follow the instructions here: https://www.nomachine.com/DT10O00163
You can send them directly using the address forum[at]nomachine[dot]com making sure you include the title in the subject. Thanks.
To everyone following this topic, we are aware of issues on certain models of Chromebook (it is not limited to Pixelbooks as we previously thought) and we are continuing investigations. Until we are able to reproduce the same strange behaviour which will allow us to open a Trouble Report, this topic will be archived. Any updates will be posted on the forums.
This is the Trouble Report related to the issue reported here: https://www.nomachine.com/TR05Q09323. You can sign up to receive a notification when a fix has been officially released in an upcoming update. In the meantime, we will reach out to you individually with a hotfix.
Hi, thanks for the new set of logs.
They show us that there is a sudden termination of nxnode upon connection, but unfortunately they don’t provide useful hints as to why that is happening. So, I need to ask you to send us some additional information.
Please check for core files and then send us a backtrace (after having reproduced the problem again). To do that, follow the instructions here: https://www.nomachine.com/AR09L00810
You can attach the files and send them to us directly as you did last time. Thanks for your collaboration 🙂
Hi dlp_1,
we received the logs but unfortunately you enabled them when some of the processes were already running. So I have to ask you to restart the nxserver reproduce and send logs again (restart can be achieved by executing /usr/NX/bin/nxserver –restart). Thanks!
Nikolas, can you send us logs from the Linux host?
Please follow the instructions here: https://www.nomachine.com/DT10O00163. You can send them directly to forum[at]nomachine[dot]com making sure to include the title of your topic in the subject. Thanks.
Hi, NoMachine gives you access to the physical display of the remote OS (physical or virtual machine). However, it is not a hypervisor, but you can install it on one since it works out-of-the-box with solutions such as VMware, Virtualbox etc etc. If you have a computer running, for example, 2 separate virtual machines, you could install the free version of the NoMachine on both of them. From the connecting client you would be able to connect to both as separate NoMachine sessions.
Additionally, there is the Terminal Server range (Linux only) which lets you run multiple individual Linux desktops and or applications on the same host.
The logs didn’t reveal much. Can you tell us the server-side version of NoMachine you are connecting to?
Also, do you see the desktop, even for a moment, before you get disconnected?
Server-side logs with debug enabled are useful. Please follow the instructions here in order to enable them, making sure you reproduce the problem before gathering up the logs.
Hello, what NoMachine product and version are you connecting to on the server side?
Any logs can be sent to forum[at]nomachine[dot]com making sure you reference the title of your topic in the subject.
It could be related to this:
Cannot connect to Ubuntu physical desktop when Wayland is enabled
https://www.nomachine.com/TR04Q09228Try the workaround and let us know.
The download pages report it is built to for Ubuntu’s up to 18. Is a build for 19 available
Please consult the article:
Which operating systems are supported?
https://www.nomachine.com/AR07H00568which explains in brief what our policies are for adding new releases of supported OSes, distributions and versions.
Are you able to share the logs with us?
Detailed instructions on how to collect logs are described in following article:
How to gather debug logs for support requests
https://www.nomachine.com/DT10O00163Send logs to forum[at]nomachine[dot]com making sure to use the topic’s title in the subject.