Forum Replies Created
-
Posts
-
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.
Hi 🙂
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/AR06N00891I 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
Please see here: https://forums.nomachine.com/topic/no-audio-from-an-imac-with-mojave
Does it help?
Please tell us the specific Linux distro and desktop environment you are connecting to. Also logs would be useful. Please follow the guidelines here: https://www.nomachine.com/AR10K00697. You can send them to forum[at]nomachine[dot]com making sure to reference the title of your topic in the subject. Thanks.
Let’s check to see if the node is running. Open a terminal on the problematic Mac and run this command:
/Applications/NoMachine.app/Contents/Frameworks/bin/nxserver --statusIf the server is running, you’ll get this:
NX> 111 New connections to NoMachine server are enabled. NX> 162 Enabled service: nxserver. NX> 162 Enabled service: nxnode. NX> 162 Enabled service: nxd. NX> 162 Enabled service: nxhtd.What output do you get?
Hi, the logs were not complete and were also missing the affected session.
Please follow the steps in the document here on how to extract complete logs: https://www.nomachine.com/DT10O00163.
Have you updated the Ubuntu OS or the NoMachine package on the Linux box? We aren’t aware of any issues like this, but if you tell us the version of Ubuntu we can check it anyway.
If the problem comes back, let us know.
Thanks for the feed back Sissy! If you are interested in a more formal reply read this comment to another user about H.264: https://forums.nomachine.com/topic/much-faster-screen-updates-in-latest-version 🙂
Thanks kosak and graphixillusion. We’ve found the problem affecting specifically set-ups with large screens, so are in the process of patching. We’ll then send a new patched version (full binary) for testing 🙂
Check that you have one of the Terminal Server products installed e.g. Workstation, Terminal Server. You can do that by following the steps here: https://www.nomachine.com/AR07C00232.
If you have the free NoMachine product installed you will connect to the physical display of the remote computer. You say “it didn’t use to happen”. What product did you install beforehand?
More information about the free edition of NoMachine is here: https://www.nomachine.com/AR10K00700
Hi, if you send us the logs of the C1 machine, we can take a look to see why you can’t connect to that computer. To extract the full logs, please follow the instructions for the affected PC here: https://www.nomachine.com/AR10K00697
Send attachments directly to forum[at]nomachine[dot]com making sure to reference your topic. Thanks!