Britgirl

[Britgirl]

They are rather large. After sending them you can disable debug and remove them.

Logs contain usernames and IP addresses and this information can be removed beforehand if you prefer to do that before sending. I can send you the details via email to upload to the NoMachine Support log service we have for subscribed customers (read more about our privacy policy here https://kb.nomachine.com/AR05P00977 and how logs are handled).

[Britgirl]

Why does multiple screens affect the number of ports? Do you mean connections/multiple players?

Obviously having a single port in the range would affect the case you run multiple connections from the same client, as only one of them would be able to use UDP. There is also a (small) risk that an external app keeps that port busy.

[Britgirl]

Hi 4venger, you might be interested in the upcoming NoMachine Network feature in NoMachine 9, coming soon, which will let you see (and connect to) all your computers regardless of the network they are on. By adding them to NoMachine Network, which will be free to do, they will each be allocated a univocal Machine Id. Then all you’ll need to do is log in to the Network service on any device and add your computers to the Machines panel using their Machine Ids (just like you add a NoMachine connection today). There’s a brief introduction about what users can expect (give or take a few small changes): https://www.nomachine.com/network. Connecting to those computers using the Network service will require a Network Subscription, monthly or yearly, and you can continue to use the free version 🙂

[Britgirl]

Denying rules across the board is planned. In the meantime you can do it using following script:

#!/bin/bash
#
# CLASS can be one of: all|feature|service|session

CLASS=all;

if [[ $CLASS = "all" ]]; then

     CLASS=" -E feature|service|session";

fi;

TYPES=$(sudo /etc/NX/nxserver --resourcelist --class $CLASS | grep $CLASS | awk '{print $2}');

for i in $(echo $TYPES); do

     sudo /etc/NX/nxserver --ruleadd --class propagation --type $i --value no;

done

This script will systematically deny all propagated rules for the specified session class. After which, you can then add the specific, individual rules.

[Britgirl]

Can you show us the output of the xrandr command so we can check what resolutions are available to you?

When connected to the physical desktop, the maximum resolution you can get is the maximum resolution supported by the remote graphics card i.e the one on the Ubuntu host in your case. More about this is available here: https://kb.nomachine.com/AR02M00835.

You mentioned RDP which works that way because it is a virtual session. If you want to work with a virtual display with NoMachine and a higher resolution, you can try two things:

1) try launching NoMachine’s own framebuffer. So kill X (sudo init 3) and restart nxserver. NoMachine will create its own virtual framebuffer. You should be able to connect and change the resolution.

2) try the NoMachine Workstation. It’s available in the Enterprise section of the download area.
https://www.nomachine.com/product&p=NoMachine%20Workstation

[Britgirl]

Hi, version 7 is no longer available for download in the public repository. If you have a customer Id, you can reach out to the support team and ask for a download.

Balloon notifications are used to notify as well as prompt the desktop user to accept a specific function (e.g accept an incoming connection) and are a central security feature of NoMachine software. Whilst in version 7 it is possible to disable all balloon messages using the appropriate key in node.cfg, in version 8 the disabling of all balloon messages is no longer possible.

In v9, it will be possible to remove sensitive information such as IP address and username in the server GUI from the balloon notifications, so that more generic message will appear e.g., “A user is connecting to your machine”.

[Britgirl]

Check what value the system settings of Ubuntu 24.04 ‘Scale option’ is set to. Change it to 100. We are aware of a problem with scaling on server side, which you can monitor using the following link:

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

You could also try changing the view mode in the NoMachine Display panel to ‘Enable viewport mode’ or ‘Scale to window’. Alternatively, in the NoMachine menu panel open Display -> Change settings and try setting a custom resolution in ‘Use a custom resolution’ W/H).

[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.

[Author]

Posts