Forum Replies Created
-
AuthorPosts
-
Britgirl
KeymasterCheck your inbox ๐
Britgirl
KeymasterHi, 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 ๐
Britgirl
KeymasterHi 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!
Britgirl
KeymasterNikolas, 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.
Britgirl
KeymasterUpdate: from version 6.6.8 onwards, the most recent version of FFMPEG (4.1.3) is supported.
Britgirl
KeymasterHi, 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.
Britgirl
KeymasterThe 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.
Britgirl
KeymasterJust to let you know that our developers are still working on this.
Britgirl
KeymasterHello, 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.
Britgirl
KeymasterIt 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.
Britgirl
KeymasterAre 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.
Britgirl
KeymasterHi ๐
thanks for letting us know.
Having a desktop environment already installed is necessary, also when installing on headless machines. Most common Linux desktop environments are Unity 3D, GNOME 3, KDE’s Plasma desktop and lightweight ones such as MATE desktop (a fork of GNOME 2), Xfce and LXDE.
If you are new to Linux, you might find the following useful:
https://www.nomachine.com/AR04K00667
https://www.nomachine.com/AR06N00891Britgirl
KeymasterHi Hellcats, I’ve send you the debug package to download with instructions. Check your inbox ๐
Britgirl
KeymasterI thought I had already provided some input on this, alas I obviously didn’t hit the submit button. As Kroy wrote, NoMachine doesn’t many any changes to Network drivers whatsoever, so it’s very unlikely that NoMachine is the cause. The fact that you tried to restore the OS to an earlier version and it didn’t work is an indication of another underlying issue.
A good starting point could be to look at the MS website about the network connection issue: https://support.microsoft.com/en-ca/help/10741/windows-fix-network-connection-issues
Britgirl
KeymasterPlease see here: https://forums.nomachine.com/topic/no-audio-from-an-imac-with-mojave
Does it help?
-
AuthorPosts