Forum Replies Created
-
Posts
-
Hi Mr.X.
The file player.cfg is the right one to modify in order to use different directories than default ones, the only condition is that those paths exist.
The command line option selecting a different CFG file is ‘–config’:
nxplayer --config <path to CFG file>Hi blabj.
The connection configuration flow has gone through a lot of design changes based on feedbacks and usability tests, so what you see now is what the majority of users asked for. This doesn’t mean it is perfect, so new use cases are always helpful to evaluate how to make that flow more flexible.
First of all, how it works. The client skips configuration steps each time there is only one choice. When the connecting user has no sessions running on the server and the filter is on “My desktops”, the configuration moves on virtual desktop type selection. From this dialog you may go back and select ‘All desktops”, unless the type is stored in the configuration file or the server only offers one virtual desktop type, because in such conditions the virtual session starts right away. While this workflow is ideal for administrators wishing to make life easier for users, it might be a problem for you.
If you wish to use the same connection to do both virtual desktop and desktop sharing, then I’d suggest to not save the desktop type in the configuration (by checking the box “Save this setting in the connection file” in the type selection dialog).
You may try this product:
NoMachine Web Companion
https://www.nomachine.com/product&p=NoMachine%20Web%20CompanionIt does exactly what you wish to do, the only difference is that it also ships a complete NoMachine Client, so users won’t need to manually install it.
Installation and Configuration Guide
https://www.nomachine.com/DT09K00053&dn=Hi cyconical.
As you said, the only useful feature (so far) to achieve what you want is the ‘–exit’ option. We’re planning to improve the support for clients running in kiosk mode, but that will require configurations on client side.
If you’re sure your clients are on Linux, you may distribute a modified version of the client startup script which could append the ‘–exit’ option, so the feature would be triggered each time the user starts the session by double clicking your NXS file.Hi pkats15.
Did you reboot your host after installing NoMachine? If you did it but the problem is still there, please get logs as explained in the article
https://www.nomachine.com/DT04M00076#3
and send them to forum[at]nomachine[dot]com.
Thanks!Hi trinn.
Currently NoMachine doesn’t allow to have a window for each monitor. Anyway don’t be discouraged! 🙂 We’ve in our plans some changes for a better support to multiple monitors in fullscreen mode, when both client and server have multiple displays. When this change will be implemented, extending it to work in windowed mode and have one window per monitor should be easy.
Hi alex.
The file transfer service cannot be used in a custom session. We’re discussing a way to correctly integrate seamless windows and file transfer, but I cannot offer a work around right now.
As a further choice you may use the disk or USB sharing services, your application will see a directory/disk on the client just like if it was on the server and vice versa. Are you referring to these services when you talk about “attach a drive” feature? In such a case we can find a workaround for the Qt file dialog problem.
By default we use ‘kdialog’ (on KDE) or ‘zenity’ because they’re better integrated with the system. Is it possible that none of them are installed on your host? What’s the Linux distribution where you need to browse the file system?My only recommendation is to have the key sequence be CTRL+N or ALT+N. I switch monitors all the time and pressing all three keys is a bit awkward.
You can configure them by using the Shortcuts button in the Input settings dialog.
Hi cacophony.
We’re still digging into the information you’ve sent. In the meanwhile you may download NoMachine 5.0.47 introducing keyboard shortcuts to switch current monitor.Hi dmingram66.
I’d like to be sure you’ve the same problem reported by albe, could you please send Diagnostic Reports to forum[at]nomachine[dot]com? Thanks.Hi noetus.
We’re testing different configurations to reproduce your issue, so far with no success.My workaround is to start NoMachine on the primary monitor, connect to server, set fullscreen to off, set display resize to off, move NoMachine to secondary monitor, set fullscreen to on, set display resize to on, and log in. However, though this usually works, it isn’t guaranteed to.
Does the same problem occur if you keep fullscreen and display resize disabled?
Could you send a screenshot of your ‘Screen Resolution’ dialog to see how your monitors are arranged?Hi idux.
Could you please help by retrieving some logs? This is the list of commands to execute:– Open Terminal
– tar -czf log.tar.gz .nx/M-*
– tar -czf system.tar.gz /var/log/system.log
– ls -l /Applications/NoMachine.app/Contents/Frameworks/bin > dir.log
– ps -ef | grep nx > ps.logSend all the highlighted files to forum[at]nomachine[dot]com.
Thank you!Hi norcalwingman.
We’d like to examine logs of your authentication attempts. After it fails, please enter the directory $HOME/.nx and save all directories with prefix ‘M-‘ by using this command:tar -czf logs.tar.gz M-*
Send the archive logs.tar.gz to forum[at]nomachine[dot]com.
Thank you very much for your help.Hey motto, this is just to tell you that we’re still checking the problem. I’ll let you know something as soon as possible.
Hi albe.
Please check this, the workaround explained there should help you:
A crash occurs when executing a call to network API on OS X 10.11 El Capitan
https://www.nomachine.com/TR10M06094