Gega

Forum Replies Created

Viewing 4 posts - 46 through 49 (of 49 total)
  • Author
    Posts
  • in reply to: Can’t connect to SLES 11 SP4 machine #13134
    AvatarGega
    Participant

    Hello

    It seems as a different problem so we need new logs, could you collect logs and send them to us the same way as earlier?

    in reply to: NX Server not starting #12658
    AvatarGega
    Participant

    Hello,

    From your “–restart” command output I assume that you are using NX 3.5 which doesn’t have any daemon, therefore no process is running unless you have running sessions. By “Service started” we mean that nxclient/nxplayer could connect.

    We recommend to upgrade to new version of NX. Current version is 5.1.54.

    in reply to: Can’t connect to SLES 11 SP4 machine #12365
    AvatarGega
    Participant

    Hello,

    In order to understand the cause of these problems we need debug logs from the server side. Please uncomment and set the ‘SessionLogLevel 7’ configuration key in the ‘/usr/NX/etc/server.cfg’ and ‘/usr/NX/etc/node.cfg’ files. Here you can find detailed info on how to gather logs: https://www.nomachine.com/DT07M00098.

    Then restart server, reproduce the issue and send the collected logs to forum[at]nomachine[dot]com.

    If it’s not possible to collect debug logs, than sending ‘/usr/NX/var/log/nxerror.log’ might help.

    in reply to: Custom commands #11848
    AvatarGega
    Participant

    Hello kgrzeska,

    Custom commands are not sent to custom scripts, so there is no way to control allowed commands from custom scripts, there is other way to control allowed commands. Our products: NoMachine Terminal Server, NoMachine Enterprise Server and NoMachine Cloud Server support profiles feature. Profiles can be used to define allowed command. The general format of the command is:

    nxserver –ruleadd –class session –type unix-script –value value OPTIONS

    value must be path to allowed command, e.g. /usr/bin/firefox.

    OPTION can be any of the following options:

    –system

    set the rule on a per-server basis. The rule will be applied to the whole NX System and to every user accessing it

    –user USERNAME

    set the rule on a per-user basis. The rule will be applied to the specified user only

    –guest

    the rule will be applied to all guest users and will not affect other users. Guest accounts are available only on Linux.

    –node NODE

    set the rule for the specified NODE only

    –group GROUP

    set the rule for the specified GROUP.

     

    Here are some examples how to set allowed commands using profiles:

    This command will set firefox as allowed command for user: adam :

    nxserver –ruleadd –class session –type unix-script –value /usr/bin/firefox –user adam

     

    This command will set firefox as allowed command for group: adam :

    nxserver –ruleadd –class session –type unix-script –value /usr/bin/firefox –group adam

     

    This command will set firefox as allowed command for everyone:

    nxserver –ruleadd –class session –type unix-script –value /usr/bin/firefox –system

     

Viewing 4 posts - 46 through 49 (of 49 total)