[FreeNX-kNX] Timeout problems, user ssh login never attempted (mac problem?)

[David Mohr]

On Tue, May 26, 2009 at 11:43 PM, David Mohr <damailings at mcbf.net> wrote:
> Hi everyone,
> we've been using freenx for a while now, and it has served us very
> well, a big thanks to everyone involved in the project.
>
> Recently one of our users started having a problem with logging in; it
> always times out. We've tried everything we could to debug the
> problem, but it is very puzzling. We removed ~/.nx on both the server
> and the client for the user. free using the default ssh
> authentication.
>
> The detailed output is always:
> ---SNIP---
> NX> 203 NXSSH running with pid: 1159
> NX> 285 Enabling check on switch command
> NX> 285 Enabling skip of SSH config files
> NX> 285 Setting the preferred NX options
> NX> 200 Connected to address: xx.xx.xx.147 on port: 22
> NX> 202 Authenticating user: nx
> NX> 208 Using auth method: publickey
> ---SNAP---
>
> I can see the successful authentication for user `nx' in my logs. Yet
> there is no attempt at an authentication for the user account (no
> second connection attempt to ssh is ever made). Also there is no entry
> in /var/log/nxserver.log . For all working connections, I see plenty
> of output in the nxserver.log file, so there is no general problem
> with logging.
>
> The client is running Mac OS X, and the log file is attached. All
> working clients are using either Linux or Windows without problems.
>
> So the client seems to time out because the server fails to send more
> messages. But how can I debug this when I don't get any entries in the
> server log?
>
> Any help would be greatly appreciated.

We've done some more tests, and it seems like this issue is somehow
connected to an OS X 10.5.7 update which was installed last week. We
have two machines (both Intel), which behave as described above, for
different user accounts. We updated a PPC Mac to 10.5.7, and it
continued to work.

Has anyone else had issues with Mac OS X clients? For what it's worth,
I also tried to install the nomachine free-edition on a different
machine, and the troublesome clients still can't connect, while it
works for everyone else.

~David