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

it makes sense, my i7 is also connected to a wifi router, I will also give
it a shot!

2011/1/27 Radioactive Frog <pbhatkoti_at_gmail.com>

> Everyone - thanks for your inputs.
> I have found the solution.
> I ran my laptop on wired connection for a full day and it didn't drop.
> Connected to eth0.
> well connection drop is depend on your setting on router but telnet session
> was not terminating after it drop.
>
> I uninstalled the wifi module from laptop and used NDIS driver instead.
>
> NDIS driver rocks. acces to the lab thr Wireless is now working perfectly.
>
>
>
>
> On Wed, Jan 26, 2011 at 5:00 AM, Jeferson Guardia <jefersonf_at_gmail.com>wrote:
>
>> Frog,
>>
>> It also happened to me before, when I was doing labs on my i7 computer, I
>> used to log in remotely to my routers (loaded up in dynamips) at home and
>> used to work on them, but if I was idle for a while, it would freeze and no
>> matter what I did, I wouldnt have access again, only stop/start on dynagen
>> to the router that froze would solve the issue..
>>
>> nightmare!
>>
>> 2011/1/25 Radioactive Frog <pbhatkoti_at_gmail.com>
>>
>>> 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
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Thu Jan 27 2011 - 11:28:42 ART