Re: (ASCEND) 56K modem disconnects

To: ascend-users@bungi.com
Subject: Re: (ASCEND) 56K modem disconnects
From: Mitchell.Arnone@occ.treas.gov
Date: Thu, 9 Apr 98 9:24:21 EDT
Mmdf-Warning: Parse error in original version of preceding line at mailhost.occ.treas.gov
Mmdf-Warning: Parse error in original version of preceding line at mailhost.occ.treas.gov
Sender: owner-ascend-users@max.bungi.com

Are your users really getting busy signals or just reporting that as their interpretation of what is going on. 

I had users (actually "technically proficient" LAN Administrators (yea.. right)) call me and report they are getting busy signals.  Well that was simply impossible for my setup because I have about a 200% overkill currently.  Finally I was able to witness what they called a busy signal.  When the client would connect, the modem on my TNT would definitely answer but the negotation was long and the client finally gave up the ghost and reported to the user that the calling modem was not answering.

We did a few things to correct this.  First, upgrading the TNT to 2.0 cleaned up most of the problems.  Next we insured that the modem drivers were the latest and not corrupted...  In some cases we removed and re-installed the modem drivers.  Thirdly, we disabled software compression on Win 95 clientsl.  Software compression seems to be a big deal.

One other suggestion, if your clients are running Win 95... go to the dialup connection and configure it to write to a log file.  After the user dials-in and disconnectes (hopefully gets disconnected), have him or her forward to you a copy of ppp.log file in the C:\windows directory.  Evaluate the log file... you should be able to see all the activity going on between the client and the dialup host.

Mitch
---------- Original Text ----------

From: William T Wilson <fluffy@dunadan.com>, on 4/8/98 11:16 PM:

On Wed, 8 Apr 1998, FastWave - Ascend MAX wrote:

> > Has anyone had any complaints with the 56K Flex modems disconnecting at
> > random?  I have three Max 4048 boxes with 2 - 24 count modem cards in each.

I have had very few random disconnects using K56 modems, but I do have
trouble with the Max sometimes simply failing to answer calls.  I think it
MIGHT be related to the fact that some calls last for an exceptionally
long time (several days).  It happens about once a week or once every
other week - anyone trying to dial in simply gets a busy signal, after a
long pause.  Other than the occasional extended-length call, this
particular Max is under VERY light load - one PRI with typically about
half a dozen calls on it at most, all analog, using RIPv1.  It has
software revision 5.0Ap36.  Existing calls are not dropped.  The only fix
that I have been able to find is to reset the unit.  Even if all calls are
dropped, the Max does not begin answering calls again.

Anyone else seen this?

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

Prev by Date: (ASCEND) ISDN caller c=65 p=45 ???
Next by Date: Re: (ASCEND) V.90 Status?
Prev by thread: Re: (ASCEND) 56K modem disconnects
Next by thread: (ASCEND) PPTP on MAX TNT
Index(es):
- Main
- Thread