Britgirl

[Britgirl]

Did you run “kextstat | grep nx” before the sudo commands or after having executed the sudo commands?

[Britgirl]

Hi, please submit the server side logs which didn’t attach to forum[at]nomachine[dot]com making sure you reference the title of your topic in the subject of your email. I extracted the partial excerpt of log that you included in your topic as a separate txt file because it was quite long. What we need is the complete set of server-side logs.

Thanks.

 

[Britgirl]

It’s not clear whether you’re trying to connect with public key, or mapping ssh port. In any case, the best thing for you to do is send us the logs from the non-working Windows server (the one you are not able to connect to). Follow the instructions here and then send them to forum[at]nomachine[dot]com making sure you reference the title of the topic in the subject of your email.https://www.nomachine.com/DT10O00163#1.

Then from the client side, either the RPi4 or the working Windows host, send us the .nx folder. https://www.nomachine.com/DT10O00163#2.

[Britgirl]

We’ve opened a Trouble Report which contains the workaround I provided earlier:

AD mobile accounts cannot create sessions on macOS at the first login if they cannot access their home
https://www.nomachine.com/TR04R09659

[Britgirl]

Send us the full set of logs from the server side and we can take a look to see what’s happening. We’re not able to reproduce this behaviour which is very strange, as Mth suggested.

Follow the instructions here https://www.nomachine.com/DT10O00163 and then submit them to forum[at]nomachine[dot]com making sure you put the title of the topic as the subject. Thanks!

[Britgirl]

Hi,  we ordered one and will test it. Watch this space for updates on our findings.

[Britgirl]

This is a known bug.

https://www.nomachine.com/TR12P09035.

Please use the ‘notify me’ service to receive an email when a fix has been released.

[Britgirl]

Looks like you don’t have enough disk space. What you need to do is have a clean of your server and make some space on your server host.

System requirements necessary for NoMachine software products are provided on the download pages of each product, so for example, Terminal Server, https://www.nomachine.com/download/download&id=55, and also in the relative Installation Guide, “Prequisites” section. For TS we indicate general guidelines of 1 GB RAM and 195 MB free disk space.

NoMachine software is installed by default in /usr/NX so you must guarantee that the partition where you have installed it has the amount of space that we indicate. If you can’t clear up space on that partition for whatever reason, you can install it in a different location (/opt/NX) on a different partition, see the Installation and Configuration Guide paragraph 3 for further details about that https://www.nomachine.com/DT04O00139#2.3. Simply make sure that the new location on the alternative partition has enough space.

[Britgirl]

Ref. https://www.nomachine.com/DT02O00123#3.3
NoMachine Cloud Server – Installation and Configuration Guide
Par. 3.3. Advanced Configurations for NoMachine Servers’ Hierarchy

Add Enterprise Desktop to Cloud Server by forcing the ‘tunnel’ method. To do that, execute on the Cloud Server host:

nxserver --serveradd IP_of_ED --forward-nx-methods tunnel
nxserver --serveradd IP_of_ED --forward-ssh-methods tunnel

Does this help?

[Britgirl]

Sudo would have worked. Anyway, I would rather say that Kroy gave you a reasonable proposal by suggesting you to uninstall and then reinstall given that previous attempts to provide a solution hadn’t worked, and that you didn’t submit the logs (twice we asked over these past weeks). NoMachine installs 99% of the time out-of-the-box including on virtual machines regardless of the hypervisor. On occasion, when an installation has been altered for whatever reason, or the OS is not the manufacturer’s default OS that NoMachine is expecting, an issue might occur. Reinstallation can help, although it’s not clear from what you write whether you actually reinstalled NoMachine. We’ll consider this case closed.

[Britgirl]

Hi, sorry for the late reply. We are in the process of checking whether NoMachine can be used with this particular distribution and will update the topic with our findings soon.

 

Updated June: further investigation revealed that this would require a custom build of NoMachine (via Professional Services). Please contact our sales team to see what your options are and provide details of your set-up and user numbers.

[Britgirl]

This is happening because indeed NoMachine tries to access a home directory in order to create the .nx directory but the directory doesn’t exist yet and so NoMachine receives a permission denied message. If it’s dynamically created after that, the user can then log in to the GUI.

A way round this is to edit the NoMachine cfg file on each Mac server:
/Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg

Find there line:
#UserNXDirectoryPath "" uncomment it by removing “#’ and in “” put the path to some directory which is permitted for all users. It could be /tmp for example or any other created directory with permissions at least 666 or even 777.

i.e
UserNXDirectoryPath “/tmp”

[Britgirl]

NoMachine Network is the feature you need. This will avoid having to enable port forwarding on the router.

You can tick the box in the feature request to be notified when it is released: https://www.nomachine.com/FR07J02731

[Britgirl]

There is an article which contains some guidelines for sizing a NoMachine Cloud Server multi-server setup and benchmark tests for v. 6

https://www.nomachine.com/AR02Q01015

[Britgirl]

Logs show that you are now logging in with a username oem@Zenith which doesn’t exist.

2020-04-23 15:03:05 047.001 20656 NXSERVER WARNING! User oem@Zenith doesn't exist in system.
2020-04-23 15:03:05 047.172 20656 NXSERVER WARNING! NXLogin: Cannot retrieve absolute username for user: oem@Zenith.
2020-04-23 15:03:05 047.419 20656 NXSERVER WARNING! User oem@Zenith doesn't exist in system.
2020-04-23 15:03:05 047.715 20656 NXSERVER Previous message repeated 1 time
2020-04-23 15:03:05 047.792 20656 NXSERVER WARNING! NXLogin: Cannot retrieve absolute username for user: oem@Zenith.
2020-04-23 15:03:05 048.033 20656 NXSERVER WARNING! User oem@Zenith doesn't exist in system.
2020-04-23 15:03:05 048.149 20656 NXSERVER WARNING! NXLogin: Cannot retrieve absolute username for user: oem@Zenith.
2020-04-23 15:03:05 048.366 20656 NXSERVER WARNING! User oem@Zenith doesn't exist in system.
2020-04-23 15:03:05 048.838 20656 NXSERVER Previous message repeated 1 time
2020-04-23 15:03:05 048.913 20656 NXSERVER WARNING! NXLogin: Cannot retrieve absolute username for user: oem@Zenith.
2020-04-23 15:03:05 049.183 20656 NXSERVER ERROR! Authentication with 'NX-password' from host '192.168.1.15' failed. Error is 'Wrong password or login'.
2020-04-23 15:03:14 110.278 20688 NXSERVER ERROR! Authentication with 'NX-password' from host '192.168.1.15' failed. Error is 'Wrong password or login'

The best way to proceed is to do the following:

1) in a shell/terminal on the Linux server host, find the username using the command (run it in the terminal):
whoami

2) test the username and password in command line on the Linux host:

$ /usr/NX/bin/nxexec --auth
Username:  your_username
Password: your_password

The best way to check is to use the same credentials you are using to login to that Linux host.
If you are using oem@zenith then try zenith\oem (format DOMAIN\username). If it’s ‘oem’, then use that.

If nxexec --auth is successful, it will provide system groups where the user belongs.
Then you can use these same credentials in the connection GUI to start the connection.

If nxexec reports an error it means that user username and password are wrong.

[Author]

Posts