Forum Replies Created
January 20, 2021 at 15:42 in reply to: ClientSession: Failing reason is ‘The session negotiation failed.’. #31390
Hi. Do you mind sending whole logs directory where you’ve found that file to forum[at]nomachine[dot]com? We might need also server side logs, but let’s try to grab as much info as possible from the client first. Thanks.
Please, what is the iPadOS version you’re using?
You could contact us at forum[at]nomachine[dot]com if you want to get a binary fixing the issue. We’ve documented it here:
Hi. Can you please send for debugging client side logs (%USERPROFILE%\.nx) and the output of the command
xrandr -qexecuted in a session, after trying to enable the multiple monitors fullscreen? Mail everything to forum[at]nomachine[dot]com. Thanks.
Hi. I’m testing Manjaro 20.2:
– Copy the original .desktop file with
cp /usr/share/applications/NoMachine-player-base.desktop ~/Desktop/nomachine-session.desktop
– Change Exec line of new .desktop by adding the option
– Double click the .desktop file to start the session
– Right click the NoMachine icon in the task bar and select “Pin”
From now on any new nxplayer icon is grouped with the one I’ve pinned in the bar.
Could you share how you’re doing it?
Hi, sorry for the delay. The most effective way to correctly reset the desktop resolution consists in doing it when all clients are disconnected. However if you want to change it without disconnecting, just open the Display menu panel and select a different resolution.
Hi. On some Chromebook models the Android container freezes because it doesn’t really like our app! 🙂 If you can sideload an APK get in touch with us at forum[at]nomachine[dot]com, so we can send a testing version. However we’re completely focused on an update to our mobile version, so expect the fix to be released soon.
Hey there! This is an old problem we solved, but some OS changes caused it to pop up again. Please try this: enter Settings > General > Keyboard and turn off Smart Punctuation.
We’re completely focused on a new mobile version now, so expect a fix for it to be released soon.December 31, 2020 at 17:09 in reply to: Authentication failing when unlocking to change server preferences #31085
Hi jhusker. What’s the output of the command
id <your username>executed in Terminal?
I only want to use the client feature on this laptop.
You can read this article to know how to disable the server from Terminal:
Whenever server status display “Server is not running”, NoMachine’s services (nxplayer.bin and nxclient.bin) open port and listen incoming connections.
If we want just to use it as a client, why do NoMachine have to listen connection ?
When there are no sessions running (i.e. you’re not connected to a NoMachine server), nxplayer and nxclient open ports listening only on localhost interface so they won’t accept connections from external IPs. They’re used for inter-process communication through authenticated connections and execute only user level operations.
If one or more sessions are running, some ports could be required by services. You can read detailed information here:
Hi, sorry for the delay. Currently there is not a way to do it, but we’re evaluating a good graphical solution to allow users to choose whether timestamps should be changed or not, and maybe also configure the file permissions. I’ll update the thread soon with a Feature Request link.
Hi Babok. We’re troubleshooting the issue, it looks like the client can’t retrieve the correct server status.
By the way, editing the player configuration will not help to do what you want, it just affects how GUI panels are shown to the user. If you want to be sure server is turned off, just check the NoMachine tray menu: if you don’t see the entry “Quit NoMachine service” then it means server is not running. In the contrary case you can also quit the service from the menu, and choose whether you want to start it at next reboot or not.
Thank you for the report, we’ve documented the problem here:
If you want to receive a patched binary, contact us at forum[at]nomachine[dot]com.
Hi. We’re checking the issue, I’ll follow up shortly.