[FreeNX-kNX] Timing Out

chris at ccburton.com chris at ccburton.com
Wed Aug 19 18:31:45 UTC 2009


Andrew Villano <AVillano at incentient.com> wrote on 19/08/2009 18:45:23:

> Hello,
> 
> I used that command from one linux box to the nxhost successfully. 
> It does connect. 
> 
> However, the client I am having a problem with is a windows client.
> 
> The windows client says “connected to *Host* but then soon after 
> times out. I have the client key stored in the application.



I would copy the key across again then next and hope that fixes it !!

Next will be re-installing latest windows client version etc etc

But

It shouldn't be taking a minute to connect. Do you have dns reverse 
lookups stopping the job or broken routing??




Did you get the HELLO NXSERVER - Version  etc etc prompt from ssh.

Can you get a full working session using a linux client ??




> 
> Warmest Regards,
> 
> Andrew Villano
> Systems Specialist
> Incentient LLC
> 
> From: chris at ccburton.com [mailto:chris at ccburton.com] 
> Sent: Wednesday, August 19, 2009 12:42 PM
> To: User Support for FreeNX Server and kNX Client
> Subject: Re: [FreeNX-kNX] Timing Out
> 
> 
> 
> Andrew Villano <AVillano at incentient.com> wrote on 19/08/2009 16:39:35:
> 
> > Hello All, 
> > 
> > My freenx client is timing out. I am connecting with a publickey. 
> > There is a little delay connecting to my ssh server normally but it 
> > usually connects after a minute or so. 
> > 
> > This is my client log: 
> > 
> > NX> 203 NXSSH running with pid: 484 
> > 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: 75.127.217.69 on port: 12019 
> > NX> 202 Authenticating user: nx 
> > NX> 208 Using auth method: publickey 
> > NX> 280 Exiting on signal: 15 
> 
> 
> Is it actually connecting ?? 
> 
> Try 
> 
>         ssh -v  -l nx  -i /path/to/nx/client.id_dsa.key  -p 22 
75.127.217.69
> 
> from the client to tell you what your ssh is doing. 
> 
> You will need to be connecting to sshd (22) on the server and you 
> will need a copy of the client.id_dsa.key 
> 
> chris 
> 
> > 
> > 
> > Warmest Regards, 
> > 
> > Andrew Villano 
> > Systems Specialist 
> > Incentient LLC 
> >  ________________________________________________________________
> >      Were you helped on this list with your FreeNX problem?
> >     Then please write up the solution in the FreeNX Wiki/FAQ:
> > 
> > 
http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
> > 
> >          Don't forget to check the NX Knowledge Base:
> >                  http://www.nomachine.com/kb/ 
> > 
> > ________________________________________________________________
> >        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
> >       https://mail.kde.org/mailman/listinfo/freenx-knx
> > ________________________________________________________________
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
> 
> 
http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
> 
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/ 
> 
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20090819/2d7e522a/attachment.html>


More information about the FreeNX-kNX mailing list