The best way to keep you network connection up and if you isp provides your email, is to set the auto check for new email to the lowest value. I believe MS outlook and express can be set to one minute intervals. This at least keep the circuit up, and let's the ISPs know that your connection is very active. They probably don't monitor telent activity, but I bet there is sometype of keep alive the connection if the email is check in these minimal check periods.
Anyway it worth a try. w1zz ed ----- Original Message ----- From: "Garry Shapiro" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "'KC9JS, John'" <[EMAIL PROTECTED]>; <dx4win@mailman.qth.net> Sent: Thursday, July 18, 2002 9:39 PM Subject: RE: [Dx4win] Telnet via Cable Modem Timeout > Tony: > > I have the same LinkSys router and connect via ADSL. I experience unwanted > and annoying Telnet timeouts, so I have observed this thread with keen > interest. > > I use the most basic settings and am using an older firmware version--1.34. > A year or so ago, I upgraded for no particular reason, and triggered serious > problems that were only resolved by going back to 1.34, which was not at all > trivial to do. As pointed out, LinkSys tech support was pretty marginal. > Having been so burned, I have made no changes since, following the hoary > principle of "if it ain't broke, don't fix it." > > I find "connect on demand" associated with PPPoE, which is currently > disabled. The HELP file says "You have to check with your ISP to make sure > whether the PPPoE should be enabled or not." Apparently, I do not need it > for basic functionality with this ISP. > > I cannot find "keep alive" anywhere on this version. What is its use > context? > > What F/W version are you using? Is yours a cable or DSL connection? > > Garry, NI6T > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of N2TK > > Sent: Thursday, July 18, 2002 21:30 > > To: 'KC9JS, John'; [EMAIL PROTECTED]; [EMAIL PROTECTED]; > > dx4win@mailman.qth.net > > Cc: [EMAIL PROTECTED] > > Subject: RE: [Dx4win] Telnet via Cable Modem Timeout > > > > > > I'm using a Linksys Router - BEFSS41. I stay continually connected to DX > > Telnet. > > Have you done to http://192.168.1.1? Make sure "Connect on demand" is not > > checked. Also make sure "Keep Alive" is checked. > > Tony > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Behalf Of KC9JS, John > > Sent: Wednesday, July 17, 2002 23:19 > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; dx4win@mailman.qth.net > > Cc: [EMAIL PROTECTED] > > Subject: Re: [Dx4win] Telnet via Cable Modem Timeout > > > > I'm using a Telnet connection via a Cable Modem and have no > > problems at all > > with dropouts or timeouts. I'm not using a router or anything like that, > > just a Motorola Cable Modem connected to a Gateway 700S computer using > > Windows XP and DX4win 5.03. So far it's all working fine. So your problem > > must be related to the Linksys router. Just saying it may be something you > > should look it. > > 73 de John/KC9JS > > Twin Lakes, WI > > ************************************* > > ----- Original Message ----- > > From: "Kurt W. Zimmerman" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]>; <dx4win@mailman.qth.net> > > Cc: <[EMAIL PROTECTED]> > > Sent: Wednesday, July 17, 2002 9:45 PM > > Subject: RE: [Dx4win] Telnet via Cable Modem Timeout > > > > > > > Not really knowing much about the Linksys router, I would seem to think > > > that you are experiencing a time out instead of loosing track of the > > telnet > > > session. You should have some user-definable parameters in any > > router to > > > allow you to change and/or configure timeouts. > > > > > > I would not give up all hope on the Linksys router until it has > > been fully > > > explored. Mind you, most of the folks on tech-support help desks don't > > > always have the answers. I've found that out from personal experience. > > > > > > > > > 73; > > > Kurt - W2MW > > > > > > -----Original Message----- > > > From: John Desmond [SMTP:[EMAIL PROTECTED] > > > Sent: Wednesday, July 17, 2002 10:35 PM > > > To: dx4win@mailman.qth.net > > > Cc: [EMAIL PROTECTED] > > > Subject: Re: [Dx4win] Telnet via Cable Modem Timeout > > > > > > Hi Alan, > > > > > > I just read your note today. I have had this same problem ever since > > going > > > to a > > > cable modem over a year ago. My telnet sessions would drop > > anywhere from > > 2 > > > hours to 10 hours after they were set-up. The sessions were not just to > > > DXClusters that had the problem. I use telnet to other systems such as > > > routers > > > and Linux machines. They all had the same problem. > > > > > > I have a Linksys router with the 4 port switch. In the past I > > have tried > > > calling Linksys tech support and also have loaded every new version of > > code > > > that > > > was released, hoping that they might just fix it, even if it were > > > inadvertent. > > > Their support is just plain awful if not just plain pathetic. > > > > > > What proved to me that it was the Linksys was when I replaced it with a > > > Cisco > > > 806. The dropped sessions stopped. I have had sessions up for a week > > plus > > > with > > > no drops. It is pretty clear to me that the Linksys is loosing track of > > > the > > > telnet session somehow. > > > > > > The answer may not be that you need a Cisco router. I have never tried > > any > > > of > > > the other brands out there like D-Link, etc. They may not have this > > > problem. > > > > > > > > > 73, John K0TG > > > > > > > > > Alan Clark wrote: > > > > > > > I have recently converted from a dial-up to an ISP to get my > > DX Spots to > > > a > > > > Cable Modem. Since converting to the cable modem I notice > > that it times > > > out > > > > and goes off line without any notification. All I notice is that I am > > > not > > > > getting spots any more. Works fine when I dial up the ISP, > > but with the > > > > cable modem it times out. Any insight to a solution? > > > > > > > > Alan, N5PA > > > > > > > > _______________________________________________ > > > > Dx4win mailing list > > > > Dx4win@mailman.qth.net > > > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > > > _______________________________________________ > > > Dx4win mailing list > > > Dx4win@mailman.qth.net > > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > > > _______________________________________________ > > > Dx4win mailing list > > > Dx4win@mailman.qth.net > > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > > > > > > _______________________________________________ > > Dx4win mailing list > > Dx4win@mailman.qth.net > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > _______________________________________________ > > Dx4win mailing list > > Dx4win@mailman.qth.net > > http://mailman.qth.net/mailman/listinfo/dx4win > > > > _______________________________________________ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win
