Forum Replies Created
Possible that there is problem with wrong cookie. Execute command on that foreign host:
xauth list :0
It should show similar output:
ubuntu-mate-18/unix:0 MIT-MAGIC-COOKIE-1 035d99d99c612bc76350167aeeb7be63
Then go to cloud-server machine and add IP foreign machine to /etc/hosts and set hostname from xauth (in this example: “ubuntu-mate-18”). Now add server again, using that hostname (or IP).
nxserver --serveradd ubuntu-mate-18 --label pc1 --foreignApril 3, 2020 at 08:32 in reply to: NoMachine sound card with support of sample rate above 44kHz #26484
We created feature for adding support for audio at 48kHz sample rates, you can find there: https://www.nomachine.com/FR03R03960. You can sign up to the ‘notify me’ in order to know when it has been implemented.
Did you tryd to reproduce problem after restarting nxserver or system reboot? It looks that somehow your physical desktop wasn’t detected by NoMachine so it creates a new one like it was headless. It could happen in situation where X server on the system was started much later than NoMachine server. Is it headless system and desktop was started manually? If yes, nxserver should be restarted (
sudo /usr/NX/bin/nxserver --restart) after desktop startup.
Which NoMachine verson you have – is it Workstation Evaluation or the free NoMachine version? Are you sure you are connecting as the same user which is owner of the desktop with the opened applications? Can you tell me the steps you take to connect? Perhaps you can submit the screenshots of the phases?
To connect over internet you have to enable UPnP or open port manually in the router settings. Please refer https://www.nomachine.com/AR11L00827. In the article you have instruction how to enable UPnP in the NoMachine server.
Check also https://www.nomachine.com/getting-started-with-nomachine – section: Using NoMachine for remote access to a computer over the internet.
If you want forward port manually you should pass traffic to port 4000 (NX protocol), 22 (SSH protocol on Linux/MacOSX) or (4022) (SSH protocol on Windows). Follow the router instruction to know how to do that (guide you can also find in the internet, for example from there: https://portforward.com/netgear/wndr3700/).March 24, 2020 at 15:30 in reply to: NoMachine sound card with support of sample rate above 44kHz #26147
Can you check if setting maximum quality of the audio helps (https://www.nomachine.com/DT10O00156#6.1)?March 23, 2020 at 11:50 in reply to: Linux PC/Android 10 smartphone – Authenthication failed #26082
the APP as not “designed” for this Android version, can this be the reason?
Even with this message you should be still able to connect. Do you use password authentication? Are you sure that you used correct credentials? Are there unicode characters? Were you able to connect there earlier? Please create a new connection to connect. Verify also if you can connect from other host to the same server, maybe problem is on server side.
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?
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?
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
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?
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
log-target = auto log-level = debug
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:
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.”
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 -kand 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.
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).