Britgirl

[Britgirl]

Hi, not having a password is a problem. Having a password to log in remotely is essential. What you could is enable NoMachine Users DB and set create a user and password just for NoMachine usage. It won’t affect your system settings. So when logging in you use the NoMachine User pwd rather than your system account and (no)password. Take a look at this topic post: https://forum.nomachine.com/topic/connecting-to-nomachine-on-windows-requires-password#post-49194 which contains the instructions.

Otherwise, for more advanced users, you could try using key-based authentication, as explained here: https://kb.nomachine.com/AR02L00785.

[Britgirl]

I saw your request for the patch in another topic, https://forum.nomachine.com/topic/after-upgrade-to-ubuntu-24-04-1-lts-players-immediately-disconnects/page/3#post-50869. What you can do is send us the logs for the issue that you are experiencing, submit them here or send to forum[at]nomachine[dot]com, so we can check first whether your issue is related to the problem in the other topic.

Enable debug on the server side, then reproduce the problem. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

[Britgirl]

Hi,

I either receive endless connection restart messages, there is no desktop to connect to, etc…

There is a known issue https://kb.nomachine.com/TR05V11141 and the workaround is to use x.org rather than Wayland. This is of course a temporary workaround whilst developers work on a solution. It would be useful to see the logs from both the NoMachine Windows client and the NoMachine Fedora server. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. This would allow us to check if it is indeed the same issue as the TR I linked or something else (you mention multiple problems but without any other details about when they occur).

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Hi,

I spun off your issue because it appears to be a different one, and it’s better to keep this black screen issue separate from “player disconnects”.

I tried various thing but still the black screen persists

Did you try any/all of the tips explained here?

Connecting to Linux headless machines with NoMachine
https://kb.nomachine.com/AR03P00973

Have you tried disabling Wayland and using X.org?

If none of those worked, please confirm the desktop environment you are connecting to on the Ubuntu host (and that you have NoMachine 8.14 on both sides).

[Britgirl]

I don’t know what VPN you have installed on the MBP, but it’s strange that a VPN filter remains active even when the VPN is turned off. Thanks for letting us know anyway.

[Britgirl]

The issue could be caused by a missing dependency. Try installing the ‘zenity’ package.

[Britgirl]

It would also be useful to know more about:

OS and version on the side you are connecting from (client)
OS and version of the side you are connecting to (server)

Thanks.

[Britgirl]

On the machine you are connecting to, please disable hardware encoding in NoMachine. You do this by going into Server settings > Performance > unticking the box in ‘Use hardware encoding’ (https://kb.nomachine.com/DT07S00237#2.7). Then connect again.

[Britgirl]

Could something have changed on the Windows machine, server side? The player logs you submitted show the server is not reachable. Please check that everything is still set up as it was when it was working. You can use this guide to make sure that all the steps have been followed https://kb.nomachine.com/AR04S01122.

If that does not help, we will need logs from the Windows server. Enable debug and extract them using the instructions here: 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]

The logs don’t reveal anything useful to understand the slow performance.

Please update to the latest version and then also try tweaking the quality slider and resolution sliders to see whether performance improves. See the following document for more about those:

https://kb.nomachine.com/DT09T00266 (Fig 16)

[Britgirl]

You should definitely watch out for NoMachine 9, coming soon. A tool that only applies to NoMachine I don’t think exists 🙂 You could take a look at alt-tab-macos.netlify.app, though please note that we have not tested this and can’t guarantee that it will give the desired results.

[Britgirl]

Apologies for not updating you. The logs show that the player didn’t receive anything on the port where it reads the multicast UDP messages (to know the servers available in LAN). And we’ve previously confirmed that NoMachine is broadcasting correctly on the Macbook server. So something is happening in the middle, and in the middle there is either the network or a firewall which we have no control over.

Did you already try:

disabling the FW completely on your Ubuntu machine?
checking whether the Macbook Pro (2017) machine can see the Ubuntu host and the other Macbook?
checking whether the other Macbook can see the Ubuntu machine and the Macbook Pro (2017) ?

[Britgirl]

Maybe you altered a system preference? Is this the only key combination that is not behaving?

In the upcoming v9 we will be adding an option to swap Control and Command modifiers on the remote desktop. This new option in the NoMachine User Interface is intended to allow users to swap Control and Command modifiers, so that users connecting from macOS to Windows/Linux (or vice-versa) can comfortably continue to use their local shortcuts also inside the NoMachine session (Copy/Paste/Select all/Undo/Print/Search). When this option is not enabled, instead, the user has to use the remote modifier for applying keyboard shortcuts inside the NoMachine session.

In the meantime, you could check for a third-party tool that lets you change the Command+Tab to Alt+tab shortcuts. There are a few free options on the market.

[Britgirl]

You could be encountering an already known issue,

Only a part of the desktop is rendered on 4k monitors scaled at 150%
https://www.nomachine.com/TR11T10690

Is there a scaling factor applied in the display settings of the server OS? The logs would help us to confirm that. You followed the instructions correctly, maybe try gathering the logs from outside the virtual environment?

From a terminal you can also try running tar -zcf nomachineLog.tar.gz /usr/NX/var/log and share with us nomachineLog.tar.gz.

[Britgirl]

The screenshots were not attached. Can you submit them again?

[Author]

Posts