Forum Replies Created
-
Posts
-
Try this command:
nxplayer --session <NXS file> --new-sessionDepending on the client OS, you can make this automatic by double clicking an NXS file or script.
If you have access to the NoMachine server verify that the ConnectPolicy key enables the ‘autocreate’ mode, in the file server.cfg. You can also check the ‘autocreate’ value in client logs, by looking for the file ‘connection’ in your $HOME/.nx directory.
When the virtual desktop is not automatically created, do you see other running sessions on the server? They’re listed in the same panel where you can find the “New desktop” button.
Node and server configurations cannot help you in this case, because they only affect the client when it connects to the NoMachine server. If you have control over the client you could change connection file permissions to be read-only, or create a bunch of scripts which could, for example, restore the connection file when the NoMachine client closes or the computer reboots.
Thank you very much for the information, we’ll investigate it and check if there is something we can do on our side. And kudos for the finding, it was not an easy one! 🙂
Hi. I’d be grateful if you can report after running the following tests.
What happens if you press the ‘g’ key while the issue occurs? Does it stop or it has no impact at all?
If the issue goes on, open the On-Screen Keyboard (from Windows accessibility apps menu), verify that the NoMachine window has the input focus then click the ‘g’ key, close the virtual keyboard and verify what happens.Hi.
Are you using the most recent NoMachine version?
What do you mean when you say you’re using a virtual display?
Do you’ve applications like password managers running in background?
Next time the problem occurs, press Windows + X and select “Command Prompt (Admin)” from the context menu. In the command prompt window execute the commandtasklist > procs.txtand send the file procs.txt to forum[at]nomachine[dot]com.
Thanks.Hi. Those are the favourites connections, they’re stored in $HOME/.nx/config/player.cfg. You can either change the CFG through a script, or just start a connection once to have it added to the list.
Hi. Would you like to share some details about what you’re trying to achieve? Running the wizard with pre-configured preferences is not possible because of the nature of a wizard (which is supposed to guide you through the creation of a new configuration), but I’m sure we could find a solution to your needs by using some bash scripting or by designing together a feature which could be useful also for other users. We would just need to know why you can’t use network broadcasting, what is the operating system running on clients, the list of configurations you want to customize at each client execution, and so on. Any details will help. 🙂
Hi kosak. Could you try again to attach the nxtrace.log file, or send it to forum[at]nomachine[dot]com please?
Hi. Small update just to notify that we’re tracking this problem with the following Trouble Report:
https://www.nomachine.com/TR02Q09131
You could subscribe to be notified when it’ll be released.
The new behavior is that it loaded fine the first time, and even got past authentication to the NX server. Then it froze when trying to connect to my virtual desktop. Now I can’t do anything besides launch the app; it just shows a black window until I kill it.
Could you please check the CPU usage when this problem occurs?
Does the web/browser client work well on Chrome OS? The issue I’ve had with other web-based remote desktop solutions is that certain keyboard shortcuts (like alt-tab) aren’t captured, so you can’t use them on the remote end.
Yes, it does work, but capturing the system keyboard shortcuts is a limitation for us as well. You can work around it by using the virtual keyboard, which is far from being handy but I had to mention it anyway. 🙂
Unluckily Chrome OS 72’s new Android is not (yet?) available on all Chromebooks, so this makes the debugging a little bit harder. What do you see when trying to start the NoMachine application?
As far as I can say from your latest screenshot you’re connecting to a physical desktop, so available geometries are limited by what I said initially:
When connecting to the physical desktop, possible resolutions are the ones made available by the hardware and drivers.
You can’t set 2560×1440 because your remote desktop doesn’t support it.
When connecting to the physical desktop, possible resolutions are the ones made available by the hardware and drivers. If you’re creating a virtual desktop, you can either enable the ‘Resize remote screen’ option in the Display menu (open the menu with Ctrl + Alt + 0), or set a custom resolution in Display settings.