[Dx4win] Telnet via Cable Modem Timeout

2002-07-20 Thread Dean Norris
At 07:58 7/19/2002, N2TK wrote:
Gary, I'm at an airport getting ready to board a plane. Won't be able to
check my setup for a week till I get back.
I'm using a DSL connection. I have not upgraded the software with the
router. When I looked at the router configuration from the http site, the
last two lines referred to keep alive. Also, I do have PPPOe checked as
instructed by my ISP, Verizon
Tony.


I have a Cisco 675 DSL box.  My DSL is QWORST.  I know they have upgraded 
the software/firmware for it but after looking at the instructions, I 
decided to wait until I had a month to spare.

My telephone line comes to the 675 and it, in turn goes to a Linksys 5-port 
hub.  The computers connect there.  I don't seem to have a problem staying 
connected but i have noticed a strange phenomena in my Win2K hardware setup.

I define the IP numbers for the computer boxes.  They are in the series 
10.0.0.10, etc.  But the win2k box shows, in addition to the NIC card, a 
WAN Miniport (IP) #2 in the hardware setup and it has a yellow exclamation 
mark.  Everything works ok but I have been told to let the Cisco play DHCP 
and assign IP numbers.  Also, how about using Netbui for the connection?

Any comments?  OR, since it works, should I let sleeping dogs lie?

unkadean


--




[Dx4win] Telnet via Cable Modem Timeout

2002-07-20 Thread Garry Shapiro
Since Tony, N2TK, is out of touch, this is to others following this thread.

I upgraded the firmware for my LinkSys BEFSR41 to the latest version,
1.42.7, and there is no reference to either connect on demand or keep
alive in this version. This was confirmed in several conversations with
LinkSys Support yesterday. Also, my ISP apparently does not support PPPoE in
any case, and enabling that option cripples my connection.

LinkSys suggested that the timeout might be due to something my ISP does,
but my ISP tech told me they do no such thing, so we have obviously reached
the I-don't-know-I-am-grabbing-at-straws point with LinkSys.

The newer firmware appears to have no effect on the timeout problem here.

That leaves the earlier suggestion to place this PC outside the
DMZ/firewall, which would expose it to the creatures of the jungle. There
are software firewalls available, but my pal W6WA, who is the IT guru at the
company for which I sometimes consult, strongly recommends the hardware
firewalls provided by the router.

I'm no computer weenie, so, at this point, I am stalemated.

