zaq

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 69 total)
  • Author
    Posts
  • in reply to: NoMachine broken on Windows 10 #33551
    zaq
    Contributor

    You should get an output like:

    “The command completed successfully.”

    Looks like something is wrong with creating user accounts on your system.

    Could you check if user nx is present in a list of all of your users:

    net user

    if there is an nx user, please remove it by:

    net user nx /DEL

    We need to check system logs related to user management. You can enable it by:

    1. Click ‘Start’.
    2. Find Administrative Tools
    3. Open Local Security Policy
    4. Go to Audit Policy
    6. Enable AuditAccountManagement for Success and Failure:

    Click right button of the mouse on ‘Audit account management, go to Properties -> Audit these attempts,
    enable Success and Failure.

    After that you can check the logs:

    1. Go back to Administrative Tools.
    2. Open Event Viewer
    3. Go to: Windows Logs -> Security
    4. Create again the account:

    net user nx "YOUR_PASSWORD" /y /ADD

    5. In Event Viewer window click Action->Refresh, check logs related to creating user nx account, They have
    ‘User Account Management’ type in Task Category column.

    After that, you can disable system logs related to user management by restoring to original values AuditAccountManagement Policy.

    in reply to: NoMachine broken on Windows 10 #33294
    zaq
    Contributor

    The problem is directly related to this command:

    net user nx “PASSWORD” /y /ADD

    Could you:

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

    2) Run this command:

    net user nx "YOUR_PASSWORD" /y /ADD

    3) Send the whole output from the command to forum[at]nomachine[dot]com please?

    in reply to: NoMachine broken on Windows 10 #33195
    zaq
    Contributor

    NoMachine server software needs nx user for its proper working. You can find more information here:

    https://knowledgebase.nomachine.com/AR01N00871

    If you just need to connect from the Windows machine to another computer you can install nomachine-enterprise-client package. It doesn’t need nx user:

    https://www.nomachine.com/download/download&id=16

    To investigate the problem please pack a folder with logs:

    C:\ProgramData\NoMachine\var\log

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

    in reply to: NoMachine broken on Windows 10 #33133
    zaq
    Contributor

    Hello pnunn

    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: Server status : Querying the server problem again #32458
    zaq
    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
    zaq
    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
    zaq
    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
    zaq
    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
    zaq
    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
    zaq
    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
    zaq
    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
    zaq
    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
    zaq
    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
    zaq
    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?

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

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