Forum Replies Created
-
Posts
-
Please try using pavucontrol for streaming audio. Open pavucontrol, go to playback, choose Applications and find an entry with your software. There should be a button with audio device – you could change it and check if it helps.
If your application is not on the list it means that it is not using pulseaudio.
Workaround may not work in every case. We strongly recommend to install the latest version of NoMachine to check if the problem still appears.
Can you tell which specific software you are using? Is there possibility to change default output device on the software?
Might network latency be the issue? Latency is around 15ms.
It’s not high. Everything should work correctly.
Hello.
Can you tell us little bit more about your case? I guess you have free version so you are using NX protocol to connect – right? Which login method did you choose – password?
We couldn’t reproduce such problem in our labs. Please enable debug, restart nxserver (
sudo /usr/NX/bin/nxserver --restart), reproduce the problem and send logs from server to forum[at]nomachine[dot]com. Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098#1. Please tar also player logs on client side at the time when problem appears. It’s.nxfolder which is placed in home directory. Send this file and output ofcat /etc/pam.d/nxcommand.Can you verify – for example on site whatismyip[dot]com – if IP from NoMachine GUI is your external IP? For “connection refused” issues you should refer article: https://www.nomachine.com/AR09O00937.
We need to take a look on logs to see where is the problem. Please enable UPnP again and enable debug on server side as well (https://www.nomachine.com/DT07M00098#1). Restart nxserver (
sudo /usr/NX/bin/nxserver --restart) and execute commandsudo /usr/NX/bin/nxserver --upnpmap. Logs from server side send to forum[at]nomachine[dot]com. Please attach also output of the commandsudo /usr/NX/bin/nxserver --upnpstatusand information about your router model.It looks that port 4000 is already used on server host. You need to change port for that program or change port for the NoMachine. Here is information about default ports used by NoMachine: https://www.nomachine.com/AR01L00770. To change NX Port click nxclient monitor on tray -> Show the server status -> Server preferences -> choose NX service, click Configure and change the port. After that restart nxserver.
You can monitoring sessions by using
./nxserver --historycommand (https://www.nomachine.com/DT07M00090#7.1.). It will show the complete list of sessions, including those that have been cleanly terminated or failed.We didn’t receive any logs. Is nxserver is running after restart? Can you enable debug, restart nxserver (sudo /etc/NX/nxserver –restart), reproduce problem, collect logs from server and client side and send them to forum[at]nomachine[dot]com? Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.
Did you uncomment line? Can you paste here
grep DesktopAuthorization /usr/NX/etc/server.cfgcommand output?Maybe after server.cfg changes you have select the ‘Require permission to let remote users connect’ checkbox in the nxclient options and it’s interfering?
If you were able to reproduce problem – can you try disable XBESClientUI service and tell us the result of the test?
We couldn’t reproduce such problem. Can you enable debug, restart nxserver (
sudo /usr/NX/bin/nxserver --restart) and if problem appears – send logs and ~/.xsession-errors to forum[at]nomachine[dot]com. Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.Please enable debug (uncomment and set SessionLogLevel 7 in the /usr/NX/etc/server.cfg), restart nxserver (
sudo /usr/NX/bin/nxserver --restart) tar logs (it’s in the /usr/NX/var/log/) and send them to forum[at]nomachine[dot]com.Send also output of the commands:
sudo /usr/NX/bin/nxserver --upnpstatus and ifconfig -a.You can restart nxserver by using special button in the nxclient monitor options. Click on the NoMachine icon in the tray. Choose “Show the server status”. Then click on “Restart the server” button.
If you prefer using command line – open cmd as an administrator. Navigate to the %ProgramFiles%\NoMachine\bin (if you install NoMachine in default folder) and execute
nxserver.exe --restartcommand.Are you sure that system is rebooted. In received logs we can see processes started in June 16. Can you show output:
who -b? Isn’t any minimized nxclient window on panel on any desktops? If you could not find any to fix problem kill process with number 8062 (root 8062 0.1 0.1 104180 8864 ? Sl Jun16 182:37 /usr/NX/bin/nxclient.bin –post progress –fd 4 –reopen).We weren’t able to reproduce problem. Are you sure that you set DisplayMonitorNotifications 0 on server side? Maybe you didn’t restart nxserver after changes (
sudo /usr/NX/bin/nxserver --restart).Logs could help. When you reproduce problem – please pack ~/.nx folder folder on server side and send it to forum[at]nomachine[dot]com.
Its a virtual desktop and NoMachine version is NoMachine_5.3.12_5 and ubuntu14.04.
It looks that you have NoMachine free version so you probably mean remote desktop, so it’s physical – not virtual desktop.