kroy

[kroy]

Hi.

It’s not quite clear to us what the problem is. Windows aren’t reopen after creating a new session or it’s not connecting to the physical session?

[kroy]

It doesn’t look that problem is on NoMachine. It seems more like a network issue. Can you send your predefined session config to forum[at]nomachine[dot]com that we could analize if there is any problem on configuration?

[kroy]

It is not advisable to make changes to the binary files. Please uninstall, remove NoMachine directories and install again. If problem with black screen shows again – use this tip: https://www.nomachine.com/AR03P00973

[kroy]

Hi.

Can you describe more details. What kind of USB dongle is that? Is it a modem, a network card that is supposed to allow access from outside the network?

[kroy]

Which pulseaudio version do you have? Is there any other audio framework runned there (for example phonon which is default on KDE)? Can you reverse changes in the node.cfg then enable debug (pulseaudio and NoMachine), reproduce and send it to forum[at]nomachine[dot]com?

To enable debug on pulseaudio:
– edit /etc/pulse/daemon.conf and change:

; log-target = auto
; log-level = notice

to:

log-target = auto
log-level = debug

Execute:

pulseaudio -k
pulseaudio -D

Check logs and send to us file with output:

cat /var/log/syslog* | grep -i pulse > /tmp/pulseaudio_logs.log
How to collect server side NoMachine logs automatically:
https://www.nomachine.com/DT10O00162

[kroy]

Please follow the article: https://www.nomachine.com/AR02L00785.

“If you have generated the SSH key pair on Windows, for example by using PuTTYgen, be sure it’s in OpenSSH format or convert it. To do that choose the key file in the PuTTYgen main window. Then go to Conversions->Export OpenSSH key to export your private key and save it.”

[kroy]

Thanks for the report. You can follow this trouble report: https://www.nomachine.com/TR03R09568 and use the notify me tool to know when a fix is available.

Are you sure there were other physical outputs earlier? NoMachine is not invasive and not able to remove other modules from output list. You can shutdown NoMachine (sudo /usr/NX/bin/nxserver --shutdown) and respawn pulseaudio (execute pulseaudio -k and then pulseaudio -D). Is there sound on the machine desktop (physically, without involving NoMachine)? If not there won’t be in the NoMachine session neither.

However audio in the connections will work when you create virtual desktop or if it’s free or NoMachine Enterprise Desktop version on the headless machine.

[kroy]

There isn’t a fix available yet, but you can use following workaround for this problem:

1. Check and set Gateway Port (or set manually NXUPnPPort in etc/server.cfg).
2. Remove all files from ProgramData/NoMachine/var/db/node/externalports/ location.
3. Restart nxserver (click on NoMachine icon on the system tray -> Show the service status -> Restart the server -> Continue).

[kroy]

We cannot reproduce such problem. What NoMachine version do you have? What is the Desktop Environment and Display Manager on the CentOS host? Are there any more logs on the server side? You can enable and collect them automatically, please follow the instructions here: https://www.nomachine.com/DT10O00162

[kroy]

You can disable the automatic startup NoMachine at boot time (https://www.nomachine.com/AR11P01005). You can always install NoMachine Enterprise Client https://www.nomachine.com/download-enterprise#NoMachine-Enterprise-Client.

If you just want to disable access to your local desktop – check this tutorial – https://www.nomachine.com/disabling-access-to-your-local-desktop.

[kroy]

We couldn’t reproduce this problem. Which Desktop Environment do you use and which screensaver? If you try to lock screen manually inside the session are you reproducing this behaviour?

[kroy]

Screenshot indicates that there could be wrong starting command. What is the output of the command grep DefaultDesktopCommand /usr/NX/etc/node.cfg. Please enable debug, reproduce problem and send logs to forum[at]nomachine[dot]com (all that should be done on the server side). There are instructions how to enable and collect debug logs automatically: https://www.nomachine.com/DT10O00162. Make sure you put the title of the topic as your subject.

cloud Kali machine

Can you write from which cloud service are you using?

[kroy]

Hi. Please try solution from that article: https://www.nomachine.com/AR03P00973. Turn of X server and restart nxserver.

sudo service gdm stop
sudo /usr/NX/bin/nxserver --restart

To disable X server permanently you can execute command: sudo systemctl disable gdm3.service.

[kroy]

Please try again to configure port forwarding. On Port Range Forwarding field set 4000 as Start and End Port. Then you need to choose router’s external IP and port 4000 to connect over internet.

[kroy]

If it’s your local network – you should use local IP and port 4000 (please take a look: https://www.nomachine.com/getting-started-with-nomachine). External IP and port (in your case 25.90.xx.xx:20564) should be used if you are connecting over internet. If this is your case and there shows connection timeout error it could be some router settings problem.

Can you check if your router supports UPnP? Please verify also if 25.90.xx.xx indeed is your external IP (for example there: https://www.whatismyip.com/). If not – it looks that you have a double NAT networking. It means that NoMachine has to go through two or more routers. In that case you need to set up separate port forwarding rules on each device. If IP is the same you need to manually configure them: https://portforward.com/help/doublerouterportforwarding.html.

It will be possible to skip these steps with NoMachine Network feature (https://www.nomachine.com/FR07J02731) which is coming soon.

[Author]

Posts