On Wed, 2006-11-15 at 12:16 +0800, Art Fore wrote: > > > On 11/15/06, Craig White <craigwhite@xxxxxxxxxxx> wrote: > On Wed, 2006-11-15 at 10:58 +0800, Art Fore wrote: > > > > > > On 11/14/06, Dr. Michael J. Chudobiak <mjc@xxxxxxxxxxxxxxx> > wrote: > > > > > > Art, here are some tips: > > > > 1) In the past, I found I had to run "passwd -uf nx" > to enable > > the nx > > user. The rpm didn't do it properly for some reason. > > > > 2) Make sure the client enables SSL encryption. > > > > 3) The rpm didn't uninstall properly, which really > messed > > things up. If > > you try to uninstall it, use rpm -evvv to get a > verbose output > > to see > > which files are causing trouble. > > > > Done the passwd -uf nx which reported success. SSL > encription is > > enabled. Still no luck. Client comes back with > > NX> 202 Authenticating user: nx > > NX> 208 Using auth method: publickey > > NX> 204 Authentication failed. > > > > Log file on server has Received signal 15, terminating. > > > > So, any further suggestions? > ---- > get the file > /etc/nxserver/client.id_dsa.pub > from the server > > paste it into the key on the client > > Copied the file to c:/documents and settings/art.fore/.ssh and .nx and > to c:\program files\nx client for windows\share\keys. Now the client > comes up with the same error, the server log only comes up with > connection closed by MailScanner warning: numerical links are often > malicious:10.18.31.29 (client IP address) > > What next? ---- keep failing until you follow instructions I would suppose Craig
