Britgirl

[Britgirl]

There is no impact on performance and only only one port is used at a time. Reducing the range too much only increases the chance that all the ports in the range are busy, and in that case udp wouldn’t be used.

[Britgirl]

Thanks for following up and we’re happy to know you solved the issue.

For future use, and if you need a list of ports that NoMachine relies on, take a look at the following article: https://kb.nomachine.com/AR01L00770

[Britgirl]

You can use sudo /etc/NX/nxserver --history and also sudo /etc/NX/nxserver --history --verbose

--history
Display, Username, Remote IP, Session ID, Date, Status, Node, Type

--history --verbose
Display, Type, Session ID, Services, Depth, Screensize, Status, Session name, Username, Platform, Users, Date

Also sudo /etc/NX/nxserver --history --stats will give information about session numbers and users connected.

The is also “server statistics” in the Server panel of the UI (Settings > Status). This will give you information at a glance. All of the Enterprise configuration guides have a section dedicated “Session Management”. For example, here: https://kb.nomachine.com/DT07T00258#12. The Cloud Server isn’t mandatory, it all depends on what your specific requirements are.

In version 9, there are going to be improvements to the --history in general, making it easier for admins to parse this information for forensic reasons.

[Britgirl]

Hi, disable HW decoding on the Linux client. To do that exit the player (from the system tray) and follow the instructions here: https://kb.nomachine.com/AR07U01202, making sure to select option 3:

3) disabled HW decoding is completely disabled, the codec library for HW decoding is never loaded and the checkbox is grey out inside UI panel ()

Does that help?

Second, check for any core files or crash reports generated on the Linux client, and submit those.

Third, submit logs from both Linux client and Windows server. To gather logs, please follow the instructions here: https://kb.nomachine.com/DT07S00243

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

[Britgirl]

The current version is 8.13. The feature you are requesting was always scheduled for NoMachine 9, priority of which has been NoMachine Network (https://www.nomachine.com/network). Version 9 development is coming to a close now, so there’s not long to wait. Now that development on v9 starts to ease up, it has allowed us to concentrate on features, vital for our users, and swapping command/ctrl is one of them.

[Britgirl]

Hi, this is what the plan is for version 9. We are going to provide the following options: i) The default behaviour as it is now, which is that the Windows key is mapped to Command; and ii) the possibility to map Ctrl to Command and Windows key to Ctrl. By enabling the option ii), it means that pressing Ctrl-c or Ctrl-v on a Windows client will be mapped to Command-c and Command-v on the Mac server. Note that this new option could have side-effects on other shortcuts such as the shortcut used for cycling through application windows.

[Britgirl]

A final note, as I wrote earlier, we have already scheduled a maintenance release. We cannot however foresee differences between a beta, Sequoia in this case, and its final release (of September 16) which could lead to some incompatibilities with the NoMachine software, as has happened in this case with the release of the latest macOS version. For this reason we give ourselves a period of 30 days to make adjustments as written in the article I linked earlier. Problems reported for “Sequoia beta” have been addressed during the development of our release candidate, however those fixes are being revisited to make them suitable for macOS 15 just released. We will update the forums when we have more information.

Here is the related Trouble Report with the possible workarounds: https://kb.nomachine.com/TR09V11212

[Britgirl]

Hi Me, welcome to the forums.

So was this taken as a bug report as people were obviously testing with those pre-release versions?

I’m not sure what the question is but I can add that we take all users’ issues seriously, including users who test beta versions of supported operating systems. And of course we also test beta versions and use the provider’s beta phase to assess possible solutions for any problems that arise. Fixes are then implemented as quickly as possible and according to our release schedule.

What is the ETA for the fix now that this issue is active on production release of a widely used operating system?

NoMachine aims to become completely compatible within 30 days of a supported operating system production release (this is a general guideline, but we work to make that time as short possible, see the article I linked earlier). We already have a maintenance update planned early next week. That update is being finalized as I write, even at the extent of postponing the maintenance for a few days also to ensure 100% compatibility with Sequoia. As soon as we have more news, it will be posted here.

[Britgirl]

renatenickole, it seems you are referring to our legacy version (pre version 4) These commands are not supported.

[Britgirl]

Hi, if you don’t want the server component installed on your machines, try Enterprise Client. It’s free to download and use, suitable for users who only want to start connections to remote desktops (and not receive connections) https://www.nomachine.com/product&p=NoMachine%20Enterprise%20Client.

Or what you can do is install without starting the NoMachine Services automatically, see section 2.8 of this document for example, https://kb.nomachine.com/DT07S00246.

[Britgirl]

morozov, is your server headless? Enable debug and send us the full logs. Please follow the instructions here: https://kb.nomachine.com/DT07S00243

Also send us the logs in the directory in point 2 above.

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

[Britgirl]

psantucc

we’re unable to reproduce this behaviour despite several attempts and the logs you sent us indicate nothing strange.

1) can you tell us if the server is headless?

2) send us all the logs in this directory: $HOME/.nx/nxegl/

[Britgirl]

We have opened a Trouble Report which you can monitor at the following link:

https://kb.nomachine.com/TR03V11103

[Britgirl]

Hi,

is it possible to disable copy/paste function :

– from client (source machine) to server (destination machine) ?

– from server to client ?

Yes, it is possible in all server products, that means also the free version. Here some instructions to disable copy and paste, both directions: https://kb.nomachine.com/DT07S00233#22

 

Is it possible to create complex rules like:

“Allows copy/paste from server to client only if the client is in LAN” ?

“Disables copy/paste from any client not in LAN”

Rules, via “profiles”, are available in specific products of the Enterprise suite, namely all Cloud Server products, Terminal Server and Enterprise Terminal Server. By federating the smaller Workstations and Enterprise Desktops under one of the Cloud Servers, profiles can be propagated. How to do it? Below is an example, which blocks allows only 192.*.*.*  addresses.

$ sudo /etc/NX/nxserver --ruleadd --class feature --type client-clipboard --value no --address 10.0.*.*

$ sudo /etc/NX/nxserver --ruleadd --class feature --type server-clipboard --value no --address 10.0.*.*

[Britgirl]

You have the same overlapping issue like in the other topic mentioned above. To fix the overlap you can move the second screen to not overlap the other. For example, arandr will let you do this.

[Author]

Posts