kroy

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 555 total)
  • Author
    Posts
  • in reply to: How to make NoMachine update target computer IPs? #38680
    kroy
    Contributor

    What is your username for the computer you are accessing? This “username” is what you should write here: C:\Users\HERE\.nx\cache

    Folder “.nx” is hidden, you can set File browser to show hidden items or just paste C:\Users\PASTE-HERE-USERNAME\.nx\cache path in navigation bar in the File browser.

    in reply to: How to make NoMachine update target computer IPs? #38646
    kroy
    Contributor

    Also in the home directory – C:\Users\your_username\.nx

    in reply to: How to make NoMachine update target computer IPs? #38629
    kroy
    Contributor

    Hi

    You don’t have to change IP manually. It will change automatically after few seconds. Problem is that it looks that you already entered IP manually and it’s saved permanently in connection file now. You can remove that change with editing .nxs (probably last file in the: ~/.nx/cache/) on client side. Find line with key “Server host” and delete IP value like here:

    <option key=”Server host” value=”” />

    in reply to: NoMachine systems-login Idlehint=no #37743
    kroy
    Contributor

    Hi

    Is NoMachine currently do not use systems-login daemon?

    NoMachine don’t use systems-login daemon.

    If there is a need we could propose some custom script that would set Idlehint=yes, for example with this command:

    dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1/session/c21 "org.freedesktop.login1.Session.SetIdleHint" boolean:true

    (where c21 is ID of your session).

    in reply to: Forward authentication not working for sudo #37645
    kroy
    Contributor

    You should revert changes – it looks it’s indeed script, not a file with keys. Are you using physical desktop? If yes – agent forwarding won’t work. Agent forwarding option can be used on virtual and custom sessions (even already existed).

    in reply to: Forward authentication not working for sudo #37624
    kroy
    Contributor

    Hi

    According to http://pamsshagentauth.sourceforge.net/ authorized_keys_command specifies path to command not a file with keys:

    auth sufficient pam_ssh_agent_auth.so authorized_keys_command=/path/to/command
    Use /path/to/command, which will receive a single argument, the name of the user authenticating, to look up authorized keys. the output of the command is expected to be in authorized_keys2 format. This runs the command as the user authenticating

    If /usr/bin/sss_ssh_authorizedkeys is path to file with authorized keys tru set in /etc/pam.d/sudo:

    auth    sufficient   pam_ssh_agent_auth.so file=/usr/bin/sss_ssh_authorizedkeys debug

    in reply to: No available desktops after upgrading ESXi #37319
    kroy
    Contributor

    Can you check what shows with whereis "libpam.so.0" command, and htat are you able to log as local user with: /usr/NXbin/nxexec --auth (execute that command as local user, do not use “sudo”).

    in reply to: No available desktops after upgrading ESXi #37281
    kroy
    Contributor

    If configuration on that Slackware wasn’t changed, there shouldn’t be a problem with creating the desktop. Are you able to run startx from your virtualization client? If not, that would indicate a problem with image after ESXi upgrade. If desktop started and after sudo /etc/NX/nxserver --restart you’re still not able to connect, please send logs. First enable them, reproduce the problem and then collect logs (more instructions are there: https://knowledgebase.nomachine.com/DT11R00182).

    kroy
    Contributor

    Hi

    Please edit /usr/NX/etc/node.cfg and set following key:

    DefaultDesktopCommand "/usr/bin/env XDG_CONFIG_DIRS=/etc/xdg:/etc/kde/xdg /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startplasma-x11"

    in reply to: Connecting over a mobile network using SSH tunnel #36170
    kroy
    Contributor

    Hi.

    You have two Ubuntu: ubuntu-mobile (not available for connections from other network) and ubuntu-home (it’s in local network and it’s available for connections from your mobile phone and over internet). On ubuntu-home needs to be installed ssh server (sudo apt install openssh-server).

    Open terminal on ubuntu-mobile machine and create reverse tunnel:
    ssh -fN -R ubuntu-mobile-IP:14000:localhost:4000 username-ubuntu-home@ubuntu-home-IP
    or
    ssh -fN -R *:14000:localhost:4000 username-ubuntu-home@ubuntu-home-IP

    The first command allows you to connect through SSH tunnel from ubuntu-home machine, the second – form any address on the Internet. To connect open NoMachine Player set as IP ubuntu-home-IP and 14000 as Port (where 14000 is any unused port before ssh tunneling on ubuntu-home machine).

    in reply to: Console (not desktop GUI) displayed #35925
    kroy
    Contributor

    It seems that it was a problem with some system configuration, unrelated to NoMachine. Feel free to write here again if the problem would show again.

    in reply to: Console (not desktop GUI) displayed #35893
    kroy
    Contributor

    We are investigating the problem. Meanwhile you can edit org.gnome.Shell.desktop entry

    sudo vim /usr/share/applications/org.gnome.Shell.desktop

    and change line:
    Exec=env LD_PRELOAD=/usr/NX/lib/libnxegl.so /usr/bin/gnome-shell
    to this:
    Exec=/usr/bin/gnome-shell

    and tell us if it helps.

    in reply to: Connects but shows wrong remote host name #35748
    kroy
    Contributor

    Thanks for letting us know.
    It’s not necessary to remove NoMachine. Network broadcasting informations are cached in ~/.nx/cache folder – to clear remove correct .nxs file or remove all files from that directory.

    in reply to: Connects but shows wrong remote host name #35731
    kroy
    Contributor

    Can you check what the uname -n command shows on that “Host-B” machine? On NoMachine player you should see exactly the same hostname.

    in reply to: Not finding physical session or opening virtual session #35606
    kroy
    Contributor

    DefaultDesktopCommand "/usr/bin/cinnamon-session --session cinnamon" should fix the problem with virtual desktop.

    Regarding to physical desktop – we cannot reproduce such problem on Mint 19.3 with LightDM. Is it clean installation of the NoMachine? If it’s update, upgrade or some re-installation – execute following commands:

    sudo /etc/NX/nxserver --addtoredis
    sudo /etc/NX/nxserver --restart

    and recheck. If that won’t help we suggest to remove NoMachine with all config files:

    sudo dpkg --purge nomachine
    sudo rm -rf /usr/NX /etc/NX /var/NX

    and install again newest package.

Viewing 15 posts - 1 through 15 (of 555 total)