zaq

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 65 total)
  • Author
    Posts
  • in reply to: Server status : Querying the server problem again #32458
    Avatarzaq
    Contributor

    Hi,

    We weren’t able to reproduce the error. Could you check your NoMachine
    Service shortcut? It’s the path:

    C:\ProgramData\Microsoft\Windows\Start
    Menu\Programs\NoMachine\NoMachine Service

    and check target like you can see in the attached picture.

    Also logs will be helpful, please gather them like it is described in:

    https://www.nomachine.com/DT10O00163#1.4

    and send log archive to:

    forum[at]nomachine[dot]com

    in reply to: Server status : Querying the server problem again #32405
    Avatarzaq
    Contributor

    Hello Babok,

    Did you do update by installing *exe file with new version or by clicking in Settings in GUI? Which was your previous version?

    in reply to: NX server does not launch at OpenSuse Tumbleweed boot #31765
    Avatarzaq
    Contributor

    Hello,

    Could you check status of nxserver start mode:

    /etc/NX/nxserver --startmode

    if you get:

    NX> 807 Service NoMachine status is: Manual

    please set as automatic:

    sudo /etc/NX/nxserver --startmode automatic

    in reply to: NX server does not launch at OpenSuse Tumbleweed boot #31494
    Avatarzaq
    Contributor

    Hello Eragontux

    We weren’t able to reproduce the problem in our laboratory.

    Could you send output from this commands:

    /etc/NX/nxserver --version

    ps aux | grep nx

    systemctl status nxserver

    sudo systemctl restart nxserver

    and packed log directory:

    /usr/NX/var/log

    to forum[at]nomachine[dot]com.

    Do you see the error in YaST2 GUI, pls check attached image.

    Attachments:
    in reply to: Unable to install on Windows 10 #29839
    Avatarzaq
    Contributor

    Hello wlgrd,

    Could you:

    1) Open cmd as Administrator – open Menu Start and just write cmd, then choose ‘Run as administrator’.

    2) Run this commands:

    dir "C:\Program Files (x86)\NoMachine\etc"

    icacls "C:\Program Files (x86)\NoMachine\etc\nodes.db"

    3) Send the whole log file and outputs from the commands to forum[at]nomachine[dot]com please?

    in reply to: Server doesn’t start on cold boot #29811
    Avatarzaq
    Contributor

    I think that you can find more useful information here:

    https://www.nomachine.com/AR03P00973

    in reply to: Server doesn’t start on cold boot #29778
    Avatarzaq
    Contributor

    Hello gasde,

    We weren’t able to reproduce the problems in our laboratory.
    Could you gather logs from the affected host like it’s described in:

    https://www.nomachine.com/DT10O00163#1.1

    and send to forum[at]nomachine[dot]com please?

    in reply to: Windows 10 – No session available on this server #27887
    Avatarzaq
    Contributor

    Hello fr2

    Looks like you have a problem with creating a profile of user nx.
    There are 2 possible reason:

    1. Do you use domain users/LDAP/ActiveDirectory? Do you have non
    standard restrictions for users?

    2. It’s possible that default user profile on your host might be
    corrupted. You can try to create few user accounts and check if
    it’s possible to login on their desktops. If you experience any
    problems, please refer to this Stack Overflow thread:

    https://superuser.com/questions/947398/cant-login-with-new-local-users-in-windows-10

    in reply to: Not able to start nxserver on Ubuntu 16.04 #27517
    Avatarzaq
    Contributor

    Hello resmi,

    Looks like your issue is related to a presence of nx user.
    Probably user nx was removed during the installation process.

    Do you use domain users/LDAP/ActiveDirectory? Do you have non
    standard restrictions for users?

    A standard set of logs will be helpful. Gather them like is
    described in:

    https://www.nomachine.com/DT10O00163#1.1

    and send to forum[at]nomachine[dot]com.

    in reply to: NXD Service won’t start on MacOS 10.12.6 Sierra #27010
    Avatarzaq
    Contributor

    Hello apfaffman,

    You are right, looks like your issue is related to presence of nx user
    From logs looks like in the beginning of installation the user had
    existed:

    NX> 700 Running: /usr/sbin/chown nx:wheel ‘/Applications/NoMachine.app/Contents/Frameworks/etc/update.cfg’.
    NX> 700 Result: OK.

    but in the next phase there where problems:

    NX> 700 Running: /usr/sbin/chown nx:wheel ‘/Applications/NoMachine.app/Contents/Frameworks/etc/guests.db.lock’.
    NX> 700 ERROR: Cannot change ownership of: /Applications/NoMachine.app/Contents/Frameworks/etc/guests.db.lock to: nx:wheel.

    Looks like the user nx was removed during installation process.

    Do you use domain users/LDAP/ActiveDirectory? Do you have non
    standard restrictions for users?

    Avatarzaq
    Contributor

    Hello david555

    Probably your problem is related to SELinux. To check this you can:

    1) temporally set permission mode

    sudo setenforce 0

    2) run NoMachine:

    sudo /etc/NX/nxserver --restart

    3) try to reproduce the problem,

    4) set SELinux’s enforce mode:

    sudo setenforce 1

    if you aren’t able to reproduce the problem, then we check deeper
    SELinux logs.

    Anyway a standard set of logs will be helpful. Gather them like is
    described in:

    https://www.nomachine.com/DT10O00163#1.1

    and send to forum[at]nomachine[dot]com.

    in reply to: Nxserver is always disabled on SLES12 #25580
    Avatarzaq
    Contributor

    Hello coco_jie

    We are not able to reproduce the problem in our laboratory. Could you
    give us more info please.

    Send output from commands:

    1) /etc/NX/nxserver --version

    2) ps aux | grep nx

    3) sudo /etc/NX/nxserver --startup

    and also set of logs in the way like it’s described:

    https://www.nomachine.com/DT10O00163#1.1

    in reply to: Cannot install latest version (6.9.2.1) on Ubuntu 16.04 #25464
    Avatarzaq
    Contributor

    Hello,

    The problem is related to ‘install’ command.
    Probably the standard command was replaced by a link/wrapper to apt.
    Could you run:

    /bin/install --help

    It should looks like this:

    $ install --help
    Usage: install [OPTION]... [-T] SOURCE DEST
    or:  install [OPTION]... SOURCE... DIRECTORY
    or:  install [OPTION]... -t DIRECTORY SOURCE...
    or:  install [OPTION]... -d DIRECTORY...
    
    This install program copies files (often just compiled) into
    destination locations you choose........

    The default location of original ‘install’ program in Ubuntu 16.04 is:

    /usr/bin/install

    in reply to: Server status is not running #23277
    Avatarzaq
    Contributor

    Hello Carlos,

    During detecting name of Administrator’s group something went wrong.
    Do you use ActiveDirctrory/LDAP/domain users?

    To investigate the problem I need output from these commands:

    net localgroup

    net user nx

    and a file adminGroup.txt from this:

    "C:\Program Files (x86)\NoMachine\bin\nxdisplay.exe" --admingroup > adminGroup.txt

    You can send the outputs and the file to forum[at]nomachine[dot]com.

    in reply to: Cannot reconnect after logout #23210
    Avatarzaq
    Contributor

    Hello Sergey Slizovskiy,

    Generally you can install a package with the patch having only NoMachine access.

    If you are attached by NoMachine to physical session – the session is visible on physical screen. You can run terminal and install update package. You will be disconnected but after several minutes, when update finished you should be able connect again.

    If you are not sure that you are running physical session or you are running virtual NoMachine session, you can install ‘screen’ program:

    sudo apt update
    sudo apt install screen

    then run screen session -> execute in terminal:

    screen

    and in the screen session run NoMachine update:

    sudo dpkg -i nomachine_6.7.6_41_amd64.deb

    you will be disconnected, and after update finished you can connect by NoMachine again.

    As safe as updating NoMachine is, there is a risk that something totally unexpected could happen. This could affect the possibility of connecting via NoMachine.

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