zaq

Forum Replies Created

Viewing 9 posts - 61 through 69 (of 69 total)
  • Author
    Posts
  • Avatarzaq
    Contributor

    Hello,
    Could you try to update to 4.4.6, please? There is a fix for SELinux
    Fedora 21.
    If the issue persists please gather debug information following the
    instructions here:

    https://www.nomachine.com/AR07K00677

    Also please save active processes:

    ps -Af | grep nx > processes.txt

    Send debug information and ‘processes.txt’ to issues[at]nomachine[dot]com.

    in reply to: NoMachine installation is automatically removed by AV #6163
    Avatarzaq
    Contributor

    Hello,

    We aren’t able to reproduce your problem in our lab. We need more
    details. Could you answer the questions which you skipped previously, please?

    1. Is your Norton AV set at the default configuration. If not, what has changed?
    2. Is there any clue as to which NoMachine file Norton AV treats as dangerous.
    Is it the installation package “nomachine_4.4.6_11.exe”(md5sum:
    7d9f1515598b562a0c61dcdc526a3a05)?
    3. Could you export the Norton report and send to us please?
    Anyway you can try to install once more NoMachine and check if your
    problem happens again. Please send attachments to forum[at]nomachine[dot]com.

    in reply to: NoMachine installation is automatically removed by AV #5957
    Avatarzaq
    Contributor

    Hello,

    We aren’t able to reproduce your problem in our lab. Could you tell me more details, please?

    1. Which version of NoMachine are you using? A full installation package name is enough.

    2. Which version of Norton AV do you have installed?
    In this link it tells you how to find the version:
    https://support.norton.com/sp/pl/pl/home/current/solutions/kb20080417101717EN_EndUserProfile_en_us

    3. Is your Norton AV set at the default configuration If not, what has changed?

    4. Is there any clue as to which NoMachine file Norton AV treats as dangerous.

    5. Which operating system do you have? (Windows XP, Windows Vista …; x64 or x32)

    6. Could you export the Norton report and send to us please?
    How to find the report:
    https://support.norton.com/sp/en/us/home/current/solutions/v23920762_NAV_Retail_2014_en_us

    Avatarzaq
    Contributor

    Hello,

    The free version of NoMachine doesn’t support SSH connections. You should check point 1.3 of the installation guide:

    https://www.nomachine.com/DT09K00056

    TR06J02727 is related to the a very early beta version of NoMachine, which supported the SSH protocol.

    In answer to your questions, when you use a NoMachine product with SSH support then:

    1. In /var/NX/nx/.ssh/known_host is a public key.
    Files: default.id_dsa.pub and restore.id_dsa.pub are only backups.

    2. The privet key of a user nx is in: /usr/NX/share/keys/server.id_dsa.key

    Avatarzaq
    Contributor

    Hello,

    The free version of NoMachine doesn’t support SSH connections. You should check point 1.3 of the installation guide:

    https://www.nomachine.com/DT09K00056

    This is why ‘nxserver –checkssh reports an error. This is used by other NoMachine products, which support the SSH protocol.

    Instead of using ‘nxserver –checkssh’ to verify your installation you can use:

    /etc/NX/bin/nxserver –status

    The output of the command should be:

    NX> 161 Enabled service: nxserver.
    NX> 161 Enabled service: nxnode.
    NX> 161 Enabled service: nxd.

    In the case of NoMachine (free), ‘–checkssh’ is unnecessary but harmless. We will remove it.

    Avatarzaq
    Contributor

    Hi,

    We have reproduced your issue. We have inserted a new Trouble Report at http://www.nomachine.com/TR06L04470. We will fix this problem in the next release.

    in reply to: Question for NoMachine configuration #3886
    Avatarzaq
    Contributor

    Hi,

    We reproduced the issue related with the main menu in our test laboratory. We also have a workaround for it:

    In file:

    /usr/share/desktop-directories/NoMachine-dir.directory

    Change the line from:

    ‘Comment=’

    to

    ‘Comment=NoMachine’

    This should be enough. If not then log out and log in.

    We will fix this issue in the next release.

    Avatarzaq
    Contributor

    Value of AvailableSessionTypes entry is reseting during update. This is list of keys which are re-set during every update:
    – server.cfg

    ClientConnectionMethods
    AvailableSessionTypes

    – node.cfg

    Most of those keys keeps the paths to system tools. The paths are refreshed during every update/upgrade.

    CommandFuser
    CommandLsof
    CommandXdpyInfo
    CommandXmodmap
    CommandXkbComp
    CUPSBinPath
    CUPSSbinPath
    CUPSBackendPath
    EnableCUPSSupport 1 (checks if CUPS is available if YES, set to “1”)
    ClientConnectionMethods
    AudioInterface (checks which audio tool is available)
    CommandStartPulseAudio
    EnableSMBFSSupport
    AvailableSessionTypes

    Your old *.cfg file has changed name:
    server.cfg -> server.cfg.backup
    node.cfg -> node.cfg.backup
    You can easly restore your old *cfg file.

    If any entry during update is duplicated it’s a bug. Could you send more information about the case. A *cfg file with double entries will
    be helpful and also /usr/NX/var/log/nxinstall.log and the /usr/NX/var/log/nxupdate.log files from the server side installation.

    These files you can attach here or send to issues[at]nomachine[dot]com.

    Avatarzaq
    Contributor

    Hi,

    After the update all services should be working. The update procedure updates the configuration files (*.cfg)
    only for adding new configuration keys. Your settings in the *.cfg files shouldn’t be changed, likewise license
    files (*.lic) aren’t overwritten and files in  NX/etc/keys/ remain the same.

    No special package. As explained above, the update procedure is intended to preserve current configurations and settings.
    If this is not the case, ie. you have found your configuration or keys changed, please tell us what these are.

    Logs would also be useful which you can attach here or send to issues[at]nomachine[dot]com

    We will need the /usr/NX/var/log/nxinstall.log and the /usr/NX/var/log/nxupdate.log  files from the server side installation.

Viewing 9 posts - 61 through 69 (of 69 total)