Forum Replies Created
May 31, 2017 at 11:33 in reply to: Restrict NoMachine to listen on a particular interface #14933
Could you please explain what should be the effect of „rtlocalhost=127.0.0.1” ?
As far as I can tell, nxnode.bin is not listening on a pre-defined UDP port then (like e.g. “0.0.0.0:4500“). But this also means that the UDP connection can only be opened from the server side to the client side. So in case if that is not possible (e.g., due to firewall rules), then the UDP connection in the other direction (from the client to the server) will not work. Is my understanding correct?May 19, 2017 at 17:32 in reply to: Restrict NoMachine to listen on a particular interface #14853
Thnx for a hint! This option indeed works for us. However, if UDP is enabled then “nxnode.bin” is bound to e.g. “0.0.0.0:4500” (if port 4500 is used for UDP). Is there some way to restrict this as well?February 22, 2017 at 15:28 in reply to: Wait for application startup during the virtual session start #13837
Thnx for an advice. I did try UserScriptAfterSessionStart. But for me the NoMachine doesn’t wait for the script to terminate before the desktop is exported to the client side. So the script is still running after the NoMachine client shows the display. Am I doing something wrong there?
Ok, thnx for the info.
Thanks a lot! That indeed solved the problem with glitches! And the problem with sound delays seems to be gone if I switch from VP8 to MJPEG.