Britgirl

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 4,335 total)
  • Author
    Posts
  • in reply to: User name and password issues logging in #47834
    Britgirl
    Keymaster

    Earlier you wrote that you are also not able to login using Windows own remote desktop program. It’s either something misconfigured (possibly to do with the MFA app), the username and/or password is incorrect, or the fact that it’s a corporate PC, is it possible that remote desktop was even disabled?

    NoMachine accepts multiple username formats, explained in the article just below.

    Username formats supported to log-in to NoMachine by password authentication
    https://kb.nomachine.com/AR03S01118

    Is it possible for you to make a test which for the test’s purposes requires a person on the other end? I realise that your intention is to get unattended access, but at least this way we can see that a NoMachine connection is actually possible. On your mother’s PC (the server side), check that GuestDesktopSharing is enabled. In the free version it’s enabled by default, but you can check it by going into the NoMachine server settings, in the Security panel: !M icon in the system tray > Server status > Security > Allow guest desktop sharing on this server. Then start your connection (see also the illustrated tutorial https://www.nomachine.com/getting-started-with-guest-desktop-sharing, there are steps for the desktop owner and steps for the guest).

    Another thing we can do is look at the player logs and the server-side logs to check the error in more detail. Again, on your mother’s computer, open the Security panel, scroll all the way down and select debug level in ‘Server logs’. Restart the NoMachine server in Status. Then on your computer, the local side, open the Settings and go to Player > Security, tick the box ‘Don’t delete log files on exit ‘. Reproduce the problem. For the Player logs on Windows the .nx folder is hidden. To find it, write the following in the address bar or the file browser:
    %USERPROFILE%\.nx or navigate through the computer folder till the user’s home and digit .nx in the navigation toolbar to reach it. Path can be similar to: C:/Users/nomachine/.nx. Zip it.</p>
    For the server logs, find the VAR folder. It’s stored in %PROGRAMDATA%/NoMachine/var/log/. Zip that as well. Send everything to forum[at]nomachine[dot]com.

    </div>

    in reply to: User name and password issues logging in #47825
    Britgirl
    Keymaster

    To access any desktop via NoMachine you need a system account on that computer. On Windows 11 you need to input the same credentials you would normally use when accessing your onelive account on the MS website. Or you can use the local username assigned to your account. The password is the same for both. To check the local username, just go into the C: drive of the computer you want to access, select Users and check what your local username is. Are you sure you are using the right password? Don’t use the PIN that Windows 11 asks you when unlocking the screen.

    in reply to: User name and password issues logging in #47820
    Britgirl
    Keymaster

    Can you show us the error that you are receiving with NoMachine? What Windows version is it on the side you are connect to?

    in reply to: Hardware encoder not working on Linux #47813
    Britgirl
    Keymaster

    We’re analyzing the information you provided to us, so thank you, and now it’s a question of replicating the environment and reproducing the exact same errors. We’ll update the topic as soon as we can.

    in reply to: How to disable password storing in the client? #47798
    Britgirl
    Keymaster

    Yes it did, but my fault for not noticing that the document I indicated was not up-to-date. All v8 documents are aligned now.

    Britgirl
    Keymaster

    Those commands are for running virtual desktop sessions which are available in all Terminal Server products. What you need to do is

    By default, on Linux:

    /usr/NX/bin/nxplayer --session <path to .nxs file>

    For more details check out this article https://kb.nomachine.com/AR04O00923. You may also be interested in this document which highlights what you can configure in your connection file: https://kb.nomachine.com/DT07S00240

    in reply to: NoMachine connection to Windows 11 freezes up #47793
    Britgirl
    Keymaster

    The output didn’t proffer any useful hints unfortunately.

    Completely disable hardware decoding on the client if you already didn’t do so by following the instructions here:
    https://kb.nomachine.com/AR07U01202

    Attach gdb so we can get the dump of threads of the client not updating the screen:

    $ sudo gdb -p <pid of the client process>
    $ set height 0
    $ set logging file /tmp/backtrace.txt
    $ set logging on
    $ threads apply all bt full
    $ quit

    Also, when the connection freezes, is the client still responsive?  ie. Can you open the menu and interact with it? While the window appears to be frozen, is the CPU usage of the client process normal?

    in reply to: Hardware encoder not working on Linux #47784
    Britgirl
    Keymaster

    Can you give us the output of lspci?

    Britgirl
    Keymaster

    Decoding is disabled in the Player.cfg on the client side, the device that you are connecting from. There is an article you can check for the steps to follow:

    How to disable hardware decoding on the client side
    https://kb.nomachine.com/AR07U01202

    in reply to: How to disable password storing in the client? #47781
    Britgirl
    Keymaster

    Apologies, the correct key is EnableClientCredentialsStoring none. I realised my mistake when checking the server.cfg file. The key is present in your version. Just set it to none.

    in reply to: Hardware encoder not working on Linux #47775
    Britgirl
    Keymaster

    We’re doing some tests in our lab and we’ll let you know.

    in reply to: Hardware encoder not working on Linux #47766
    Britgirl
    Keymaster

    Are you still getting the same error when running iHD_drv_video.so from /usr?

    QuickSync/QuickSync: WARNING! Failed to set display handle. Error is -17: Device operation failure.

    Britgirl
    Keymaster

    Hi, this is a known issue and the fix will be in the next update.

    Message “SELinux is preventing systemd from ioctl access on the file /usr/lib/systemd/system/nxserver.service” is issued on RHEL 9.3
    https://kb.nomachine.com/TR02V11080

    in reply to: How to disable password storing in the client? #47744
    Britgirl
    Keymaster

    In version 8 it is configured on the server side using the EnableCredentialsStoring key in the server.cfg. Also present in the free version.

    The key to not store the credentials is set in the server.cfg on the server, not the player.cfg. Remove the key from the player.cfg, if you’ve added it, which is not required. Then try again. Restart the nxserver. If you are still being requested for the credentials, tell us

    Client OS and version
    Server OS and version

    Also submit the player.cfg and server/node cfg and we can check them. Send them to forum[at]nomachine[dot]com.

    in reply to: Hardware encoder not working on Linux #47740
    Britgirl
    Keymaster

    The output you pasted show that ihd is still being loaded from /opt/intel/mediasdk/lib64/iHD_drv_video.so. Try restarting nxserver again. Knowing its proxmox can make a difference yes. What’s the exact distro and display manager your replicating?

Viewing 15 posts - 16 through 30 (of 4,335 total)