Forum Replies Created
-
AuthorPosts
-
December 13, 2016 at 13:31 in reply to: Client window does not properly resize to cover monitor #13176TorParticipant
Hi. The list of available resolutions on the new server appears to have mixed or invalid refresh rates. Is the guest OS correctly configured (guest additions, VMWare tools, etc)?
December 12, 2016 at 11:51 in reply to: Client window does not properly resize to cover monitor #13165TorParticipantHi.
The behaviour you’re describing looks correct if the client is not configured to resize the remote desktop, it keeps the original geometry and snaps the window to that size. If instead you’ve enabled the “Resize remote screen” option in the Display menu, then the remote desktop may not support the resolution you’re trying to set or the desktop environment is forcing its own resolution.This behavioural change may be due not only to different NoMachine versions, but also to different desktop environments used on those servers.
Are those servers running in virtual machines? Can you please send the output of the command ‘xrandr -q’ executed in a terminal on both servers?
TorParticipantHi again. We’ve slightly changed the keyboard grabbing option, so that now it can work around your issue also when the NoMachine client is windowed. Would that be a good solution for you? If you would like to test it, please contact us at forum[at]nomachine[dot]com.
TorParticipantThis is an accessibility feature and as such, we would like to support it. The problem is that it is implemented in a way that makes difficult for an application to continue to handle correctly keyboard events. There are many other apps with the same problem, and we guess this may be one of the reasons why the feature is not available on some recent desktop managers.
The keyboard grabbing option, configurable in the Input menu, can work around this problem when the NoMachine client runs fullscreen even if it doesn’t allow the cursor to highlight. Unluckily it doesn’t help in window mode.October 12, 2016 at 16:06 in reply to: "Show remote cursor pointer" grayed out on Android client #12708TorParticipantHi. The option ‘Show remote cursor pointer’ is not currently compatible with the BT mouse, this is the reason why it is disabled. The next NoMachine version (we’re currently using it internally) will change in this way: the cursor will be always visible and will have an option to hide it; the ‘pointer mode’ will need the remote cursor pointer to be visible, and can be enabled even if there is an hardware mouse attached, by handling differently mouse and touch events. I’m sure this will solve your problem.
With the current version you can see the remote cursor when pressing the mouse button. Even if this is far from being ideal, it can be helpful to confirm the operation you’re doing.TorParticipantHi. We’ve checked your logs and used them to emulate the same environment without reproducing an issue like that. Even if the problem is on the server we’ll need more information, but since they may be sensitive we’ll contact you by e-mail.
By the way, in your logs it shows you’re connecting to a fully licensed server. Remember that you’re entitled to support via your customer area. Perhaps you should get your administrator to open a support ticket. This would also avoid sensitive information being published on the forum.
TorParticipantHi.
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!October 3, 2016 at 12:27 in reply to: "The NoMachine service is not available or the access was disabled" macOS Sierra #12559TorParticipantHi. 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.
TorParticipantThis Trouble Report tracks your issue: https://www.nomachine.com/TR12L04740
We plan to release a fix in the next update of our mobile application.September 14, 2016 at 14:31 in reply to: Can I use the commandline to bypass the connection screen and the login #12360TorParticipantHi Taylor.
What is the command you’re using to start the client?
TorParticipantHi 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
September 13, 2016 at 10:07 in reply to: Can I use the commandline to bypass the connection screen and the login #12346TorParticipantHi.
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" />
- This reply was modified 8 years, 2 months ago by Tor.
TorParticipantHi 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.
TorParticipantHi. 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.
TorParticipantHi.
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. - Change the server.cfg file by disabling the ‘automigrate’ feature
-
AuthorPosts