Tor

Forum Replies Created

Viewing 15 posts - 391 through 405 (of 620 total)
  • Author
    Posts
  • in reply to: Chrome OS #14623
    Tor
    Participant

    Hi. We plan to release the new mobile version with our next major release. In the meanwhile you may wish to install the APK of our current version, you can get it from the download area of our website.
    As for Chromebook, NoMachine client works on it, but the next release will also improve our support by offering a better integration.

    in reply to: Ctrl-alt-del passthrough #14592
    Tor
    Participant

    I understand your point, but we prefer to avoid to hardcode key combinations to grant more freedom to users. NoMachine client shortcuts are configurable and quite flexible, they’re based on users’ feedback and generally appreciated.
    The default shortcut described in the Feature Request will be Ctrl + Alt + End, but since shortcuts are configurable you can set the combination you prefer.

    in reply to: Windows desktop scaling on client breaks NoMachine #14586
    Tor
    Participant

    Hi. I assume you’re using an Enterprise or Cloud Server on Linux as a bridge for your RDP connection. Can you please confirm it, together with the NoMachine version you’re using on Linux? Also, what is the rdesktop version on the Linux server? We didn’t reproduce your issue in our labs, so we need this information to go on with the investigation.

    in reply to: Ctrl-alt-del passthrough #14582
    Tor
    Participant

    Hi. I think you may need this Feature Request, we plan to include it in the next release:

    Adding a keyboard shortcut to send ctrl+alt+del
    https://www.nomachine.com/FR09N03203

    If it is it, I’d suggest to subscribe to the FR to be notified when we’ll release it.

    Tor
    Participant

    You can use the --session command line option, probably coupled with --exit. Check this article for details:

    Command line options for the NoMachine client
    https://www.nomachine.com/AR04O00923

    in reply to: Typing delay on NoMachine #14336
    Tor
    Participant

    Hi chomes.
    We’re not aware of similar issues, so we’d need more information to investigate your report.

    • What is the NoMachine version installed on the server?
    • Are you connecting to a virtual or physical desktop?
    • When the problem occurs, do you see a general slowness (all updates are slow) or is the problem limited to keys?
    • Can you try if the same problem occurs with all applications (e.g. Terminal, different text editors, browser’s address bar)?
    • Do you’ve a way to test another server with a different OS, like OS X?
    • Are you connecting to the server through a LAN or a WAN? Do you know your bandwidth and latency?
    • Could you try NoMachine when no other apps are running in background?
    in reply to: Hide NoMachine client with running a custom session #14280
    Tor
    Participant

    Hi Alex. You can find options description here:

    Command line options for the NoMachine client
    https://www.nomachine.com/AR04O00923

    in reply to: Hide NoMachine client with running a custom session #14260
    Tor
    Participant

    Hi. You can execute the NoMachine client with the command line option ‘–hide’, the main window will hide when the custom session starts and will show again when the session terminates. The option doesn’t affect other type of sessions, so you may consider to add it to your application’s shortcut.

    in reply to: Specify which display to connect to #14259
    Tor
    Participant

    Hi. At the moment a physical desktop cannot be automatically selected by storing it in the NXS file.

    in reply to: Fullscreen on secondary display #14106
    Tor
    Participant

    Hi Tobias.
    We’re aware of this problem, it is documented here:

    https://www.nomachine.com/TR02L04268

    The only workaround is disabling separate Spaces for displays. In order to avoid to scroll the window, you can enable the “Resize remote screen” option in the Display bar to tell the remote desktop to use the size of the window.

    in reply to: Feature Request: ChromeOS Client #14051
    Tor
    Participant

    Hi.
    Since the announce of Chrome OS supporting Android apps, we’re focused on improving our app to run flawlessly on Chromebooks. Check out this page to know if your model supports (or will support) Android apps so you can download NoMachine client from Play Store:

    https://sites.google.com/a/chromium.org/dev/chromium-os/chrome-os-systems-supporting-android-apps

    We don’t have a native version for Chrome OS in our short-term roadmap, but if this will change in future we’ll announce it here and on our website.

    in reply to: Making a shortcut for direct connection #14007
    Tor
    Participant

    Hi Gerhard.
    There are multiple ways to have a shortcut pointing to your connection settings:

    – Click New in the client, and at the end of the wizard check the option “Create a link on the desktop”

    or

    – Copy on desktop the connection file, located by default in Documents\NoMachine

    or

    – Copy the connection file and paste it as shortcut on desktop

    In all cases you can save the password in the connection file, if you don’t want to be asked again at connection time.

    When you’re in the authentication panel the first time you connect, select the box “Save this password in the connection file” then click OK.

    in reply to: Sending Command-W to remote desktop #13964
    Tor
    Participant

    Hi Christian.
    There may be something wrong, we’ll verify it. Thank you for the report. 🙂

    in reply to: Connection session at startup #13952
    Tor
    Participant

    You may configure the client to automatically start when logging in the Ubuntu session. There should be an application like “Startup Applications Preferences” to configure autostarting applications, or you may configure it manually by creating the file ~/.config/autostart/nxplayer.desktop with the following content:

    [Desktop Entry]
    Type=Application
    Name=NoMachine client
    Exec=/usr/NX/bin/nxplayer --session "path to the NXS file" --exit
    Icon=NoMachine
    Comment=NoMachine client automatic session
    X-GNOME-Autostart-enabled=true
    in reply to: Sending Command-W to remote desktop #13949
    Tor
    Participant

    Hi.
    The option “Grab the keyboard input” is the only way to send Cmd+W to the remote side. Please note the keyboard is grabbed only when the remote desktop is visible and active, so for example if you open the client menu and press Cmd+W, the window will close.

Viewing 15 posts - 391 through 405 (of 620 total)