Re: OT: Telenet to terminal server dropping -ubuntu 10 driving

Dale et. al,
thanks for your comments :)

no-OP feature is for maintaining connection - fixes the fear of timeout.
my case is different... lets say mine times out in 20 seconds and I am
trying to initiate a new connection and it won't do that from my laptop. on
the other hand if i try telnetting into the same TS from other box on the
same subnet i can do that.

I have observed connecting via LAN / wired it's working perfect :)

it looks like it's the wireless module/driver which is the issue.

On Tue, Jan 25, 2011 at 7:54 AM, Dale Shaw <dale.shaw_at_gmail.com> wrote:

> Hi,
>
> > On Mon, Jan 24, 2011 at 6:49 AM, Narbik Kocharians <narbikk_at_gmail.com
> >wrote:
> >
> >> It used to happen to me as well, but it was all fixed when i configured
> the
> >> No-OP keeps in SecureCRT. Try it if it works GR8, if it does not, then
> move
> >> on to the next issue.
>
> On Tue, Jan 25, 2011 at 12:16 AM, Radioactive Frog <pbhatkoti_at_gmail.com>
> wrote:
> > No it locks up even I am working. HTTP connects ok to the same device but
> > not TELNET. Telnet locks up to all devices from my PC.
> >
> > Sorry I don't have that luxury yet to use secureCRT but gnome-terminal.
>
> SecureCRT's No-Op feature is just an application-specific keep-alive
> (i.e. if the session type is SSH, it uses an SSH keep-alive).
>
> It does sound like one of the endpoints or something in between is
> getting involved in the TCP session state.
>
> What does..
>
> sysctl -a | grep net.ipv4.tcp_keepalive
>
> ..say?
>
> Are you making the tcp/80 connection (that works) with telnet or some
> other client?
>
> No session timers on the terminal server side?
>
> Cheers,
> Dale

Blogs and organic groups at http://www.ccie.net
Received on Wed Jan 26 2011 - 00:47:35 ART