Forum Replies Created
-
Posts
-
The setting DisplayGeometry sets the resolution used by the X server when it starts, and it is kept unless the client asks a different resolution.
Normally settings configured on server side take over those configured on the client, but in some cases the client has priority. The geometry is very specific for each client configuration, and forcing it on server side may cause serious headaches for users with a different display resolution. This is not your case, but consider a server configuring a resolution 1920 × 1080 and a user connecting with a laptop 1366 x 768. He would be forced to use either the fit to window to scale the session, or the viewport to navigate the session with scrollbars.
This is a session setting, you can configure it when you’re connected to the remote server. Press Ctrl+Alt+0 when you see the remote desktop (this is the default shortcut, unless you’ve changed it in Input preferences) and you’ll see that Display button.
Hi Eddie!
Please verify if the box “Match the client resolution upon connecting” is unchecked in Display settings. This configuration does exactly what you’ve described, by changing the remote desktop geometry to match the local display resolution.I already use it, but it would also be nice to have a “maintain aspect ratio” option so that the screen just scaled without distorting. It would of course leave some black bars sometimes.
Hey Teuton, check this out on NoMachine 5:
Keeping the aspect ratio when the session window is in a scaling mode
https://www.nomachine.com/FR12L02847Hey Oleg!
I’m happy you’ve sorted it out. While checking your report we’ve found some things not working as expected on Plasma 5, so we’re enhancing the support for that environment.
As for file transfer, it is supported on all NoMachine products. You can see the file transfer menu item only when someone connects to the server. More information here:How to transfer files between computers
At last, thank you for your positive comments! We all at NoMachine work hard to make users happy. Welcome to the family. 😉
Hi oleg.
Thank you for taking the time to report this. In order to start the investigation, could you please clarify on which OS the tray icon is not visible? You initially said it was on Windows, but the solution you’ve tried is related to Linux.As for the specific solution, we don’t use system’s Qt so sni-qt (which is a plugin) is not loaded in our library. Probably installing it caused a change in the system that indirectly affected NoMachine’s icon. We’ve our own implementation of Status Notifier Items interface, so when a system tray is not available we use DBUS to create the menu in Indicator.
Hi karl.
Could you please send a screenshot of the folder preferences? You can access it by clicking on Preferences button in the NoMachine client, then Folders tab.Hi!
Currently a NoMachine connection can be started by double clicking the NXS icon or by using the option –session on command line.
We’re planning to add an URL handler so that you can use ‘nx://’ in the browser address bar to start the client and connect to a NoMachine server.
May one of these help you?Hi jimla!
Sorry for the delay. We’ve tried to reproduce your problem but without luck.
Please extract server side logs as explained at https://www.nomachine.com/DT04M00076 and send them to forum[at]nomachine[dot]com. Thanks!Hey rejsmont!
We’ve documented the problem causing that log, you can see it here:https://www.nomachine.com/TR07M05813
Anyway it doesn’t look to be related to the authentication problem, we’ll get back to you soon with more details/questions. Thank you.
Iceback, the shortcut Ctrl+Tab is used to trigger the view loop, so it doesn’t go through the usual events handling and we were not catching it correctly. Maybe you’ve a different configuration or you’ve enabled the keyboard grabbing?
Hey guys.
After going deep into this issue we’ve decided to split it up into two different problems. One is documented in TR05M05497 and it is related to Alt+Tab not working on server Windows 8 and later; the other one is about Ctrl+Tab not working correctly from OS X client:https://www.nomachine.com/TR07M05788
Any of you wishing to test a fix for the latter, please contact us at forum[at]nomachine[dot]com.
Hi wernermaes.
The ‘–list’ option reports all users connected to that NoMachine Server, while NoMachine Monitor shows users connected to the session where it is running. For the same reason, Whiteboard can be used only with users sharing the same session, so for example if other users are running their own virtual desktops, you cannot communicate with them through the Monitor.