Results 1 to 8 of 8

Thread: NX NOMACHINE 3.5

  1. #1
    Join Date
    Jun 2008
    Location
    South-West France
    Posts
    1,036

    Default NX NOMACHINE 3.5

    Hello.

    After doing somme test (NX ran correctly for a month), I reinstalled NXSERVER from the new version 3.5.

    I am not able to make NXSERVER running.

    I know that i had to tweek the previous install, but I can't imagine now what I did.

    What is sure :
    There is no firewall
    NX : You canNOT change the NX AuthorizedKeysFile path
    ( NXSERVER look to /usr/NX/.............. )
    SSH : : You can change the ssh AuthorizedKeysFile path
    Authentication only by Key, not by password.
    During this test I use the root user.
    I can connect with SSH from the two computers from any side.
    NX : the builtin user nx is added by hand to an ssh_user group.
    NX : root is allowed.
    SSH : the builtin user root is added by hand to an ssh_user group.
    NX or SSH or BOTH : It seems you cannot change the owner ( I am not sure )

    What I tried :
    Merging key in AuthorizedKeysFile NX side or SSH side seems not to work.

    Problem : user nx failed to authenticate
    In fact, reading the logs I see that the key is not found.
    Normal because user nx as no key; so how can he authenticates ?


    Help should be welcome.
    Thanks for helping. JCD
    __________
    server leap 15.0 -- ASUS g75vw KDE leap 15.0 -- ASUS g750JZ Optimus KDE leap 15.1 -- acer aspire s13 win 10 home -- HP Omen win 10 home - scan EPSON V500 - Brother HL2250DN - Samsung CLP-325W

  2. #2

    Default Re: NX NOMACHINE 3.5

    Nxserver typically uses nomachine's key, sounds like you haven't configured your server to use it

    I don't know whether you're using nomachine's server or the freenx server, I've only used the freenx server and this is how you set it up:

    As root, in a terminal (konsole if you use kde) run this command: nxsetup --install --setup-nomachine-key --clean --purge

    You may not actually need the --clean & --purge switches but if you do the settings from your old version will be removed before applying the settings for your updated server and that way you are less likely to have any erroneous settings from your old configuration causing any problems

    If after doing that you still have issues there are two things you can try, firstly remove all the files under /home/username/.nx, this will make sure the user you are trying to connect with won't have anything like old configuration or session data that may be interfering

    The second thing you can try if it still doesn't work is adding any users you want to grant nx access to the nx group

  3. #3
    Join Date
    Jun 2008
    Location
    South-West France
    Posts
    1,036

    Default Re: NX NOMACHINE 3.5

    After doing somme test (NX ran correctly for a month), I reinstalled NXSERVER from the new version 3.5.
    I am not able to make NXSERVER running.
    I know that i had to tweak the previous install, but I can't imagine now what I did.
    I am using nomachine nxserver , not freenx.

    What is the difference between them ?
    Thanks for helping. JCD
    __________
    server leap 15.0 -- ASUS g75vw KDE leap 15.0 -- ASUS g750JZ Optimus KDE leap 15.1 -- acer aspire s13 win 10 home -- HP Omen win 10 home - scan EPSON V500 - Brother HL2250DN - Samsung CLP-325W

  4. #4

    Default Re: NX NOMACHINE 3.5

    Freenx is free, nomachine are a commercial company and whilst you can download and install their server for free it has a limitations on how many connections you can use at any given time

    You can find instructions on installing and configuring nomachine's server here if you haven't looked through them already:

    NoMachine NX - Support: Documents

  5. #5
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,654

    Default Re: NX NOMACHINE 3.5

    Allow me to add also an alternative (I used myself FreeNX for several years)
    which is very interesting, X2Go, it is available from the OBS.
    http://download.opensuse.org/reposit.../openSUSE_11.4
    A description can be found here http://www.x2go.org

    It is maybe of interest for you because NX from Nomachine will switch with
    the upcoming version 4.0 to a closed source license and it is unclear if
    there will be free (as free beer) licenses in the future.

    --
    PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.4 | GeForce
    9600 GT | 4GB Ram
    Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.4 | nVidia
    ION | 3GB Ram

  6. #6

    Default Re: NX NOMACHINE 3.5

    About to go away for a few days but I've bookmarked that for a look when I get back, cheers for the link

  7. #7

    Default Re: NX NOMACHINE 3.5

    Quote Originally Posted by jcdole View Post
    I am using nomachine nxserver , not freenx.

    What is the difference between them ?
    • NoMachine server allows only one (maybe two) clients to connect. FreeNX doesn't have this limitation.
    • While using xdm (gdm,kdm), NoMachine displays the session manager login where you can choose the desktop environment or window manager to start. FreeNX starts the default window manager - the one saved in the variable WINDOW_MANAGER or WINDOWMANAGER - (although I might have configured things that way). Therefore with FreeNX, a session manager doesn't need to be running on the server for xdm connections. Actually the server doesn't need to be running X at all. With NoMachine, you will get a blackscreen and an error message if you request an xdm connection while X is not runnign on the server:


    • FreeNX plays well with NoMachine and can forward connections destined to NoMachine to a specific port. You'll use the following settings in /etc/nxserver/node.conf (the port is up to you but should be open for ssh incoming connections):

      Code:
      ENABLE_NOMACHINE_FORWARD_PORT="1"
      NOMACHINE_FORWARD_PORT="9123"
      
      NOMACHINE_SERVER="/usr/NX/bin/nxserver"
      NOMACHINE_NX_HOME_DIR="/usr/NX/home/nx"
    • For FreeNX, make sure the keys are in /var/ib/nxserver/home/.ssh and belong to the user 'nx'
    • For NoMachine make sure the keys are in /usr/NX/home/nx/.ssh and belong to the user 'nx'
    • In both cases, make sure the know_hosts file is present is this directory and refers to the correct host (the server).
    • Check the home directory of the nx user in /etc/passwd (in particular when using both servers)


    When 11.4 was released, I had trouble with FreeNX and compiled version 0.7.3 myself. It is available in my repo. I presume it has been fixed in the meantime though.

    Index of /repositories/home:/please_try_again/openSUSE_11.4

  8. #8
    Join Date
    Jun 2008
    Location
    South-West France
    Posts
    1,036

    Thumbs up [SOLVED] NX NOMACHINE 3.5

    Hello.

    First I thank you all for helping.

    I will look next time for freenx If necessary.

    Now my problem.

    The SAMBA-LDAP SERVER CONFIG

    1°) Have removed nxserver and associate directories.

    2°) Have removed ssh config files and keys

    3°) Have force software update for SSH

    4°) Have modify new ssh config file. Most important parameters :
    • Port 22
    • AddressFamily inet
    • Protocol 2
    • HostKey /etc/ssh/ssh_host_dsa_key
    • AuthorizedKeysFile %h/.ssh/authorized_keys2
    • PermitRootLogin yes
    • AllowGroups ssh_user
    • PasswordAuthentication no
    • UsePAM yes
    • X11Forwarding yes


    5°) Have generate new DSA key

    6°) In /root/.ssh have make a hard link from authorized_keys to authorized_keys2

    7°) Copy key to remote machine

    - - - - - -

    8°) Configure the remote machine same way but as there is no nxserver on the remote machine some parameters desappear.
    • Port 22
    • AddressFamily inet
    • Protocol 2
    • # HostKey /etc/ssh/ssh_host_dsa_key
    • # AuthorizedKeysFile %h/.ssh/authorized_keys2
    • PermitRootLogin yes
    • # AllowGroups ssh_user
    • PasswordAuthentication no
    • UsePAM yes
    • X11Forwarding yes


    9°) Have generate new DSA key

    10°) In /root/.ssh have make a hard link from authorized_keys to authorized_keys2

    11°) Copy key to the samba-ldap server

    12°) test ssh connection from both side to other machine --> OK

    13°) test ssh connection from same side to same machine --> OK

    - - - -

    14°) Return to the SAMBA-LDAP server and install NOMACHINE nxserver
    following the documentation.
    Set SSHD port as configured in sshd_config for all config files relative to nxzzzzz software

    15°) Generating a new DSA key-pair

    16°)
    chown nx:root /usr/NX/home/nx/.ssh/authorized_keys2
    chmod 0644 /usr/NX/home/nx/.ssh/authorized_keys2

    chown nx:root /usr/NX/home/nx/.ssh/default.id_dsa.pub
    chmod 0644 /usr/NX/home/nx/.ssh/default.id_dsa.pub

    17°) On the client install NOMACHINE NX CLIENT

    18°) Distribute the private key from nx server to clients, place it under the subdirectory 'usr/NX/share/keys' and localy on the server for testing connection locally.

    19°) Test nx user localy on the server
    ssh -i /usr/NX/share/keys/server.id_dsa.key nx@my_server
    HELLO NXSERVER - Version 3.5.0-4 - LFE
    NX> 105 quit
    Quit
    NX> 999 Bye.
    Connection to my_server closed.

    19°) Configure NX CLIENT by running nxclient --wizard.

    20°) Test connection from remote to server --> OK.
    Get server screen on my laptop.

    21°) change everywhere SSHD STANDARDPORT (22) to non generic port.

    Thanks to all
    Thanks for helping. JCD
    __________
    server leap 15.0 -- ASUS g75vw KDE leap 15.0 -- ASUS g750JZ Optimus KDE leap 15.1 -- acer aspire s13 win 10 home -- HP Omen win 10 home - scan EPSON V500 - Brother HL2250DN - Samsung CLP-325W

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •