Forum Replies Created
-
Posts
-
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.
Edit by Carin: If we decide to open a Feature Request, we will update this topic.
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:
https://www.nomachine.com/TR12R10006
If you want to receive a patched binary, contact us at forum[at]nomachine[dot]com.
Thank you for the report. We’ve opened a Trouble Report, we’ll include a fix in our next maintainance, you could subscribe to be informed when it’ll be released:
Hi. We’re reproduced the problem in our labs, thank you for the report. Just one difference: the problem appears when the client window is maximized, not fullscreen. Is that your case too? If window is actually fullscreen, how do you click the title bar?
Hi. We’ve opened a Feature Request to improve current client behaviour:
Hi! We’re currently working on a mobile release to update it to version 7, and we’ll check your reports too to be sure to improve DeX support. Just a quick question: how are you using DeX? Is it a Cable/Pad/Station connected to a monitor or a DeX for PC (on Windows or Mac)? Thanks.
Hi. Enter Display menu to enable “Resize remote display” option, in order to tell the remote desktop to change its size when the client window changes, then enable “Fullscreen on all monitors”.
We’ve also extended the description of the Feature Request to make these steps more clear.Sure. I’ll give it a whirl.
Please send an e-mail to forum[at]nomachine[dot]com by using the title of this post as subject, so we can send back the binary.
In the meanwhile we’ve documented the problem here:
Hi Pierre and Fred. 🙂 The issue appears to be on Windows, not Fedora. Would you like to test a binary fixing it?