Britgirl

[Britgirl]

Hi Jon,

The free edition of NoMachine is for access to the physical display, so it’s the correct behaviour. Maybe what you are looking for is NoMachine Workstation from the Terminal Server family for Linux?  Check out the differences here: https://kb.nomachine.com/AR10K00702. The Workstation is available to download here: https://www.nomachine.com/product&p=NoMachine%20Workstation.

[Britgirl]

If no input is arriving on the Mac side, it could be a simple issue of permissions not set on the macOS system during installation of NoMachine. Go to System Settings > Privacy > Accessibility and then “+” and add NoMachine. If it’s already there, remove and add it again (see this article https://kb.nomachine.com/AR11Q01061). Then connect again from Windows.

[Britgirl]

When it happens again, please gather the logs from both sides.

[Britgirl]

Can you tell us the Linux distribution and what desktop environment it is, so we can verify?

[Britgirl]

The GDM issue could be this: https://www.nomachine.com/TR07S10316.

About the blurry screen connecting from Windows (your images may be too large for our upload tool, email is best):

– Right-click the NoMachine app shortcut on your desktop and select Properties
– Select the Compatibility tab
– Click “Change high DPI settings”
– Check the box “Override high DPI scaling behavior”
– Select “Application” from the combo under “Scaling performed by”

Does that help?

[Britgirl]

Hi, can you submit the screenshot to forum[at]nomachine[dot]com?

Also, when you try to connect to GDM as your desktop environment, what is the NoMachine message that you see?

[Britgirl]

Hi, this is a similar issue to a couple of other topics (see below) and we have opened a Trouble Report which you can see here: https://www.nomachine.com/TR03V11111.

No audio with 8.11.3: Linux server, macOS client

No sound forwarding (option to change settings is greyed out)

The fix is going to be released in 8.12.

[Britgirl]

Can you check whether the Command key (corresponding to the Windows key) actually gets pressed in Dragon? You can do this with Mac’s onscreen keyboard. Go to Apple menu > System Settings > Accessibility > Keyboard > Accessibility Keyboard.

[Britgirl]

Hi, which previous topic are you referring to? One you opened in 2020 is about macOS.

You say that from Windows you can connect to the Debian server without problems. We assume you are connecting to the same Debian server as when you connect from the Debian client. Right?

Can you submit a screenshot/screenshots of what you see when you try to connect from the Debian client? Are any error dialogs shown?

Logs from the two Debian machines would be useful. Please follow the instructions here to enable debug and then gather the logs.
https://kb.nomachine.com/DT07S00243. Send them directly to forum[at]nomachine[dot]com. Thanks.

[Britgirl]

Biglia,

In safe mode nxplayer starts normally, after reboot it doesn’t work again.

You also said that NoMachine works well on the other Windows computer you tried it on. So it’s something specific on that affected PC which you will have to debug. This can be done by checking the services and software (not started in safe mode) and disabling/uninstalling them one by one, and trying to open nxplayer each time. Could it possibly be an antivirus creating a false positive? It’s worth checking. The other user in this thread said Bitdefender had been preventing nxplayer from opening.

[Britgirl]

Hi, macOS Sequoia is available as a Preview only (and just out less than 24 hours ago), so there could be some further updates still from the Apple developers before they release the final stable version. Thanks for reporting, we will be testing ourselves as well in the meantime. Can you provide more details about how NoMachine failed with Parallels?

[Britgirl]

Hi, logs suggest a possible network issue in that both client and server sides record a disconnection. However, the logs don’t match i.e it appears you took them at different times. So to be extra sure, we need you to submit new logs. Clean out old logs, reproduce the problem and then submit the new client and server logs like last time 🙂

Also useful, the output of nxserver --status run in a Windows CMD prompt on the Windows server you are connecting to would be useful as well. Open the CMD console as administrator and input "c:\Users\All Users\NoMachine\nxserver\nxserver.exe" --status. Paste the output here.

[Britgirl]

Logs show:
1945 2016 2024-06-06 21:05:11 234.255 TcpConnector/TcpConnector: ERROR! Error is 99 ‘Cannot assign requested address’.
Error: Connection to ‘localhost:25001’ protocol ‘TCP’ failed.

Did you add localhost to the /etc/hosts file as suggested by Fisherman? We will be checking installing NoMachine on GCP/Docker, also to make sure our current documentation is kept up-to-date (https://www.nomachine.com/accessing-your-remote-desktop-on-google-cloud-platform-via-nomachine) and extended.

[Britgirl]

Hi, the next maintenance 8.12 will indeed add support for Intel’s VPL coming soon.

[Britgirl]

Please include the Linux distribution details and desktop environment to keep everything in one topic. The attachments were not accepted, so the best thing to do is to zip them up and send to forum[at]nomachine[dot]com. Thanks!

[Author]

Posts