Britgirl

[Britgirl]

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.

https://www.nomachine.com/DT10O00163#1.1

[Britgirl]

Just to let you know that our developers are still working on this.

[Britgirl]

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.

[Britgirl]

It could be related to this:
Cannot connect to Ubuntu physical desktop when Wayland is enabled
https://www.nomachine.com/TR04Q09228

Try 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/AR07H00568

which explains in brief what our policies are for adding new releases of supported OSes, distributions and versions.

[Britgirl]

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/DT10O00163

Send logs to forum[at]nomachine[dot]com making sure to use the topic’s title in the subject.

[Britgirl]

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/AR06N00891

[Britgirl]

Hi Hellcats, I’ve send you the debug package to download with instructions. Check your inbox 🙂

[Britgirl]

I 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]

Please see here: https://forums.nomachine.com/topic/no-audio-from-an-imac-with-mojave

Does it help?

[Britgirl]

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.

[Britgirl]

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 --status

If 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?

[Britgirl]

Kosak and Graphixillusion, you should have received an email from us with a download link 😉

[Britgirl]

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.

[Britgirl]

Logs received thanks (both times 😉 )

[Britgirl]

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.

[Author]

Posts