Bilbotine

[Bilbotine]

Hello Steve,

If you need a command to know how to check if nxserver is operative, it is nxserver --status.

If this is not what you need, can you please give us more details on what you need to do and on which platform ?

[Bilbotine]

Hi Strider,

In order to investigate, we need logs – can you please gather them with debug enabled?

In order to do so, follow the instructions in this document: https://kb.nomachine.com/DT07S00243. It’s valid for v9 as well.

Reboot the server, or logout and log back in.

Gather logs again, and send them to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email.

[Bilbotine]

Hello Steve,

Can you answer the following questions, to help us understand better what the issue can be:

– Can you try to connect to the same server using another username ?

– Can you confirm that the server you are connecting is SBTS  ?

Thank you!

[Bilbotine]

Hi lmvdr,

Thank you for the additional info.

We could provide you a package with a possible fix, if you are willing to try it?

If you agree, please send us an email to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email, and we’ll send a link to the package, as soon as it’s ready.

[Bilbotine]

Hi Peter,

I presume you, with “make visible”, mean “how do I connect with NoMachine”. To connect you need either an IP address or a Machine Id, the latter case if you added the machine to NoMachine Network, but in any case your VMs must be “visible” on the LAN, so an IP address on the LAN must have been assigned to them.

[Bilbotine]

Hi weezul,

Thank you for reporting it.

This issue will be fixed in the next update.

[Bilbotine]

Hi lmvdr,

We are aware of the problem and are actively working on a resolution.

In the meantime, could you please confirm whether your Mac is equipped with an Intel processor?

[Bilbotine]

Hi SimpleTechGuy,

We are not able to reproduce the problem on our side, unfortunately.

From what we understand, you are connecting to the arch, thescreen lock is inside and there is a crash player with the session to that arch – or do you have the player on the arch and you are connecting to another host, and that player crashes after screen lock ?

Can you give us more details to continue the investigation ?

 

[Bilbotine]

Hi ShayMu,

Can you specify which version of NoMachine you are using, what OS versions, and also send us the logs so we can investigate deeper ? Please send the via email, to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email.

If needed, here’s the procedure to collect the logs: NoMachine – Collect Server And Client Logs Manually – Knowledge Base

[Bilbotine]

Hi Haidit,

Please try to install xfce; xfce physical session should work, even without a monitor plugged.

On our side it works with NVIDIA Jetson Nana, it should be the same on your model. You can check our article “Tips for using NoMachine on NVIDIA Jetson Nano” for more info: https://kb.nomachine.com/AR02R01074

[Bilbotine]

Hi graphixillusion,

Thanks for the logs, we checked them but we need more info.

Can you please gather the logs with debug enabled? In order to do so, follow the instructions in this document: https://kb.nomachine.com/DT07S00243. It’s valid for v9 as well. Reboot the server, or logout and log back in. Gather logs again, and send them.

Thanks!

[Bilbotine]

Glad the issue is solved, tashin ! 🙂

[Bilbotine]

Hi tashin,

It looks like you have artifacts on the session, but only on linux. Please try to disable the hardware decoding in the session: Menu>Display settings>Modify>”Disable client side hardware decoding”

Let us know if it solves the issue or not!

 

[Bilbotine]

Hello Steve,

First, sorry for the delay in answering.

Whilst we don’t have a specific article dedicated to SELinux, NoMachine does not require any special configurations and installs out-of-the-box. All our tests are with SELinux enabled, so with the standard default settings of SELinux.

Best regards

[Bilbotine]

Hi cameronpoe01,

“when I try to log in, and it prompts me for a username and password” – Please see if these instructions help, on your computer:

1. Launch the NoMachine User Interface from Programs menu or Applications and right click on a connection. Choose ‘Edit connection’  to access connection settings.

2. Be sure that NX is the selected protocol in the drop-down menu.

3. Go to the Configuration panel and choose ‘Use key-based authentication with a key you provide’, click on Modify.

4. Select the private key

5. Back to the previous panel and click on Connect

The client will prompt you for username and passphrase. If the key has no passphrase, the client will only ask for the username (there is no passphrase input field).

 

If you followed these instructions and the problem persists, it can be that it is caused by the option ‘Import the private key to the connection file’ that is checked in the client UI.

As a workaround, please uncheck the option ‘Import the private key to the connection file’ in the UI. Selecting that option is necessary only if you need to move the connection file to a different place and you need to carry on also the private key. Oherwise it’s not necessary to select it.

Please let us know if the issue is solved !

Best Wishes,

[Author]

Posts