Britgirl

[Britgirl]

Hi,

“given that it worked until my trial license expired” – are you referring to the NoMachine Network trial license (7 days)? This will have let you connect to any of your machines (once added to NoMachine Network) using their Machine Id.  Now that the Network trial is expired, you can continue to use the IP address to connect to your computers as you used to do.

(Btw you didn’t need to reinstall NoMachine to remove Network-related configurations. You can disconnect the machine from NoMachine Network, that’s all. Then it stops being reachable with its Machine Id)

“not sure how to proceed to get this new laptop “on the network””

You are using 192.168.44.1 to connect, which is a LAN-based IP address, and not for external access, so we’re assuming that client and server machines are on the same home subnetwork.

First, rightclick the connection, and click ‘Edit’, open the Host combo box and verify that the selected IP address matches the subnet of the client. Another thing you can check is the nxserver is running on the computer you want to access (Settings > Server > Status).  Can you show us a screenshot of the Machines and Edit panels? If you don’t wish to submit them here, you can send them via email to forum[at]nomachine[dot]com.

[Britgirl]

Hi hys17, in that case, it would be useful to see the logs from the affected M2 Ultra server. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1. Attach them here or send to forum[at]nomachine[dot]com. Thanks!

[Britgirl]

Hi, there is a similar topic which you see here: https://forum.nomachine.com/topic/nxplayer-fails-to-open-on-win10-2#post-50834

We have never been able to find anything wrong on our side despite exchanging logs and dumps and long hours of investigation. One of our lead developers summed up what the results of analysis (from the link above): “After all our attempts to reproduce the issue and to progress in the debug through static analysis, we can certainly say that this problem is completely out of our control. A possible reason why it happens with NoMachine only (at least from what you’ve seen so far) is the sequence of DLLs loaded that badly interact with one or more configurations and third party services on your machine.”

[Britgirl]

Hi Milika, the logs you submitted a few weeks back didn’t show any errors. So we confirm that software encoding is being used instead of HW encoding due to the high resolution. Using Tahoe will show the same thing. As Bilbotine mentioned, we are planning to add support to use HW encoding for resolutions higher than 4k.

 

[Britgirl]

Thank you all for your valuable feedback on applications manifesting the same behaviour.

We’ve been in contact with Apple since some time, as we’ve been tracking the beta release to prevent unexpected issues. When we noticed the problem reported on a tested beta version we were initially confident on a quick macOS fix, since we only use well documented, secure and public API to synthesize the events on the system. However when the bug was confirmed on the release candidate, which was extremely close to the official release, we knew we would disappoint our users. Unfortunately, sometimes dealing with OS vendors and new versions can be little bit hard.

The workaround we proposed, which is of course temporary, is activating an old and deprecated API for events (do you see the funny side?). It’s not perfect, we know. Rest assured we’re doing everything possible to close this issue quickly. Thank you for your patience.

 

[Britgirl]

Hi, we found a workaround, please try it and let us know.

Edit /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg on your Tahoe machine and add: DisplayServerExtraOptions "-oldeventapi 1". Then restart NoMachine with sudo /etc/NX/nxserver --restart

(from https://forum.nomachine.com/topic/unable-to-edit-system-settings-on-mac#post-54165)

[Britgirl]

I sent you a link to a patched library. Please try it and let us know if it solves the problem.

[Britgirl]

Anyone in this thread can write to us and we will provide them with the download link of a 9.1.24 with the fix applied. The fix will be in the next maintenance release.

[Britgirl]

Er1c4rd

Let’s check first that it is the same issue. Please tell us what “nothing works” means. Is it just input (mouse and keyboard) does not work or are screen updates not working? Or is it something else? This specific issue described in this topic occurs on Linux Mint 21, what is your Linux distro and version on the NoMachine server? Can you also clarify what you mean when you write “logs me in through HyperV” 

[Britgirl]

Hi, currently names are not shown but we are going to fix that in the upcoming maintenance 🙂

[Britgirl]

Can you tell us the Linux distro and version?

[Britgirl]

Hi, please update to v9.1.24. The corresponding TR is: https://kb.nomachine.com/TR06W11382.

[Britgirl]

Hi, you should update to the latest version both sides. It would be useful to know OS details both sides, and whether you are connecting to the physical display or a virtual display. Logs from both the player and the server would be useful.  You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298

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

https://kb.nomachine.com/DT08U00298#1.1 and #1.2.

[Britgirl]

No, it’s not officially released yet. Checking with the NoMachine Support team, I can see that you raised a Report Issue and recently received the fix in a private download. The fix will be the next upcoming release.

[Britgirl]

This was a feature we had inserted into a major new version, in this case targeting NoMachine 9, rather than as a minor. Implemented such important enterprise features in older versions is not an incentive for users to update 😉  More information about supported versions is available here: https://kb.nomachine.com/AR06P00985

[Author]

Posts