Forum Replies Created
-
Posts
-
Hi,
Is it possible that there are other applications using NoMachine’s port 4000? Is the host you are accessing configured as a node of an Enterprise Server maybe?Hi Thinker55,
To understand better we will need more logs from the server side. Reproduce
the problem and send to forum[at]nomachine[dot]com. Instructions about collecting logs you can find here:
https://www.nomachine.com/DT07M00098.Hi,
At the moment it’s not possible to change this timeout. You can disable UDP communication completely, but not a particular direction of the UDP communication.
Hi,
In most cases “The NoMachine service is not available” means that there is no NoMachine installed on the remote machine or the installed version doesn’t support SSH connections.
The nxplayer restart can be caused by a crash. Can you send us the crash report? It may be in the following folders:
/Libraries/Logs/DiagnosticReports
/Libraries/Logs/CrashReporter
/Users/Username/Library/Logs/CrashReporterSend any attachments to forum[at]nomachine[com].
Hi,
The logs don’t help us understand what might be happening. Please tell us what OS X version you have installed NoMachine on and what you are trying to connect to (OS and version). What is the error displayed in the nxplayer? Are you using NX protocol when connecting to free version?
Hi Tom,
If you want to forward microphone to the remote machine when you are connected to a session:
– you have to enable microphone forwarding (Mic in icon) in the menu panel (CTRL+ALT+0 or peel on the right top of the session window)
– you can choose a, different than a default, device in Audio settings (Mic in -> Change settings -> Microphone input)
– you should be able to record the chosen device from the NoMachine Microphone Adapter on the remote machineHi,
We need more information about the problem. Can you specify the Android version and device? Can you record and attach the distortions?To understand better we will need logs from the client side. Reproduce
the problem and send to forum[at]nomachine[dot]com. Instructions about collecting logs you can find here:
https://www.nomachine.com/DT07M00098.Hi, thanks for the report. The glitches seem to be a PulseAudio problem. You can try these workarounds:
– exit Iceweasel
– run PulseAudio tool: pavucontrol
– start Iceweasel and the videos should be working
– keep the pavucontrol runningor if you do not have pavucontrol:
– exit Iceweasel
– run PulseAudio tool, parec, in terminal:
$ parec –latency=20 –format=float32le –rate=25 –channels=1 –channel-map=mono -d nx_audio_null.monitor /dev/null
– start Iceweasel and the videos should be working
– keep the parec runningHello, it seems that provided passphrase is not matching the private key. Check out, in advanced options of the connection, if proper private key is selected. In edit dialog of the connection check ‘Reset saved preferences and password’ checkbox and try to connect again.
If this will not help, we can send you a debug library to check the issue.
We have opened a trouble report to track this issue:
https://www.nomachine.com/TR09L04536
NoMachine logs on Linux are filled up with errors
about Pulse Audio ServerA fix for this problem will be included in the next update.
In the meantime you can try to disable sound notifications
from the Server status GUI -> Server preferences -> Security
panel.@sshere, Did you have a chance to extract the logs?
Can you explain ‘reverting my AUDIO to the SPIF output’ problem? Is it enough to disable audio (start session, open Menu panel (CTRL + ALT + 0) -> Audio -> Disable audio)?
We will need also the server side logs. Please, send logs file to issues[at]nomachine[dot]com. Follow this article:
https://www.nomachine.com/AR07K00677@samo_dadela, after NX session starts, PulseAudio default source is changed to ‘nx_voice_out.monitor’. You can try to change or update KVM options to choose a proper PulseAudio source.