Britgirl

[Britgirl]

The logs can be attached here and they will remain public, or you can send them to our email address forum[at]nomachine[dot]com. Logs may contain IP addresses, usernames and computer names of the affected user sessions. It is possible to blank out the sensitive information before submitting for analysis. Thanks

[Britgirl]

Hi, thanks for those. Logs confirm an already known issue: https://kb.nomachine.com/TR02X11706 which also includes a temporary workaround. The fix is going to be included in NoMachine 10, coming soon.

[Britgirl]

Are these rootless sessions? We aren’t aware of similar issues and it would need a thorough investigation, something that is probably best done through the traditional support channel. It would be wise to update to a more recent version of NoMachine 8 first, if updating to version 9 is not possible, and see if that helps.

[Britgirl]

Can you send us the full set of logs taken from the host you are connecting to? Go to Settings > Server Settings > Security, scroll down and Take logs. Send us the whole file. You can send it to forum[at]nomachine[dot]com or attach here. If you are sending it via email, please use the topic of this title as the subject of your email. Thanks!

[Britgirl]

I just noticed you submitted some logs already, we’ll check those and come back to you.

[Britgirl]

Hi, we aren’t aware of issues with with ScreenCaptureKit on Tahoe.
Logs from the macOS server would also be useful. Go to Server settings > Security > scroll down and Take logs.

You could also try adding the -nosckgrab parameter in the NoMachine node.cfg file on the server side. In /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg, append DisplayServerExtraOptions "-nosckgrab", save, then restart the nxserver (Server settings > Status > Restart). Does this make any difference?

[Britgirl]

Hi,

first, on each of your internal servers that you want to access you should install a NoMachine server. We provide 3 different families targeting enterprise needs: in simple terms: Enterprise Desktop for access to the desktop, Terminal Server for Linux-only machines that lets you run multiple desktop environments on the same host, and Cloud Server which functions as a gateway to your fleet of NoMachine servers. Each server where you install one of these three requires a subscription for that product. You can reach these machines over IP or over Machine Id (NoMachine Network). Connecting over IP does not require any “user-side” subscription.

Instead,  if you would like your users to connect using NoMachine Network, then they will each require their own User Id, by creating their own account, and a Network subscription. Whilst we don’t currently support a “team licensing model” (e.g., just to give a basic example, one subscription for 4 users, 1 or 2 of which can connect through the Network service at any time), this is something we’ll support soon. However, you can still manage the Network subscriptions yourself now by creating your own account, purchasing 4 Network subscriptions, and then assign the Network subscriptions to other users (the users must still create their own accounts) from your User Area. You can unassign, reassign as you need, when you need. Doing it that way gives you control on who is using what. If a user leaves your organization, you can unassign any Network subscription by removing their User Id from the “assign” field. This does not delete their account, however.

Also take a look at the following articles: https://kb.nomachine.com/AR04X01355, https://kb.nomachine.com/AR06W01294.
There is also a useful article that puts all the FAQ about NoMachine Network in one place: https://kb.nomachine.com/AR04X01360

If you create an account, you get 7-days to try the Network service, and from your User Area you can generate your own evaluation licenses to activate the server product of your choice. Our sales team are ready to help if you have any more questions about what products to use based on your specific requirements.

[Britgirl]

Hi, we are aware of this problem and have already opened a Trouble Report. Please use this link to track its status: https://kb.nomachine.com/TR07X11889.

[Britgirl]

Users encountering this issue, please take a look at the topic submitted here for a possible solution: https://forum.nomachine.com/topic/video-tearing-glitching-caused-by-nvidia-driver

[Britgirl]

Hi, thanks for reporting this. I will add this topic as a link to the earlier one 🙂

[Britgirl]

Investigations that were done did not allow us to pinpoint specific system variables which are affecting the NoMachine UI. However, some improvements recently made could help, and we invite you to update to the latest version. If you are still encountering the same issue, please follow the instructions that were recently posted for a similar topic here: https://forum.nomachine.com/topic/nomachine-ui-stops-working-enabling-linux-for-windows#post-55834

And then reach out to us through the website, so we can continue through our traditional support channel. You can contact us using the following email address issues[at]nomachine[dot]com.

[Britgirl]

Investigations that were done did not allow us to pinpoint specific system variables which are affecting the NoMachine UI. However, some improvements recently made could help, and we invite you to update to the latest version. If you are still encountering the same issue, please follow the instructions that were recently posted for a similar topic here: https://forum.nomachine.com/topic/nomachine-ui-stops-working-enabling-linux-for-windows#post-55834

And then reach out to us through the website, so we can continue through our traditional support channel. You can contact us using the following email address issues[at]nomachine[dot]com.

[Britgirl]

Hi, NoMachine disconnects when the Mac goes into hibernation, and then reconnects when it wakes up. What you are seeing is the correct behaviour even though you didn’t physically disconnect and reconnect NoMachine.

Thanks for submitting the logs, they confirm what I wrote previously:

Info: Remote desktop resized to 3840×1200.
Info: Session window surface configured.
Info: Changing display mode to ‘viewport’.

Upon reconnection, NoMachine tries to apply the previous resolution before it disconnected, but can’t because the macOS desktop (not NoMachine) decided the resolution should be 3840×1200. So it switches to ‘viewport’ because the client has a smaller available resolution.

[Britgirl]

Hi, we’ve reproduced this and opened a Trouble Report here: https://kb.nomachine.com/TR07X11880. For the time-being you should use a different key for switching the layout (or a combination). Please use the link to keep track of the TR’s status. Thanks for reporting 🙂

[Britgirl]

Hi, thanks for those, they helped us to identify where the issue is. We are going to send you an updated library with a potential fix. Please download and install, the same as you did previously and let us know if it fixes the issue.

[Author]

Posts