[FreeNX-kNX] Timing Out

[Andrew Villano]

I've deleted cache through the program. I don't see a directory though.

How do I increase the timeout?

Warmest Regards,

 

Andrew Villano

Systems Specialist

Incentient LLC

-----Original Message-----
From: Spiro Stathakis [mailto:spiro.stathakis at gmail.com] 
Sent: Thursday, August 20, 2009 9:37 AM
To: User Support for FreeNX Server and kNX Client
Subject: Re: [FreeNX-kNX] Timing Out

Can you delete / move  the NX cache folder on the client?


2009/8/20 Andrew Villano <AVillano at incentient.com>:
> My client connects to FreeNX servers on a different subnet (of which are on
> the same subnet).
>
>
>
> I can telnet to the server in question and connect instantaneously. They key
> is the same.
>
>
>
> The only delay in logging on in SSH is after entering credentials, the delay
> lasts about 45 secs.
>
>
>
> I was using the same user accounts on all attempts.
>
>
>
> Warmest Regards,
>
>
>
> Andrew Villano
>
> Systems Specialist
>
> Incentient LLC
>
> ________________________________
>
> From: chris at ccburton.com [mailto:chris at ccburton.com]
> Sent: Thursday, August 20, 2009 3:31 AM
> 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 20:26:33:
>
>> Linux client connects within a few seconds.
>>
>> Same network route.
>>
>> I can connect with the same windows client to other linux machines
>> on the same subnet (with identical configurations). The linux CLIENT
>> was on the SAME subnet though.
>>
>> 1)       Copied the key several times, its identical
>> 2)       I don't know what routing issue there could be, the ssh
>> port is forwarded to the machine
>> 3)       I'm using putty to connect to the machine and I'm currently
>> connected fine.
>>
>> Very strange....
>
>
> OK
>
> Your client connects to FreeNX servers on the same subnet, but not to the
> server in question on a different subnet, though it has done previously, but
> taking a minute to log in.
>
> You can however telnet to the server on a different subnet using putty. Is
> the connection instantaneous ??
>
> A linux client on the same subnet as the server in question can connect
> instantly using FreeNX.
>
> The key on the windows client is the same as the key on the linux client.
>
>
>
>
> If you telnet to the sshd port ( 22 default ) on the server from the windows
> machine you should get an ssh prompt instantly
>
> SSH-2.0-OpenSSH_x.y  or whatever. If it takes a minute or so then that would
> be something to look at  . . .
>
>
>
> When tou were connecting using the linux client from the same subnet as the
> server, were you using the same user account or does the problem move
> following user accounts ??
>
>
>>
>> Warmest Regards,
>>
>> Andrew Villano
>> Systems Specialist
>> Incentient LLC
>>
>> From: chris at ccburton.com [mailto:chris at ccburton.com]
>> Sent: Wednesday, August 19, 2009 3:15 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 19:37:03:
>>
>> > I can get a full working session from a linux client.
>> >
>>
>> Right, server and keys working then. How long does the Linux client
>> take to connect.
>>
>> Is this over the same network route . . .
>>
>>
>> > I can connect with the windows client to clients on the same IP.
>>
>> How do you mean?? Client software to client software ??
>>
>> >
>> > I got the hello nxserver prompt from ssh.
>>
>> We know it works from Linux.
>>
>>
>> In order I would look at
>>
>> key mismatch on the windows machine
>>
>> routing issue windows client to server - timeouts or filtering on
>> the server or packets going two ways
>>
>> windows software issue -  try a windows ssh client   eg  http:
>> //sshwindows.sourceforge.net/  or just re-install the windows client
>>
>>
>>
>>
>>
>> >
>> > 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
> ________________________________________________________________
>
________________________________________________________________
     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
________________________________________________________________