Britgirl

[Britgirl]

@ mcvitas, please check your email inbox. I have sent you further instructions on how to get logs to us. Thanks!

[Britgirl]

Did you already check that the box “Don’t advertise the computer on the network” is not flagged on the Mac machines?

The NoMachine MDNS service uses the UDP port 5353. Check whether the firewall on those Mac computers is maybe blocking access to it.

[Britgirl]

Hi, we’ve logged your interest in testing a native package of NoMachine for Windows ARM. It’s certainly not a technical limitation to port NoMachine to run natively on Windows ARM, and it’s definitely something we’d like to offer in the future. Adding support for new platforms in our future roadmap is purely a business choice. Although the Windows on ARM segment offers more choice in terms of hardware available (it wasn’t like that a couple of years ago), it still shows a somewhat lacking ecosystem compared to Intel and AMD products on the market. In the meantime, we’re keeping an eye on Windows for ARM increasing popularity and if we have a pre-release package available for testing, we’ll announce it here 😉

[Britgirl]

We reproduced the same behaviour. But this seems to be more of a problem of Mint and not NoMachine. It can be fixed by setting the environment varible in node.cfg:

DefaultDesktopCommand "env XDG_CONFIG_DIRS=/etc/xdg/xdg-xfce:/etc/xdg:/etc/xdg /usr/bin/startxfce4"

This should be enough to get the correct desktop GUI. Since the desktop-user was already logged and probably you had “wrong” settings saved, you need to reset it with:

rm -rf /home/desktop-user/.config/xfce4

and then logging in to your NoMachine session should give you the desired DE.

[Britgirl]

This is not caused by NoMachine software. This is because the virtualized OS X does not recognize the original hardware, so you should check your hypervisor settings.

This example may help depending what you are using: https://stackoverflow.com/questions/70186036/icloud-unsupported-device-when-installing-macos-big-sur-in-vmware

[Britgirl]

I assume you are asking about two users connecting to the same virtual desktop session? By default, users connecting to a host where a NoMachine Terminal Server product, e.g Workstation, has been installed can share their NoMachine virtual desktop with other users.

If one of the two users has already created the virtual desktop session, the other user can authenticate and select “All desktops”. The list of available sessions will be shown. See the screenshots I have attached.

Further reference:
How to share a NoMachine virtual Linux desktop with other users
https://www.nomachine.com/AR07P00993

Attachments:

1. 

   6.png
   

2. 

   7.png
   

3. 

   8.png
   

[Britgirl]

There was a typo in the previous reply. Could you try with the following and tell me if that works:

rm -rf /home/type_username_here/.config/xfce4

then follow the steps as before (log in to desktop using NoMachine physical session, logout, create virtual desktop session)

[Britgirl]

Hi, by installing Enterprise Desktop on the device you want to access, you get unlimited connections to the physical desktop available there. This means that unlimited users can connect to that computer and they will see, and share, the same desktop. The Enterprise also supports access via web, users can also connect by using their browser.
Aternatively, users that want to connect can install either the free edition of NoMachine or the Enterprise Client package on their own devices.

Enterprise Desktop is available in evaluation for 30 days here: https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Desktop.

In order to get started with browser-based access, please take a look at the guide here:
https://www.nomachine.com/getting-started-with-web-based-remote-access

You might also want to take a look at this article:

Differences between NoMachine Enterprise Desktop and the free to download NoMachine package
https://knowledgebase.nomachine.com/AR07L00808

[Britgirl]

Hi, firstly I fixed the status of that FR, it should not say “Implemented” but “Dismissed”. One of our developers will answer your other question 🙂

[Britgirl]

Hi, this is a serious issue we recently found in the USB driver we distribute on the Mac. Please check the Trouble Report and follow the instructions to apply the workaround. We already fixed the problem. It will be released in the next Maintenance Update, due in the next few days.

USB forwarding does not work properly on macOS Monterey
https://knowledgebase.nomachine.com/TR12S10425

Update 28/1: We are waiting to receive the necessary Entitlements from Apple in order to release the next scheduled maintenance which includes the fix for this issue. Without these Entitlements we are unable to provide signed drivers and unsigned drivers will not be loaded by the system. As soon as we have received the appropriate permissions from Apple, we will release the software update.

[Britgirl]

Got them thank you!

[Britgirl]

We have not received any logs 🙁

Are you able to send them again?

For the authentication failure issue it would be better to start a new topic about that with all the details and the specific error message you are getting.

[Britgirl]

Hi, I’ve just forwarded it on to you again. It was originally issued from the Forums backend. I’m not sure what happened there. Let me know that you got it.

[Britgirl]

The instructions for enabling and gathering logs manually are correct 😉

Try the shorter method “Collect server side logs automatically”

https://knowledgebase.nomachine.com/DT11R00182#1

Command nxserver --debug --enable allows you to enable debug logs for all components: nxserver, nxnode, nxwebplayer/client and the display agent in one go. It must be executed on the machine where the problem occurs. In your case, this is on the Windows machine server-side.

To do it on Windows, open a CMD console as administrator and move to the ‘bin’ folder under the NoMachine installation, e.g:

cd %ProgramFiles(x86)%\NoMachine\bin
nxserver --debug --enable all

Connect and reproduce the problem. When you’ve reproduced the issue, you then do:

cd %ProgramFiles(x86)%\NoMachine\bin
nxserver --debug --collect

The log archive is named as: NoMachine-log-.zip (e.g. NoMachine-log-2022.01.19-9.15.01.zip) and stored in: %PROGRAMDATA%/NoMachine/var/log/archives.

[Britgirl]

Hi,

it seems the Player logs were missing. And we would need to see those. In the UI on the computer you are connecting from:

– Make sure that the box to not delete log files on exit is flagged
– Connect to the server and reproduce the problem.
– Compress the user’s home/.nx directory containing logs.

[Author]

Posts