Forum Replies Created
-
Posts
-
Hi, I’m not sure what you’d like to achieve in terms of running the LDM after the XFCE desktop session starts. Maybe try with #UserScriptAfterLogin “” and in the server.cfg, not node.cfg? Also check your permissions, and ownership of the effective user. This ‘afterlogin’ script is executed as user nx, so you need admin privileges.
More about custom scripts is available here:
Server Automation Interface: some examples to use custom scripts triggered on server/node events
https://kb.nomachine.com/AR02L00787and any of the guides of the Enterprise products. Here’s the link to the Enterprise Desktop guide (like the free version but with more features) https://kb.nomachine.com/DT10R00171#11.3.
At the moment it’s not possible for us to indicate a time-frame. Right now our priority is NoMachine 9.
We can tell you the Client Hello Extensions, though we would be interested in knowing why you are asking. We use the very minimum to support our case. It’s not the purpose of NoMachine to implement an extensible TLS system, but to implement NoMachine. If there is an extension that is not included, and which you consider a requirement, please tell us what it is and we can evaluate whether to add it.
Extension Type: 0x000A (supported_groups)
Extension Type: 0x000B (ec_point_formats)
Extension Type: 0x000D (signature_algorithms)
Extension Type: 0x0016 (encrypt_then_mac)
Extension Type: 0x0017 (extended_master_secret)At the moment we don’t have plans to add support for AVP. It’s an interesting use-case but a rather niche one.
Could you try adding this to the node.cfg file?
DisplayAgentExtraOptions “-alteventapi 1”
Locate the node.cfg file, edit it by adding the above line, then save. Restart the server.
There are no keys recorded by xev, maybe the application didn’t have the focus? You have to keep the cursor on the xev window to make them appear. Can you try again in that way?
Can you also tell us if “Grab the keyboard” is enabled in the Player settings? (Settings > Player > Input)
This seems similar to another topic on the forum: https://forum.nomachine.com/topic/stuck-on-desktop-not-shared-after-updating-to-8-13-1 where we didn’t receive logs from the user.
We are unable to reproduce the issue despite several attempts. Can you submit the logs, first enabling debug, then reproducing the error?
You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Submit the logs to forum[at]nomachine[dot]com making sure to include a reference to this topic. Thanks.
Hi, this is unusual.
I’m not sure if its related, but I did notice that even plugging the Pi directly into my router still did not give me the speeds I was expecting when testing with SpeedTest.net. I get 100mbps up and 180mbps down. With the same cable, switch, etc on another computer I get my full ISP’s speed…a gigabit up and down. Maybe there’s something wrong with the Pi’s ethernet? I tried WiFi and its even worse, of course.
Can you send us the session statistics? Start a session from the RPi to a Windows computer, open the menu (Ctrl-Alt-0) and go to Connection, then click Take session statistics. (More about this is documented here:https://kb.nomachine.com/AR02N00875. Then, for completeness, start a session from Windows to the RPi and do the same again. Zip them up and post here.
Another thing, what distribution is the RPi4 using and what desktop environment is it?
Thanks.
sudo /etc/NX/nxserver --restartthrough the command line is of course ok. I gave you the GUI-based option 🙂Hi,
inside the session, from the Windows client to the Linux server, can you open the xev tool and check what is actually being printed when you press the spacebar on the Windows machine? Is the spacebar the only key which doesn’t work?
FYI I have removed the image which shows “Desktop not shared” because it contains sensitive information.
Please tell us Linux distribution and version, desktop environment (LXDE, Gnome, KDE, something else?), and attach the exact message you see when you try to connect.
Hello, thanks for pointing out the articles, we’ll be checking them to make sure they are updated. About TLS, version 1.2 still is a reliable and widely used standard in the corporate world, Of course, whilst it’s obviously favourable to use the latest version, the move to TLS 1.3 is something we are already working on, as low priority.
This sounds like a permissions problem. Go to accessibility and screen recording permissions, remove nomachine/nxnode, then restart the NoMachine server (server settings > status > restart the server). Then go back to macOS System Preferences accessibility and screen recording and add permissions for the NoMachine application again. Check this illustrated guide on how to do this https://kb.nomachine.com/AR11Q01061)
Hi, the development roadmap is no longer in the public domain. Indeed they log the evolution and design of our software and are documents that go into extreme detail. There is a public section for Trouble Reports where we publish bug reports, the workarounds available and eventual closure.
Please send us debug logs from the computer you are connecting to. You should enable debug and then reproduce the problem. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Ziomario, the NoMachine app for Android/iOS functions only as a client. You cannot use it as a server. This means that you won’t be able to connect to the Android device with NoMachine.
The IP address you see is a session file from an earlier session. But you won’t be able to use that session file to connect to Android, for the reason I just mentioned. You should delete the session file, editing the port to try to connect to the Android host which cannot accept connections will have no effect.
Instead, regarding the unusual crash, if it continues, please make sure you are using the latest version (which I assume you are but you didn’t mention it) and submit the logs as I mentioned earlier.