Garry, NI6T

 -Original Message-
 From: N2TK [mailto:[EMAIL PROTECTED]
 Sent: Friday, July 19, 2002 14:58
 To: 'Garry Shapiro'; 'KC9JS, John'; dx4win@mailman.qth.net
 Subject: RE: [Dx4win] Telnet via Cable Modem Timeout


 Gary, I'm at an airport getting ready to board a plane. Won't be able to
 check my setup for a week till I get back.
 I'm using a DSL connection. I have not upgraded the software with the
 router. When I looked at the router configuration from the http site, the
 last two lines referred to keep alive. Also, I do have PPPOe checked as
 instructed by my ISP, Verizon
 Tony.

 -Original Message-
 From: Garry Shapiro [mailto:[EMAIL PROTECTED]
 Sent: Thursday, July 18, 2002 9:40 PM
 To: [EMAIL PROTECTED]; 'KC9JS, John'; dx4win@mailman.qth.net
 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

[Dx4win] Telnet via Cable Modem Timeout

2002-07-19 Thread Garry Shapiro
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] Telnet via Cable Modem Timeout

2002-07-19 Thread [EMAIL PROTECTED] (Kurt W. Zimmerman)
I was going to make this suggestion next.  This does work.  I set my email 
polling time to 3 min.  I can stay connected for hours/days.

73;
Kurt - W2MW

-Original Message-
From:   EdKathyStratton [SMTP:[EMAIL PROTECTED]
Sent:   Thursday, July 18, 2002 9:54 PM
To: Garry Shapiro; [EMAIL PROTECTED]; 'KC9JS, John'; dx4win@mailman.qth.net
Subject:Re: [Dx4win] Telnet via Cable Modem Timeout

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

[Dx4win] Telnet via Cable Modem Timeout

2002-07-19 Thread N2TK
Gary, I'm at an airport getting ready to board a plane. Won't be able to
check my setup for a week till I get back.
I'm using a DSL connection. I have not upgraded the software with the
router. When I looked at the router configuration from the http site, the
last two lines referred to keep alive. Also, I do have PPPOe checked as
instructed by my ISP, Verizon
Tony.

-Original Message-
From: Garry Shapiro [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 18, 2002 9:40 PM
To: [EMAIL PROTECTED]; 'KC9JS, John'; dx4win@mailman.qth.net
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

[Dx4win] Telnet via Cable Modem Timeout

2002-07-18 Thread Brian Boerner
Just an FYI, I'm running a Compaq CPW Wireless Router and it has this
problem. I'll troll the setup pages tonight to see if I can find a keep
alive value. I would also say the main difference between linksys and cisco
is one is a home networking product and the other is probably commercial.
You've got to skimp where you can to make up the margin. :)

-bmb


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Kurt W. Zimmerman
 Sent: Wednesday, July 17, 2002 10:45 PM
 To: '[EMAIL PROTECTED]'; dx4win@mailman.qth.net
 Cc: [EMAIL PROTECTED]
 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] Telnet via Cable Modem Timeout

2002-07-18 Thread Pete Smith
At 10:19 PM 7/17/02 -0500, KC9JS, John wrote:
So your problem
must be related to the Linksys router. Just saying it may be something you
should look it.


I'm not sure this is obviously the router.  Cable modem systems can be set 
up (provisioned is the weird word they use, I guess from telephone-speak) 
in a number of different ways.  At least in theory, the one I'm on grants a 
set-duration lease of an IP address.  There was briefly a time where it 
would drop every 2 hours regularly as clockwork, but that stopped fairly 
quickly and now I keep the same IP address.  I *think* the system is 
automatically renewing my lease every two hours...

As for the support, I couldn't agree more.  Once in a while you get someone 
who knows his or her stuff, but it's rare.  I've found one such guy now and 
learned a back way to get to him.  It makes things a lot better.

73, Pete N4ZR

Check out the World HF
Contest Station Database at
www.pvrc.org






[Dx4win] Telnet via Cable Modem Timeout

2002-07-18 Thread Ted Sarah - W8TTS
Hi,

I went through the same problem.  Took the Linksys Router out of
the picture and it cleared up.

Ted - W8TTS



[Dx4win] Telnet via Cable Modem Timeout

2002-07-18 Thread [EMAIL PROTECTED] (Kurt W. Zimmerman)
If you read the RFP on DHCP, you will find that as long as the IP is active 
that it will get renewed during its half-life of the lease.  So if you have 
an expiration of 2 hours, your IP will be renewed every hour.

-Original Message-
From:   Pete Smith [SMTP:[EMAIL PROTECTED]
Sent:   Thursday, July 18, 2002 3:48 AM
To: dx4win@mailman.qth.net
Cc: [EMAIL PROTECTED]
Subject:Re: [Dx4win] Telnet via Cable Modem Timeout

At 10:19 PM 7/17/02 -0500, KC9JS, John wrote:
So your problem
must be related to the Linksys router. Just saying it may be something you
should look it.


I'm not sure this is obviously the router.  Cable modem systems can be set
up (provisioned is the weird word they use, I guess from telephone-speak) 
in a number of different ways.  At least in theory, the one I'm on grants a 
set-duration lease of an IP address.  There was briefly a time where it
would drop every 2 hours regularly as clockwork, but that stopped fairly
quickly and now I keep the same IP address.  I *think* the system is
automatically renewing my lease every two hours...

As for the support, I couldn't agree more.  Once in a while you get someone 
who knows his or her stuff, but it's rare.  I've found one such guy now and 
learned a back way to get to him.  It makes things a lot better.

73, Pete N4ZR

Check out the World HF
Contest Station Database at
www.pvrc.org




___
Dx4win mailing list
Dx4win@mailman.qth.net
http://mailman.qth.net/mailman/listinfo/dx4win



[Dx4win] Telnet via Cable Modem Timeout

2002-07-18 Thread l dietrich
Isn't there a way to lengthen the lease interval?

Lou N2TU
- Original Message -
From: Kurt W. Zimmerman [EMAIL PROTECTED]
To: 'Pete Smith' [EMAIL PROTECTED]; dx4win@mailman.qth.net
Cc: [EMAIL PROTECTED]
Sent: Thursday, July 18, 2002 8:17 AM
Subject: RE: [Dx4win] Telnet via Cable Modem Timeout


 If you read the RFP on DHCP, you will find that as long as the IP is
active
 that it will get renewed during its half-life of the lease.  So if you
have
 an expiration of 2 hours, your IP will be renewed every hour.

 -Original Message-
 From: Pete Smith [SMTP:[EMAIL PROTECTED]
 Sent: Thursday, July 18, 2002 3:48 AM
 To: dx4win@mailman.qth.net
 Cc: [EMAIL PROTECTED]
 Subject: Re: [Dx4win] Telnet via Cable Modem Timeout

 At 10:19 PM 7/17/02 -0500, KC9JS, John wrote:
 So your problem
 must be related to the Linksys router. Just saying it may be something
you
 should look it.


 I'm not sure this is obviously the router.  Cable modem systems can be set
 up (provisioned is the weird word they use, I guess from
telephone-speak)
 in a number of different ways.  At least in theory, the one I'm on grants
a
 set-duration lease of an IP address.  There was briefly a time where it
 would drop every 2 hours regularly as clockwork, but that stopped fairly
 quickly and now I keep the same IP address.  I *think* the system is
 automatically renewing my lease every two hours...

 As for the support, I couldn't agree more.  Once in a while you get
someone
 who knows his or her stuff, but it's rare.  I've found one such guy now
and
 learned a back way to get to him.  It makes things a lot better.

 73, Pete N4ZR

 Check out the World HF
 Contest Station Database at
 www.pvrc.org




 ___
 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] Telnet via Cable Modem Timeout

2002-07-18 Thread N2TK
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] Telnet via Cable Modem Timeout

2002-07-18 Thread EdKathyStratton
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

Fw: [Dx4win] Telnet via Cable Modem Timeout

2002-07-18 Thread Dan Szymanski
Maybe I am out of line here or something.

However, has anyone who is experiencing dropped sessions ever talk with the
SYSOP of the node they telnet into regarding this issue?  I have yet to see
any reference of any correspondence with the Clusters SYSOP to date.
Sometimes the Cluster SYSOP have a better means to give a reason for the
dropped session. I believe all telnet sessions are logged at the Cluster.  I
am not trying to disprove some of the thoughts being talked about.  I am of
the opinion that many nodes we telnet into depend on a cable modem for
broadband connection as well. However while I am at work, I normally connect
to K4JA via a telnet session.  No,  I am not using a cable modem but do have
a real fiber based DS-1 line with router and all the IT supporting hardware
one would expect a business and its IT department to have. OK, I admit to
the fact somewhere in the path QWEST is involved with the DS-1. But I will
leave that part out of the equation for now.

While I don't really need to or use DX4WIN at work, I do use WINPACK 6.80 as
my telnet terminal. I admit to having dropped sessions experienced as well.
I don't have time to look at this while at work, I just know it does happen
to me.  I also know at times my connection to the Cluster host even gets
refused for short periods of time.  I can't believe I have bad hardware in
ever instance, maybe outdated firmware.

I have talked with the SYSOP for K4JA.  A little insight.  I found out there
is a AR Cluster SUPER SYSOP who single handed manages just under two dozen
AR Cluster nodes across the country.  Boy talk about network management at
its finest. Surprise, I have discovered via multiple emails exchanged even
cluster nodes running software such as AR Cluster are not totally bullet
proof.  Even with some of the more recent software updates made to it.
Those that are running the CLX package (that would be Linux based) also have
there weakness. So I guess we can take MicroSlush out of the picture for now
at least.

So maybe we need to get some input from those who know, run and manage the
clusters for us.  I don't see why we need to beat ourselves up all the time.
Oh, I do see some relative merit of advantage for a CISCO based router @ ~
$1,500.00 or so verses say a Netopia R7100 router or LinkSys gateway router
posted on eBay for ~ $ 70.00. I don't care what version of firmware you have
installed.

In my own world, I have visions of running a AR Cluster node offering
telnet, replacing the DOS based version currently on line at home.  Some of
the networking pieces are starting to fall into place for me.  Thanks in
advance.

Regards,

K3SKE
Dan Szymanski
SYSOP K3SKE for the PVDXSN
Frederick, MD
PVRC/NCDXA

[EMAIL PROTECTED]

- Original Message -
From: John Desmond [EMAIL PROTECTED]
To: dx4win@mailman.qth.net
Cc: [EMAIL PROTECTED]
Sent: Thursday, July 18, 2002 02:35
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] Telnet via Cable Modem Timeout

2002-07-17 Thread [EMAIL PROTECTED] (Kurt W. Zimmerman)
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] Telnet via Cable Modem Timeout

