Automatic disconnection on one side

Forum / NoMachine for Linux / Automatic disconnection on one side

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #10443


    I have tested with success NoMachine 4 client ( opensuse 12.3 ).

    Now I have a try with 3 linux box running kde 4.14 ( machine A, B, C ) and kernelĀ  3.16.7 and NoMachine 5.0.63 on opensuse 13.2 (x86_64)

    The NoMachine configuration files ( node.cfg and server.cfg ) are identical for each machine.

    SSH and firewall are supposed to have the same configuration files.

    The router for the local network (wired, wifi) is a netgear 6300v2 which act also as a dhcp server.

    Any of the Linux machineĀ  can connect to each other via ssh from any side ( a-b or b-a // a-c or c-a // b-c or c-b ) and can exchange files. SSH use a different port than NX which does not use port 4000.

    Using NoMachine, machine a and c can connect from any side ( a-c or c-a )

    Machine a can connect to machine b, but not from other side ( b to a )

    Machine c can connect to machine b, but not from other side ( b to c )

    The disconnection arise a few seconds after the connection.

    During this test, the firewalls are stopped.

    All the test are made under root account.

    Any help is welcome.



    With logs provided, the problem is hard to debug, to handle it we would require
    more data.

    Please set in the node.cfg:

    SessionLogClean 0

    Also it seems, that master agent hangs in this case, so please add this line at the
    bottom in the server.cfg:

    dumpCoreOnHang 1

    This will cause the server to kill node with signal 11 instead of 9, so please make sure
    the system can handle core dumps.
    After this please restart the nomachine server:

    /etc/NX/nxserver –restart

    Reproduce the problem and send the server and node logs as previously. We would also
    require the full agent logs, so please include the full:



    When the problem is reproduced, please do:

    /etc/NX/nxserver –restart

    again so, if the Agent hanged, the system produce core report for nxnode process. We would
    require the backtrace of all threads. The instruction is available here:

    Also include the logs from client machine: .nx directory in user’s home.
    In case of uncertainty please consult article on collecting logs:

    Send all logs on to forum[at]nomachine[dot]com making sure to reference your topic in message title.

    And some finishing questions: have you tried to log in as different user than root? Do the same problems happen?
    Also is the machine you are trying to connect to on user desktop or Login Window?

Viewing 2 posts - 1 through 2 (of 2 total)

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.