brotech

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 93 total)
  • Author
    Posts
  • brotech
    Participant

    Hello,
    the url to download recent package has been changed, now it is:

    https://www.nomachine.com/free/linux/64/deb
    

    Replaced ‘download’ by ‘www’. So, full command now is:

    wget https://www.nomachine.com/free/linux/64/deb -O nomachine.deb
    
    in reply to: Unable to connect after some amount of time #28638
    brotech
    Participant

    Hello,
    seems that are some problems with correct handling of the Fedora 32 Login Window.

    The workaround should be to set in /usr/NX/etc/server.cfg:
    PhysicalDesktopAuthorization 0

    It disables asking for access to the desktop, so use only if there is no other user on that host which should access the desktop.

    And the second thing is that switch doesn’t work correctly after login/logout to desktop
    so you need to disconnect and connect again.

    brotech
    Participant

    Hello am312,
    currently, NX doesn’t require Internet access to confirm the license.

    in reply to: Password required for private key connection #28560
    brotech
    Participant

    Hello,
    yes it should work without additional methods.

    Can you please enable debug on server side, restart nxserver then reproduce issue, collect logs and send as mail attachment to address forum (at) nomachine.com with title
    “password-required-for-private-key-connection”

    Detailed instructions about collecting logs on both side(client and server)
    are available here:
    https://www.nomachine.com/AR10K00697 (for server side logs)
    and https://www.nomachine.com/DT10O00163#2 (client side).

    Regards

    brotech
    Participant

    Hello,

    if I understood correctly, you are trying connect to ‘clients’, when client means only nxplayer.

    What have you installed on the Mac hosts that you want to connect?

    You should have Enterprise Desktop installed in order to share the desktop. You can add them to the Cloud Server using the command:

    /etc/NX/nxserver --serveradd hostname

    executed on Cloud Server as administrator or through sudo.

    After that students should see a list of available desktops in Cloud Server. If you would like assign a student to a particular ED host, without the need for them to select the host itself, You can use:

    /etc/NX/nxserver --useredit student_username --forward-connection ed_host:4000

    Regards

    in reply to: Large amount of folders #28487
    brotech
    Participant

    Hello Ernest,
    in that location, NX creates a session’s directory. But when the session finishes,
    it is cleaned up. When a session ‘fails’, that directory is renamed to F-session_dir, which allows to find the reason why the session failed.

    Anyway, a ‘large amount’ of folders is the sign of problems on that host, and it is not a common case.

    Can you share the whole log directory (with that node subdirectory) ?

    $ cd “/Library/Application Support/NoMachine/var/”
    $ sudo tar cvfz NoMachine-log.tar.gz log

    And please send NoMachine-log.tar.gz as an attachment by e-mail to:
    forum[at]nomachine[dot]com with subject:
    “LARGE amount of folders”.

    regards

    brotech
    Participant

    Hello Paul,

    The command /etc/NX/nxserver run nxserver depends on the configuration used
    during the installation. Which kind of package did you install ?

    Could you please share some details about your linux platforms/distro, and show for example the output of ‘uname -a’ command ?

    Regards

    in reply to: NX service not accessible #27814
    brotech
    Participant

    Hello,
    it looks very likely to be: https://www.nomachine.com/TR04R09623
    “The nxservice service starts and stops after 10-30 seconds”
    workaround is inside.

    Please let me know if it helps.

    brotech
    Participant

    This step:
    “get the latest version of NoMachine on the web site”

    can be done using the command as:

    wget https://download.nomachine.com/free/linux/64/deb -O nomachine.deb

    it will download the most recent deb package.

    brotech
    Participant

    Hello Zenith,

    logs which you sent don’t have enabled debug for NXServer. And so I cannot help you.

    Please to run this command on the server host:

    sudo /etc/NX/nxserver --debug --enable server

    You should see ouput as:

    NX> 900 Debug mode enabled for: server
    

    What does nxserver report to you when you run that command?

    brotech
    Participant

    Hello Zenith, can you enable debug on server side using a command executed on your linux host (nxserver side) by root:

    /etc/NX/nxserver --debug --enable server

    or using sudo:
    sudo /etc/NX/nxserver --debug --enable server

    After enabling debug, please connect and login from your connecting client and with user ‘oem’.

    When the problem appears again please share nxserver.log, nxerror.log files from /usr/NX/var/log/ directory and additionally /var/log/auth.log file,
    and attach also server configuration file (/usr/NX/etc/server.cfg).

    All those files please send to forum[at]nomachine[dot]com with subject:
    “cant-login-authentication-failed-please-try-again”

    Reproducing problem with enabled debug should allow us to find a reason for problem.

    Regards

     

     

    brotech
    Participant

    NX is using MDNS protocol for advertise its presence to other NoMachine computers, visible for example in third party tool – Wireshark.

    brotech
    Participant

    Hello,

    Preventing a user from logging in to an ED is achieved by ensuring that a user always logs in to the same host. You do this by setting “forward connection” to the specific ED for a particular user. If admin sets this for all users, then you can avoid showing ED hosts which are available and/or unavailable: the user will simply go the to ED which is for him only.

    root@cs3:~# /etc/NX/nxserver –useredit adam –forward-connection ed1
    NX> 106 Modifying settings for user: adam

    root@cs3:~# /etc/NX/nxserver –userlist
    NX> 149 NX users list

    Username   NX administrator Redirected to Trusted physical for Trusted virtual for Screen sharing Access  Forwarded to
    ———- —————- ————- ——————– ——————- ————– ——- ————————————
    adam                                                                            enabled        enabled 9de912ca-ae7b-45c2-8234-f75d363b086f

    How user adam will connect to ED1? It depends on the serveradd options which are ‘ –forward-nx-methods token|system|tunnel’.
    ‘token’ and ‘system’ mean that nxplayer will disconnect from CS and connect directly to ED1, where tunnel
    means that whole connection will go through CS. You can check how your forwarding methods are set using:
    /etc/NX/nxserver --serverlist

    and modify using /etc/NX/nxserver --serveredit

    There is a FR03R03953, “Displaying the number of users connected to the child servers”
    which should be release soon in a maintenance update for v6. This might be of interest to you as well.

     

    in reply to: Authentication as user NX using the NX SSH pair failed #26267
    brotech
    Participant

    The value of server configuration file SSHAuthorizedKeys, need to be the same as value of SSHD’s AuthorizedKeysFile config key. When is different
    authentication base on pair keys will doesnt work.

    NXServer config file should be in: /usr/NX/etc/server.cfg
    SSHD config file: /etc/ssh/sshd_config

    in reply to: Unable to connect from Windows 7 to Ubuntu 18.04 #25211
    brotech
    Participant

    Hell ndavrr,
    in the NX player on Windows 7 you should use the IP of the ubuntu machine (which I understand you are doing). The port depends on the protocol (not display), for sessions using the NX protocol, the default port is 4000; for SSH connections the port is 22.

    NoMachine Player first connects to the NoMachine server, asks for authorization and then you choose a session to attach to or you create one.

Viewing 15 posts - 16 through 30 (of 93 total)