[FreeNX-kNX] HELP: Authentication Completed ... Negotiating link parameters ... Connection timeout

[Jonathan Chen]

Okay, I may have found the possible problem that is causing all users not
able to get on the server.  I simply rebooted the server to regain the NFS
mounted drive access(tried umount and it failed).  I hope that was problem
since I kept seeing

 /users/jona/.nx/C-hostname-1000-E5BC8F11E71604D83E4874396500DFEA/session:
 Stale NFS file handle
 tail: no files remaining

Now my question is, how should I resolve the problem if the cause of my NX
login is the NFS server?  It's strange that NX did not work while I am still
able to log in via regular ssh and see all the files in my home dir.  I
would like a solution where users are able to log in even if there is an NFS
issue where the users home dir is located.

Much appreciated if someone had similar problem like mine that is resolved.

-Jonathan


> ------------------------------  
> 
> Message: 2
> Date: Tue, 22 Feb 2005 13:39:29 -0800
> From: "Jonathan Chen" <jonachen at cisco.com>
> Subject: [FreeNX-kNX] HELP: Authentication Completed ... Negotiating
> 	link	parameters ... Connection timeout
> To: <freenx-knx at kde.org>
> Message-ID: <200502222139.j1MLdQq8021889 at sj-core-2.cisco.com>
> Content-Type: text/plain;	charset="us-ascii"
> 
> Hey all,
> 
> I need help diagnosing a constant problem that I am having.  
> It happens
> intermittently and have no clue why it works again.
> 
> I've used the 
> =====================================
> Date: Sun, 13 Feb 2005 23:40:24 +0100
> From: Fabian Franz <FabianFranz at gmx.de>
> Subject: [FreeNX-kNX] [PATCH] Fix for Windows resume problems
> =====================================
> 
> And that did not help much to resolve my issue.   Maybe I applied it
> incorrectly since I actually added a couple of # remark lines before
> applying the the patch.
> 
> Looking at the nxserver.log file does not help???  Out of the ordinary
> are...
> 
> NX> 148 Server capacity: not reached for user: jonachen
> NX> 704 Session cache: unix-kde
> NX> 707 SSL tunneling: 1
> NX> 710 Session status: running
> tail:
> /users/jona/.nx/C-hostname-1000-E5BC8F11E71604D83E4874396500DF
> EA/session:
> Stale NFS file handle
> tail: no files remaining
> NX> 1001 Bye.
> 
> 
> Any ideas?  Please let me know what other info that you need.
> 
> Thanks!
> 
> -Jon
> RHEL 3
> FreeNX 0.2.7?  Before the 0.2.8 security patch release...
> 
>