Mailinglist Archive: opensuse (4344 mails)
| < Previous | Next > |
Re: [SLE] Suse 9.3 + FreeNX no connection]
- From: Art Fore <art.fore@xxxxxxxxxxx>
- Date: Fri, 05 Aug 2005 20:48:44 -0700
- Message-id: <1123300124.7970.31.camel@xxxxxxxxxx>
On Fri, 2005-08-05 at 23:21 -0400, Christopher Shanahan wrote:
> On Friday 05 August 2005 23:07, Art Fore wrote:
> > Tried uninstalling everyting on the server, and reinstalling following
> > an email on the freenx site for suse 9.3.
> >
> > Still get
> > NX> 203 NXSSH running with pid: 18116
> > NX> 285 Enabling check on switch command
> > NX> 285 Enabling skip of SSH config files
> > NX> 200 Connected to address: 192.168.0.4 on port: 22
> > NX> 202 Authenticating user: nx
> > NX> 208 Using auth method: publickey
> > NX> 204 Authentication failed.
> >
> > Why is authenticating user nx? seems like it should be afore.
>
> User 'nx' is used for the _first_ authentication. Read some of the other
> threads on that list (FreeNX), you'll see other mentions to that affect.
> You'll also see that a _large_ majority of the authentication issues are not
> issues related to nx, but to ssh.
>
> > Also tried KNX, still no connection
>
> I was not able to get knx to work either. I use the free client provided by
> NoMachine. Works great!
>
> Regards.
>
> --
> Christopher Shanahan
On the freenx email that I am reading which comes also from the suse
9.3 /usr/share/doc/packages/FreeNx/READMEN.SUSE, it says
distribute the
generated private key (/home/.nx//.ssh/id_dsa) to your clients
There is no such animal.
Changed the file permissions as mentioned in the file for the authorized_keys, & authorized_keys2, etc, still no change
Wanted to try
" so all users will
be able to login with their normal passwords. Set
"ENABLE_PAM_AUTHENTICATION" to "0" in /usr/bin/nxserver to disable
PAM_AUTH. In this case you need to add your users (again as root),
like "nxserver --adduser " and "nxserver --passwd". The user must
exist in the system database for local users first."
But there is no such "ENABLE_PAM_AUTHENTICATION" in the nxserver script. No info on where to add or what the correct syntax is. Anyone have any idea about this?
Art
> On Friday 05 August 2005 23:07, Art Fore wrote:
> > Tried uninstalling everyting on the server, and reinstalling following
> > an email on the freenx site for suse 9.3.
> >
> > Still get
> > NX> 203 NXSSH running with pid: 18116
> > NX> 285 Enabling check on switch command
> > NX> 285 Enabling skip of SSH config files
> > NX> 200 Connected to address: 192.168.0.4 on port: 22
> > NX> 202 Authenticating user: nx
> > NX> 208 Using auth method: publickey
> > NX> 204 Authentication failed.
> >
> > Why is authenticating user nx? seems like it should be afore.
>
> User 'nx' is used for the _first_ authentication. Read some of the other
> threads on that list (FreeNX), you'll see other mentions to that affect.
> You'll also see that a _large_ majority of the authentication issues are not
> issues related to nx, but to ssh.
>
> > Also tried KNX, still no connection
>
> I was not able to get knx to work either. I use the free client provided by
> NoMachine. Works great!
>
> Regards.
>
> --
> Christopher Shanahan
On the freenx email that I am reading which comes also from the suse
9.3 /usr/share/doc/packages/FreeNx/READMEN.SUSE, it says
distribute the
generated private key (/home/.nx//.ssh/id_dsa) to your clients
There is no such animal.
Changed the file permissions as mentioned in the file for the authorized_keys, & authorized_keys2, etc, still no change
Wanted to try
" so all users will
be able to login with their normal passwords. Set
"ENABLE_PAM_AUTHENTICATION" to "0" in /usr/bin/nxserver to disable
PAM_AUTH. In this case you need to add your users (again as root),
like "nxserver --adduser " and "nxserver --passwd". The user must
exist in the system database for local users first."
But there is no such "ENABLE_PAM_AUTHENTICATION" in the nxserver script. No info on where to add or what the correct syntax is. Anyone have any idea about this?
Art
| < Previous | Next > |