- This topic has 3 replies, 2 voices, and was last updated 10 years, 12 months ago by
.
-
Posts
-
TL;DR – this may be procedural, but I cannot connect after the installation of the latest NoMachine client on Debian Wheezy right after the successful installation and services appear running normally.
I’ve used NoMachine in the past and the install was fairly easy from repo or download and run with the package manager. I never had to configure much, if at all for a few of the installations and I may be approaching this from a bias perspective. It was more like a ‘set it and forget it’ situation before for the last few weeks. Now with the newer version and a different distro, I’m not having such luck but I’m eager to get it working as I have homework to get completed within a month I need to do from outside of the home.
Installed latest NoMachine_4.0.366_1_amd64.deb package with the instructions on NoMachine’s site last night (this is the 3rd attempt). Worked like a charm and showed services were running, but I yet again failed to authenticate.
uname -a Linux LOCALHOST 3.2.0-4-<strong>amd64</strong> #1 SMP Debian 3.2.51-1 x86_64 GNU/LinuxSo my yes/no PEBCAK question: is the installation supposed to work “out of the box” after running the installation like in my past experiences? If yes: what logs do I need to gather and post. If no: then I need to read better documentation than the local READMEs and such on exactly what I’m doing wrong. This distro is freshly installed other than a few apps I got off of apt-get. I was running a bare metal hypervisor before and finally decided on Debian.
…After failing to find the right documentation to address the issue, I stated tinkering in the GUI, which was also having errors. Then I enabled upnp on the router (which I didn’t see as a prereq for the installation). Never liked upnp, but I need this to work. After that is enabled, NX is running. Then it check marks the box for the NX port that is active, but the SSH fails to configure with the above error in the gui. I tried searching Google and the forums and I’m honestly lost as I’m not finding the correct solution for Debian or like Debian distros. I tried tweaking the sshd conf and other stuff like cert gen, but nothing has worked, had to back out those bad changes, and I’ve been stuck for two weeks.
I am unable to establish a remote connection even with SSH enabled, with a non-root account, and it just fails right away (local LAN and Internet). I feel like I’m missing something obvious, but for the life of me I can’t find the most correct instructions for post installation configurations. Sort of stuck in a loop of scouring bing and google but no luck and the last several weeks I’ve spent most of my free time reading documentation, but it’s mostly not related to my single connection home environment.
*I’ve already uninstalled cleanly and reinstalled with a prior version as well. I thought it the moment to stopy wasting time and hopefully not waste other’s time and use the lastest.
Attempts to connect remotely result in the error “NX> 204 Authentication failed.” from Windows 7 machines. I have yet to test with another LInux or Mac device.
Occurs with the most recent NoMachine client for Windows 3.5.0_9.
Now, I believe I have a configuration error as the server appears to be running and the services are in the background, but I am not getting clear instructions when I search for post installations for Debian; instructions I have found were for the past versions of both nomachine (mostly the open source bit) and Debian (and not a mix of both) and the previous attempt to perform such actions in my install have resulted to a bunch of ssh keys being generated but never make a difference after sshd is updated. Plus the newer version likley works without much configs vs postings like this link here http://www.linuxquestions.org/questions/linux-software-2/a-guide-to-set-nomachine-nx-3-5-x-up-on-debian-wheezy-and-possibly-others-917816/
I’m attaching my sshd conf file and current gnome info (because it’s in what to include) – let me know if I can help fix this for myself and others by adding more logs to the fire. I’m hoping it’s something easy to correct.
Cheers!
Evidently, after looking at my post the attached files were blocked for security reasons.
The first one is the default config for SSHD on Debian Wheezy, or should be… I had to restore a few files:
# Package generated configuration file # See the sshd_config(5) manpage for details # What ports, IPs and protocols we listen for Port 22 # Use these options to restrict which interfaces/protocols sshd will bind to #ListenAddress :: #ListenAddress 0.0.0.0 Protocol 2 # HostKeys for protocol version 2 HostKey /etc/ssh/ssh_host_rsa_key HostKey /etc/ssh/ssh_host_dsa_key HostKey /etc/ssh/ssh_host_ecdsa_key #Privilege Separation is turned on for security UsePrivilegeSeparation yes # Lifetime and size of ephemeral version 1 server key KeyRegenerationInterval 3600 ServerKeyBits 768 # Logging SyslogFacility AUTH LogLevel INFO # Authentication: LoginGraceTime 120 PermitRootLogin yes StrictModes yes RSAAuthentication yes PubkeyAuthentication yes #AuthorizedKeysFile %h/.ssh/authorized_keys # Don't read the user's ~/.rhosts and ~/.shosts files IgnoreRhosts yes # For this to work you will also need host keys in /etc/ssh_known_hosts RhostsRSAAuthentication no # similar for protocol version 2 HostbasedAuthentication no # Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication #IgnoreUserKnownHosts yes # To enable empty passwords, change to yes (NOT RECOMMENDED) PermitEmptyPasswords no # Change to yes to enable challenge-response passwords (beware issues with # some PAM modules and threads) ChallengeResponseAuthentication no # Change to no to disable tunnelled clear text passwords #PasswordAuthentication yes # Kerberos options #KerberosAuthentication no #KerberosGetAFSToken no #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes # GSSAPI options #GSSAPIAuthentication no #GSSAPICleanupCredentials yes X11Forwarding yes X11DisplayOffset 10 PrintMotd no PrintLastLog yes TCPKeepAlive yes #UseLogin no #MaxStartups 10:30:60 #Banner /etc/tissue.net # Allow client to pass locale environment variables AcceptEnv LANG LC_* Subsystem sftp /usr/lib/openssh/sftp-server # Set this to 'yes' to enable PAM authentication, account processing, # and session processing. If this is enabled, PAM authentication will # be allowed through the ChallengeResponseAuthentication and # PasswordAuthentication. Depending on your PAM configuration, # PAM authentication via ChallengeResponseAuthentication may bypass # the setting of "PermitRootLogin without-password". # If you just want the PAM account and session checks to run without # PAM authentication, then enable this but set PasswordAuthentication # and ChallengeResponseAuthentication to 'no'. UsePAM yesThe later is the same default config, but for gnome:
ii gir1.2-gnomebluetooth-1.0 3.4.2-1 amd64 Introspection data for GnomeBluetooth ii gir1.2-gnomekeyring-1.0 3.4.1-1 amd64 GNOME keyring services library - introspection data ii gkbd-capplet 3.4.0.2-1 amd64 GNOME Panel applet for libgnomekbd ii gnome 1:3.4+7+deb7u1 amd64 Full GNOME Desktop Environment, with extra components ii gnome-accessibility-themes 3.4.2-2.1 all Accessibility themes for the GNOME desktop ii gnome-applets 3.4.1-3 amd64 Various applets for the GNOME panel - binary files ii gnome-applets-data 3.4.1-3 all Various applets for the GNOME panel - data files ii gnome-backgrounds 3.4.2-1 all Set of backgrounds packaged with the GNOME desktop ii gnome-bluetooth 3.4.2-1 amd64 GNOME Bluetooth tools ii gnome-color-manager 3.4.2-1 amd64 Color management integration for the GNOME desktop environment ii gnome-contacts 3.4.1-1+b1 amd64 Contacts manager for GNOME ii gnome-control-center 1:3.4.3.1-2 amd64 utilities to configure the GNOME desktop ii gnome-control-center-data 1:3.4.3.1-2 all configuration applets for GNOME - data files ii gnome-core 1:3.4+7+deb7u1 amd64 GNOME Desktop Environment -- essential components ii gnome-desktop3-data 3.4.2-1 all Common files for GNOME desktop apps ii gnome-dictionary 3.4.0-2 amd64 GNOME dictionary application ii gnome-disk-utility 3.0.2-3 amd64 manage and configure disk drives and media ii gnome-documents 0.4.2-2 amd64 Document manager for GNOME ii gnome-font-viewer 3.4.0-2 amd64 font viewer for GNOME ii gnome-games 1:3.4.2-3 all games for the GNOME desktop ii gnome-games-data 1:3.4.2-3 all data files for the GNOME games ii gnome-games-extra-data 3.2.0-4 all games for the GNOME desktop (extra artwork) ii gnome-icon-theme 3.4.0-2 all GNOME Desktop icon theme ii gnome-icon-theme-extras 3.4.0-1 all GNOME Desktop icon theme (additional icons) ii gnome-icon-theme-symbolic 3.4.0-2 all GNOME desktop icon theme (symbolic icons) ii gnome-js-common 0.1.2-1 all Common modules for GNOME JavaScript interpreters ii gnome-keyring 3.4.1-5 amd64 GNOME keyring services (daemon and tools) ii gnome-mag 1:0.16.3-1 amd64 a screen magnifier for the GNOME desktop ii gnome-media 3.4.0-1 amd64 GNOME media utilities ii gnome-menus 3.4.2-5 amd64 GNOME implementation of the freedesktop menu specification ii gnome-mime-data 2.18.0-1 all base MIME and Application database for GNOME. ii gnome-nettool 3.2.0-1 amd64 network information tool for GNOME ii gnome-online-accounts 3.4.2-2 amd64 GNOME Online Accounts ii gnome-orca 3.4.2-2 all Scriptable screen reader ii gnome-packagekit 3.4.2-2 amd64 Graphical distribution neutral software management tools ii gnome-packagekit-data 3.4.2-2 all Data files for graphical distribution neutral software management tools ii gnome-panel 3.4.2.1-4 amd64 launcher and docking facility for GNOME ii gnome-panel-data 3.4.2.1-4 all common files for the GNOME Panel ii gnome-power-manager 3.4.0-2 amd64 power management tool for the GNOME desktop ii gnome-screensaver 3.4.1-1 amd64 GNOME screen saver and locker ii gnome-screenshot 3.4.1-1 amd64 screenshot application for GNOME ii gnome-session 3.4.2.1-4 all GNOME Session Manager - GNOME 3 session ii gnome-session-bin 3.4.2.1-4 amd64 GNOME Session Manager - Minimal runtime ii gnome-session-common 3.4.2.1-4 all GNOME Session Manager - common files ii gnome-session-fallback 3.4.2.1-4 all GNOME Session Manager - GNOME fallback session ii gnome-settings-daemon 3.4.2+git20121218.7c1322-3+deb7u2 amd64 daemon handling the GNOME session settings ii gnome-shell 3.4.2-7+deb7u1 amd64 graphical shell for the GNOME desktop ii gnome-shell-common 3.4.2-7+deb7u1 all common files for the GNOME graphical shell ii gnome-shell-extensions 3.4.0-2 all Extensions to extend functionality of GNOME Shell ii gnome-sudoku 1:3.4.2-3 all Sudoku puzzle game for GNOME ii gnome-sushi 0.4.1-3 amd64 sushi is a quick previewer for nautilus ii gnome-system-log 3.4.1-3 amd64 system log viewer for GNOME ii gnome-system-monitor 3.4.1-2+b1 amd64 Process viewer and system resource monitor for GNOME ii gnome-terminal 3.4.1.1-2 amd64 GNOME terminal emulator application ii gnome-terminal-data 3.4.1.1-2 all Data files for the GNOME terminal emulator ii gnome-themes-standard 3.4.2-2.1 amd64 Standard GNOME themes ii gnome-themes-standard-data 3.4.2-2.1 all Data files for GNOME standard themes ii gnome-tweak-tool 3.4.0.1-2 all tool to adjust advanced configuration settings for GNOME ii gnome-user-guide 3.4.2-1+build1 all GNOME user's guide ii gnome-user-share 3.0.2-1 amd64 User level public file sharing via WebDAV or ObexFTP ii gnome-video-effects 0.4.0-1 all GNOME Video Effects ii libgnome-bluetooth10 3.4.2-1 amd64 GNOME Bluetooth tools - support library ii libgnome-desktop-3-2 3.4.2-1 amd64 Utility library for loading .desktop files - runtime files ii libgnome-keyring-common 3.4.1-1 all GNOME keyring services library - data files ii libgnome-keyring0:amd64 3.4.1-1 amd64 GNOME keyring services library ii libgnome-mag2 1:0.16.3-1 amd64 screen magnification library for the GNOME desktop (shared library) ii libgnome-media-profiles-3.0-0 3.0.0-1 amd64 GNOME Media Profiles library ii libgnome-menu-3-0 3.4.2-5 amd64 GNOME implementation of the freedesktop menu specification ii libgnome2-0 2.32.1-3 amd64 The GNOME library - runtime files ii libgnome2-common 2.32.1-3 all The GNOME library - common files ii libgnomecanvas2-0 2.30.3-1.2 amd64 powerful object-oriented display engine - runtime files ii libgnomecanvas2-common 2.30.3-1.2 all powerful object-oriented display engine - common files ii libgnomekbd-common 3.4.0.2-1 all GNOME library to manage keyboard configuration - common files ii libgnomekbd7 3.4.0.2-1 amd64 GNOME library to manage keyboard configuration - shared library ii libgnomeui-0 2.24.5-2 amd64 GNOME user interface library - runtime files ii libgnomeui-common 2.24.5-2 all GNOME user interface library - common files ii libgnomevfs2-0 1:2.24.4-2 amd64 GNOME Virtual File System (runtime libraries) ii libgnomevfs2-common 1:2.24.4-2 all GNOME Virtual File System (common files) ii libgnomevfs2-extra 1:2.24.4-2 amd64 GNOME Virtual File System (extra modules) ii libpam-gnome-keyring 3.4.1-5 amd64 PAM module to unlock the GNOME keyring upon login ii libreoffice-gnome 1:3.5.4+dfsg2-0+deb7u2 amd64 office productivity suite -- GNOME integration ii libsoup-gnome2.4-1:amd64 2.38.1-2 amd64 HTTP library implementation in C -- GNOME support library ii network-manager-gnome 0.9.4.1-5 amd64 network management framework (GNOME frontend) ii policykit-1-gnome 0.105-2 amd64 GNOME authentication agent for PolicyKit-1 ii python-gnome2 2.28.1+dfsg-1 amd64 Python bindings for the GNOME desktop environment ii task-gnome-desktop 3.14.1 all GNOME desktop environmentOccurs with the most recent NoMachine client for Windows 3.5.0_9
The most recent NoMachine client for Windows is probably a 4, not a 3.5, given that you say you have installed a 4.0.366 on Linux.
SSH connections are not supported in the free 4. This is stated in a multiple places in the docs, for example here:
Oh, so it’s not like the same connection type in the past? Aha – now that makes sense considering the NX protocol is not fully encrypted but optimized for speed. I failed to make that corelation before until now.
I also wasn’t aware that this was a 4 ‘free’ version linux and was quite a bit different from the past. I don’t need to use SSH. Thanks for clearing this up for me!
This topic was marked as closed, you can't post.