Forum Replies Created
-
Posts
-
Hi.
In our next release we’ll include the official support for Chromebook. Problems we’ve found so far are these:
https://www.nomachine.com/TR09N07231
https://www.nomachine.com/TR07N07085We’re also evaluating some small changes to improve the experience on these devices.
– Buttons get cut off from the bottom of the window. Luckily, toggling the window to full-screen reveals them.
This is one of the problems reported above. As you said, you can work around it by toggling on and off the fullscreen mode.
– Some gestures are already used by the OS, so four-finger swipe doesn’t quite work.
We’ll change the four fingers swipe to four fingers tap, like we did on iOS some versions ago.
– The window isn’t resizable.
– Relatedly, an aspect-ratio preserving display mode would be helpful.
Currently Android doesn’t allow to freely resize the window. This will change with Android N but as of now, we can’t do much. We’ll see how the Chromebook support to Android apps will evolve.
– It would be great if there were a mode that understood the presence of a hardware keyboard and also a hardware pointing device, allowing for actual right-mouse-button use.
You can expect to easily work with mouse and keyboard on Chromebook in our next release, it’s one of the main improvements we’re introducing.
Thank you for sharing your experience and for your proposals!Hi. This error occurs when the client cannot authenticate to the server with the “NoMachine login”, before asking the user credentials for the password based authentication. You can find more information here:
Configuring authentication in NoMachine
https://www.nomachine.com/DT12I00037If the public key changed, please verify that the client configuration is using the correct private key.
This Trouble Report tracks your issue: https://www.nomachine.com/TR12L04740
We plan to release a fix in the next update of our mobile application.Hi Konrad.
By default NoMachine enables the automatic migration feature: when a user connects to a server where the same user is already connected, NoMachine migrates the running application to the new connection. This behaviour can be changed in two ways:
- Change the server.cfg file by disabling the ‘automigrate’ feature
ConnectPolicy autocreate=1,autoconnect=1,automigrate=0,desktop=0,dialog=0
- Create more than one NXS file, each one with a different name, so the client will not match the running session for the migration
Hi.
If you can use a script, then you could configure a NXS file with the information you want to set and start the connection with the command
$C:\nxplayer.exe --session <NXS>
Related configurations keys (with their default values) in the NXS file are:
<option key="Server host" value="" /> <option key="User" value="" /> <option key="Auth" value="EMPTY_PASSWORD" />
Hi scotty.
You can transfer a file by either using the NoMachine tray menu or with drag&drop.
For the first method, you can read this article explaining it in details:
https://www.nomachine.com/sharing-files-between-computers
If you don’t want or you cannot use the NoMachine menu, you can drag a file from the local file system and drop it on the NoMachine client window, or vice versa drag a file from the remote file system and drop it on the local desktop.
Hi. NoMachine uses some system tools on Linux to ask for user credentials, there may be a problem with them. Could you please pack the logs you see in the directory $HOME/.nx when the problem occurs, and send them to forum[at]nomachine[dot]com? Thanks.
Hi.
We’d like to send you a debug version to retrieve some information. If you wish to help us to solve this issue, could you please send your contact to forum[at]nomachine[dot]com?
Thanks.Hi.
When you want to disconnect, press Ctrl + Alt + 0 to open the menu, then click the small icon in the bottom-right corner of the menu, under the Done button. In the disconnection dialog, check the box “Remember current window size and position”, then exit the client. When you start NoMachine again, is still the window not visible?Hi.
This problem started with 5.1.42, while the old version was working correctly? In such a case, what was the old version?Could you please retrieve logs as explained in the following article paragraphs, and send them to forum[at]nomachine[dot]com.
https://www.nomachine.com/DT04M00076#6
https://www.nomachine.com/DT04M00076#11A small addendum. I was talking about Hankaku/Zenkaku toggle key but indeed the rule applies to any IME switching: you must switch the IME also on Windows if you want keycodes correctly translated.
Hi. You’ve two options: use the hankaku/zenkaku toggle key on your keyboard, which we support correctly starting from version 5.1.40, or switch not only the input on the client, but also on the server. If you use a key combination to change the IME on Linux, the selected IME doesn’t propagate to the server.
Hi. This would be indeed a very comfortable feature! We’ve documented it in a Request classified with high priority, which makes it a good candidate to be implemented in the near future. Thank you for your feedback.
Adding a keyboard shortcut to cycle through connection windows on OS X
https://www.nomachine.com/FR07N03135If you wish you can subscribe in the page above to be notified when we’ll release the feature.
Thank you for confirming the problem.
We’ve opened a new Trouble Report to document it, you can subscribe to be informed when we’ll release a fix:The virtual keyboard does not appear when the tablet is connected to some external devices
https://www.nomachine.com/TR07N07009 - Change the server.cfg file by disabling the ‘automigrate’ feature