2002-07-17 Thread Dean Norris
At 20:19 7/17/2002, KC9JS, John wrote:
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


FYI, I am using a Cisco 675 DSL to a Linksys 4-port hub to my 2 home 
computers and rarely lose a telnet link to K7AR.

unkadean


--




[Dx4win] Telnet via Cable Modem Timeout

2002-07-07 Thread wa9als
 Yes, some of the telnet software that is used will also time out.

I use DX Telnet with WriteLog and DX4WIN.  I don't seem to need it for the
K1TTT cluster, but DX Telnet has a Keep Alive function that might help
some.

See http://www.qsl.net/wa9als/dxtelnet.htm for some details about using DX
Telnet with DX4WIN and WriteLog.  73






[Dx4win] Telnet via Cable Modem Timeout

2002-07-06 Thread Dan Szymanski
Now myself being one that has been bound up to a dial up ISP for years and a
lot longer it looks like with no hope of anything like broadband service
either from Verizon or Adelphia (the now local Cable Idiots), if losing DX
packet spots was the only bad feature I could complain about, I wouldn't say
a darn word!

Regards,

Dan
K3SKE


- Original Message -
From: Bob, N5RP [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; dx4win@mailman.qth.net
Sent: Friday, July 05, 2002 16:10
Subject: Re: [Dx4win] Telnet via Cable Modem Timeout


 At 11:03 7/5/2002 -0500, 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?
 =
 Use some other program that has an automatic scripting and log back in
 feature to get the packet spots.

 The data from that program can then be fed into a COM port on your
computer
 that DX4WIN recognizes as it's data feed source.
 Bob Perring
 ...
 Amateur Radio Station  N5RP
 mailto:[EMAIL PROTECTED]
 N5RP Station Page: http://web2.airmail.net/perring/station.html

 ___
 Dx4win mailing list
 Dx4win@mailman.qth.net
 http://mailman.qth.net/mailman/listinfo/dx4win



[Dx4win] Telnet via Cable Modem Timeout

2002-07-06 Thread Dave

 From time to time I experience the same thing here... The suspicion I have 
is that it may be RF related. From time to  I get some RF related 
activity (monitor flicker) with the beam pointed back at the shack, it 
also seems to be worse on some frequencies than others. As a result I'm 
never aware exactly when the disconnect occurs so it is hard to tie the 
transmission event back to the loss of the Internet connection.


Dave
NR1DX
[EMAIL PROTECTED]

A man who picks a cat up by the tail learns a lesson he can learn no other 
way  Mark Twain



[Dx4win] Telnet via Cable Modem Timeout

2002-07-06 Thread [EMAIL PROTECTED] (Larry Alkoff)
On Sat, 06 Jul 2002 12:22:03 +, Dave wrote:



 From time to time I experience the same thing here... The suspicion I have 
is that it may be RF related. From time to  I get some RF related 
activity (monitor flicker) with the beam pointed back at the shack, it 
also seems to be worse on some frequencies than others. As a result I'm 
never aware exactly when the disconnect occurs so it is hard to tie the 
transmission event back to the loss of the Internet connection.


Dave
NR1DX
[EMAIL PROTECTED]


FWIW I have the same timeout problem as the others and it is definitly _not_ rf
related because it only happens at a computer in my house which is 200 yards 
from
the shack.  The shack is not operational at that time, therefore no rf.

The shack uses a two meter line which is rock solid.

This would dismiss rf as the culprit for most timeout problems.

Larry



Larry Alkoff N2LA - Austin TX




[Dx4win] Telnet via Cable Modem Timeout

2002-07-06 Thread K2DBK - David
I have the same problem, and I'm sure it's not RF-related, since  sometimes 
when I've gotten disconnected I've been out of the shack (and not 
transmitting!) for some time.

There are a couple of things to consider here: First, the Internet is not 
guaranteed to be 100% reliable to all locations (or in fact, generally 
speaking, to any locations) for the kinds of things we're talking about. 
There is a lot of infrastructure between your computer and the telnet 
cluster itself, and depending on a lot of things (more appropriate to an 
Internet Infrastructure reflector than here, so I'll skip that stuff), if 
any one of those little pieces shuts down you may loose your connection.

The second thing is that it's possible that some clusters require some 
activity on the end-users part to keep the connection up.  This is not just 
a response to a low-level connectivity check, but actual user input. The 
reason is that if the cluster has limited resources (memory, CPU, etc.) 
they might not want to keep lots of inactive users connected.

I don't run a telnet cluster, but I'd be curious to hear from anyone who 
does as to whether they've got an inactivity timer available on the telnet 
connection to timeout inactive users.


FWIW I have the same timeout problem as the others and it is definitly 
_not_ rf
related because it only happens at a computer in my house which is 200 
yards from
the shack.  The shack is not operational at that time, therefore no rf.

The shack uses a two meter line which is rock solid.

This would dismiss rf as the culprit for most timeout problems.


73,
David - K2DBK



[Dx4win] Telnet via Cable Modem Timeout

2002-07-06 Thread Don Hinte
Hi All,

First Iam the SYSOP of a cluster here is San Antonio, TX. All are welcom to
use this cluster the tel-net tag is listed below.

Yes, some clusters us a timer.

Yes, some of the telnet software that is used will also time out.

Here I use Hi speed DSL, and run 4 servers, the only time I lose a
connection is in a bad storm, when the isp has a major maintance window. I
also connect my node to a node in Austin TX, we will have up times of over
45 days.

Also the SYSOP's may need to take a node down for maintance of files.

Try my node, there are no timers, if you are still going down, you may want
to check with your ISP to find out if he is running any timmers, that make
you reconnect.

73's All

Don Hinte, KA5EYH
Phone 210.646.9504
E-mail [EMAIL PROTECTED]
Web Page http://ka5eyh.drhnet.com
DXC Node dxc-ka5eyh.drhnet.com

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of K2DBK - David
Sent: Saturday, July 06, 2002 10:03 AM
To: dx4win@mailman.qth.net
Subject: Re: [Dx4win] Telnet via Cable Modem Timeout


I have the same problem, and I'm sure it's not RF-related, since  sometimes
when I've gotten disconnected I've been out of the shack (and not
transmitting!) for some time.

There are a couple of things to consider here: First, the Internet is not
guaranteed to be 100% reliable to all locations (or in fact, generally
speaking, to any locations) for the kinds of things we're talking about.
There is a lot of infrastructure between your computer and the telnet
cluster itself, and depending on a lot of things (more appropriate to an
Internet Infrastructure reflector than here, so I'll skip that stuff), if
any one of those little pieces shuts down you may loose your connection.

The second thing is that it's possible that some clusters require some
activity on the end-users part to keep the connection up.  This is not just
a response to a low-level connectivity check, but actual user input. The
reason is that if the cluster has limited resources (memory, CPU, etc.)
they might not want to keep lots of inactive users connected.

I don't run a telnet cluster, but I'd be curious to hear from anyone who
does as to whether they've got an inactivity timer available on the telnet
connection to timeout inactive users.


FWIW I have the same timeout problem as the others and it is definitly
_not_ rf
related because it only happens at a computer in my house which is 200
yards from
the shack.  The shack is not operational at that time, therefore no rf.

The shack uses a two meter line which is rock solid.

This would dismiss rf as the culprit for most timeout problems.


73,
David - K2DBK

___
Dx4win mailing list
Dx4win@mailman.qth.net
http://mailman.qth.net/mailman/listinfo/dx4win




[Dx4win] Telnet via Cable Modem Timeout

2002-07-05 Thread Alan Clark
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] Telnet via Cable Modem Timeout

2002-07-05 Thread Mike Rhodes
Alan,
  I noticed a similar thing when I switched to a cable modem but figured it
was an issue with my provider. Then I caught a deal on a Linksys router so I
could share my fast connection with other PCs in my home and the problem
went away. I have not done any special setup on the router - still need to
read thru the documentation. Running ZoneAlarm to keep things secure though.
Anyhow, nothing has changed beyond the addition of the router and I
certainly don't have an explanation for the change in behavior. Guess it is
just food for thought.

Mike / W8DN

- Original Message -
From: Alan Clark [EMAIL PROTECTED]
To: dx4win@mailman.qth.net
Sent: Friday, July 05, 2002 12:03 PM
Subject: [Dx4win] Telnet via Cable Modem Timeout


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] Telnet via Cable Modem Timeout

2002-07-05 Thread [EMAIL PROTECTED] (Larry Alkoff)
I also have had the same problem for quite a while and it's quite annoying.

My setup has a cablemodem and router.

I believe that the telnet source asks for periodic acks and times
out when the ack doesn't come.

I would like to see dx4win changed to re-connect automatically
when such a time-out occurs.

Larry Alkoff N2LA




On Fri, 5 Jul 2002 11:03:57 -0500, 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




Larry Alkoff N2LA - Austin TX




[Dx4win] Telnet via Cable Modem Timeout

2002-07-05 Thread Larry Gauthier
Alan,

Are you using a router? I use a LinkSys multi-port router to connect
multiple PCs in my house to the cable modem. I found that the DX spots in
DX4WIN time-out unless I use the LinkSys DMZ Host feature to place the Ham
PC outside the perimeter of the router's firewall protection.

-larry
K8UT

- Original Message -
From: Alan Clark [EMAIL PROTECTED]
To: dx4win@mailman.qth.net
Sent: Friday, July 05, 2002 12:03 PM
Subject: [Dx4win] Telnet via Cable Modem Timeout


 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] Telnet via Cable Modem Timeout

2002-07-05 Thread Jim Reisert AD1C
At 11:03 AM 7/5/2002 -0500, 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?

I can't say what your problem is, but I have two computers on my network, 
one wired, one wireless, through (behind) the router to the cable modem and 
my DX4WIN connections (to KE9KD-2 and N2TX) stay connected for days on end.

73 - Jim AD1C


-- 
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, [EMAIL PROTECTED], http://www.ad1c.com