Tor

Forum Replies Created

Viewing 15 posts - 391 through 405 (of 594 total)
  • Author
    Posts
  • in reply to: Nexus 6P supported? #13485
    Tor
    Participant

    Hi Brian.
    Did you see that message in our Play Store page? If it is so, you’re not being allowed to download the app because it currently needs at least a 7″ display. We’re working on a version optimized for smaller displays, it was delayed but it is still one of our top priorities. You may subscribe this Feature Request to be contacted when we’ll release it:

    Offering a NoMachine client for Android smartphones
    https://www.nomachine.com/FR09L02828

    In the meanwhile you may wish to install the APK of our tablet version, you can get it from the download area of our website. On a display bigger than 5″ (like the one of the Nexus 6P) it is not perfect but still usable.

    in reply to: Phone support still planned #13466
    Tor
    Participant

    Hi Vanderemit. We’re very close to the release of the phone optimized application. The usability on small screens is very critical, so we’re evaluating all details thoroughly to be sure to give the best experience. Be patient just a bit more and I’m sure you won’t regret it. 🙂

    Tor
    Participant

    Hi Florian.
    Can you help us to identify the issue by answering to these questions?

    • What is the NoMachine version installed on client and server?
    • What is the OS of the server?
    • Where do you reproduce the issue, on the client or on the server?
    • All monitors turn on and off, also the one of the notebook?
    • When the problem occurs exactly, always or only when you connect with NoMachine?

    It would be great if you could retrieve logs on the computer where the issue occurs. You should follow this article, point 3 of section 3:
    https://www.nomachine.com/DT07M00098#3
    Send the archive to forums[at]nomachine[dot]com.

    in reply to: Screen resolution on PC Display #13265
    Tor
    Participant

    Hi.
    Resolutions supported on your server are not related to those available on your client: even if your monitor has a resolution of 1600×900, the remote desktop may not support it. Can you send the list of available resolutions on the server by running the command ‘xrandr -q’ in a terminal, on Linux?

    in reply to: Client window does not properly resize to cover monitor #13176
    Tor
    Participant

    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)?

    in reply to: Client window does not properly resize to cover monitor #13165
    Tor
    Participant

    Hi.
    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?

    in reply to: Ctrl-key conflict with cursor highlighting #12781
    Tor
    Participant

    Hi 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.

    in reply to: Ctrl-key conflict with cursor highlighting #12766
    Tor
    Participant

    This 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.

    in reply to: "Show remote cursor pointer" grayed out on Android client #12708
    Tor
    Participant

    Hi. 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.

    in reply to: NoMachine hangs in Linux RHEL 7.2 #12639
    Tor
    Participant

    Hi. 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.

    in reply to: NoMachine client on Chromebook via Android #12600
    Tor
    Participant

    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/TR07N07085

    We’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!

    Tor
    Participant

    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/DT12I00037

    If the public key changed, please verify that the client configuration is using the correct private key.

    in reply to: Bad layout/Mapping #12390
    Tor
    Participant

    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.

    Tor
    Participant

    Hi Taylor.

    What is the command you’re using to start the client?

    in reply to: Unable to start multiple sessions using same user #12351
    Tor
    Participant

    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
Viewing 15 posts - 391 through 405 (of 594 total)