Re: (ASCEND) Ticket #802135 - Disconnect Problems on 4048 with 7.0.1

["Steven T. Pierce" <stp@Dynasty.Net>]

Troy,

Again, as I said,  I have my Ethernet -> Answer  section set to 3600, but have
cause code 100's that happen at 15 minutes (900 seconds) on the dot with no
activity... (and yes I rebooted the server after I set the preferences to make
sure it was loaded in the RAM / ROM on bootup)

Session options...
  >RIP=Off
   Data Filter=0
   Call Filter=0
   Filter Persistence=No
   Idle=3600
   TS Idle Mode=Input/Output
   TS Idle=3600
   Max Call Duration=0
   Preempt=60

So ... if I want absolutely NO IDLE TIMEOUT do I set it to ZER0,  TS Idle mode
to NONE ?

Steve
stp@dynasty.net

Troy Settle wrote:

> On Thu, 7 Jan 1999, J-Mag Guthrie wrote:
>
> > On Thu, 7 Jan 1999, Steven T. Pierce wrote:
> >
> > > The true problem seems to be a "hidden" disconnect setting of 15 minutes
> > > (I have it set to 3600 (60 minutes) instead of 900 (which would be 15))
> > > ... others complain of a 2 minute disconnect.
> > >
> > > Do the 100 cause codes indicate that the Max is timing out the
> > > connection ?  Our radius profiles are also set to 3600 (60 minutes).
>
> again, it's in the Ethernet -> Answer section.  tell it to use answer as
> default, and set the session options to your defaults.  Override this
> values with specific radius entries.
>
> My radius users file looks like this:
>
> DEFAULT Password="UNIX"
>         Framed-Protocol=PPP ,
>         Login-Service=Rlogin ,
>         Login-Host=aaa.bbb.ccc.xxx ,
>         Ascend-Maximum-Channels=1 ,
>         Ascend-Assign-IP-Pool=1
>
> All our time limits are in the Max configurations.
>
> > The other place that a time-out might be set is in the client machine.
> > Windows idea of "idle" seems to have no bearing on reality (I was reading
> > e-mail in a telnet session (using CRT) when it popped up to tell me that
> > it would disconnect unless I intervened).
>
> Windows is indeed confused, but a disconnect of this nature would result
> in a c=45 or c=185, as the 'client' would be terminating the session.
>
> > However, I've seen the case where someone gets a c=100 disconnect after a
> > few seconds and in every case, having them cycle the power on the modem
> > (by shutting down Windows, powering off, counting to ten and turning the
> > power back on -- this seems to only happen with internal modems) fixed the
> > problem.  We're running 6.1.7 on our maxen.
>
> I believe someone already mentioned this, but when you get a disconnect
> cause of 100, it's got nothing to do with the customer's computer or
> equipment.  It's 100% on the ISP side.
>
> The default value of the idle timeout is 120 seconds.  This is an insane
> value for a dialup customer, and it can be over-ridden in the
> Ethernet->Answer menu on the Max.
>
> --
>   Troy Settle <st@i-Plus.net>
>   Network Administrator, iPlus Internet Services
>   http://www.i-Plus.net

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>