fisherman

[fisherman]

to block second user to connect please enable

Server –> Security –> Require permission to let remote users connect

 

Attachments:

1. 

   NoMachine-Security.png
   

[fisherman]

I am not sure what NoMachine package currently you are using, but I assume it is NoMachine free version. Free version allows only one connection to the desktop running on the host.

By design when you are using the same username for second connection previous connection is disconnected.

Possible solution is to use different username for the second connection if you are using a product that allows multiple connections to the same host, such as Enterprise Desktop.

[fisherman]

It was Client side issue.

[fisherman]

Issue is solved in the NoMachine version 7.1.3.

[fisherman]

Please open in session Menu panel and in input tab enable “Show remote cursor pointer”.

see attached image.

Attachments:

1. 

   input_remote_cursor.png
   

[fisherman]

Can you tell us what is your desktop environment installed on Server?

Additionally, please check following forum posts related to Manjaro Linux

https://forums.nomachine.com/topic/connection-fails-on-headless-client

[fisherman]

This is not NoMachine issue, it is protection module in Kaspersky application.

Please check following link https://support.kaspersky.com/10947 and enable nxnode.bin in the trusted applications.

 

Attachments:

1. 

   kaspersky.png
   

[fisherman]

This issue looks like problem with loading fonts. Can you check MacOS console for possible errors related to NoMachine or font loading.

Additionally can you please compress and upload here $HOME/.nx.

[fisherman]

Can you try to grab the keyboard input in the session. You can do it in the in-session menu-panel or by pressing Ctrl + Alt + K to toggle the keyboard grabbing.

[fisherman]

Hello,

There is a feature request https://www.nomachine.com/FR09P03687 that could help for your case.

If I am not wrong, when you are mentioning that you dont see NoMachine server in client i am thinking that you need to enable mDNS port as well inside of firewall.

Here is the article about NoMachine used ports: https://www.nomachine.com/AR01L00770.

[fisherman]

Hello,

You are trying to download old version not available for current download.

Please see the following forum post to download latest nomachine version
https://forums.nomachine.com/topic/my-successful-story-in-setting-up-nvidia-driver-on-aws#post-27729

[fisherman]

I understood it is virtual machine as you have mentioned “Linux VM (Ubuntu 20.04)”.

If you Linux machine is without monitor attached probably Linux X server if forcing one resolution. Possibly you can attach hdmi dummy dongle or you can let NoMachine create a display on the fly rather than using physical one.

Try to turn off lightdm or gdm:
sudo service lightdm stop

and then restart NoMachine server:
sudo /usr/NX/bin/nxserver –restart

[fisherman]

Hello Predz,

What i have noticed is that you are having the Ubuntu virtual machine:
– I would recommend to install hypervisor drivers and verify if your machine is able to use different resolutions.

Or You may try to switch off your X server and let NoMachine create display for you. You can stop or disable you Display Manager, and create a connection to that desktop.

Visit this link for more information about the configuration:
https://www.nomachine.com/FR10L02842

[fisherman]

Can you try to disable “multi-pass encoding” in session Display Settings of NoMachine Menu Panel. https://www.nomachine.com/DT04O00140#5.1

[fisherman]

This is not related to NoMachine software and i think that you can find all information on Elastic Search website. I can present one possible idea how all works.

1. As a first thing you should install Filebeat (https://www.elastic.co/downloads/beats/filebeat) on each NoMachine server which logs have to be monitored.
   Filebeat monitors the log files, collects log events, and forwards them to endpoint. Settings of logs input and endpoints outputs have to be filled in filebeat.yml – you should include there all paths of log files
   NoMachine store most logs in /var/log directory, ex. /usr/NX/var/log on Linux hosts. More information about NoMachine logs you will find https://www.nomachine.com/AR10K00697, which has to be synchronized with ES and determine also where new logs will be sent (output). It can be a directly elastic search endpoint depending on what will be done with collected data next and how it has to be visualized in Kibana but, in most cases, you will want to transform this data to a more readable format for ES, ex. JSON. In that case, the best choice for your endpoint will be a Logstash.
2. Logstash is a data processing pipeline and a part of ELK Stack (https://www.elastic.co/downloads/logstash). It can be installed on the same host where Elastic Search and Kibana.
   To process data sent by Filebeats you have to create Logstash pipeline with sections input, filter and output. Input will a Filebeat in our case. The filter section is a place to determine how logs have to be processed. Output as an Elastic Search endpoint.
3. Setup your Elastic Search and Kibana, create index patterns for corresponding NoMachine logs data.
   If everything is configured correctly you should be able to find indexed new logs entries in Kibana “Discover” or Kibana “Management -> Index Management” sections.

[Author]

Posts