Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) 6.1.3 and connection profile errors
Don't feel too bad. I still haven't had a really stable release of code
for the TNT to deal with ISDN. At least the 4000 code can handle a number
of ISDN sessions without dying every 15 minutes. Now I hear that there is
a new HDLC card on the way, but nobody can tell us when, or if we get a
free replacement for all the crappy HDLC cards we already bought (falsely
advertised to handle 192 ISDN sessions I might add).
::SIGH::
--
William Charnock
System Administrator
FastLane Internet Services
(817)-429-5263
On Mon, 27 Jul 1998, Alex P wrote:
> The problem is the 6.1 code! There has been no response from Ascend as to
> why. Only the usual LQM on, LQM off type of stuff.
>
> I'm trying not to sound bitter here, but I'm getting the feeling that
> Ascend cares about the MAX4000 platform as much as it does about the P50.
> If you buy a TNT, you get working V.90 code. I'm also willing to bet
> almost anything that the MAX6000's code works fine too. If you're sitting
> around with 50 4000's in the field (as I am) you're basically screwed
> until they accidentally fix it in the next release. (If we can get them
> to admit it exists).
>
> Kevin, you've been great with everything else, can you get someone over
> there to at least respond to all of the complaints of analog users getting
> disconnected as soon as they connect (some lasting up to 5 mins).
>
> It happens with the ~20 different modems I've tried (mostly V.34's since
> that what most of my customers are still using), and there is still no
> discernable pattern to the problem. Even if no one has a clue as to why
> it's happening, a response from Ascend that they're even looking into it
> would be nice.
>
> Alex P
>
>
>
> On Mon, 27 Jul 1998, Network Support wrote:
>
> > I recently upgraded our 3 MAX 4048's to ftik.m40 6.1.3. We are using
> > stacking and have LQM turned off. After the upgrade, I restarted radius
> > for safe measure and started monitoring and checking the connections.
> > While using a Win95 PC, it will sometimes connect to any of the boxes and
> > then disconnect' saying that it cannot establish a compatible set of
> > protocols to make the connnection. I will try about 4 more times to
> > connect, and then succeed. This problem is in some type of negotiation
> > with the MAXES. I am used to seing this from our users when they forget to
> > install the tcp/ip protocol in the WIN95 network.
> >
> > It's baffling!!! Have any others experienced this? If so, please let
> > there be a cure.
> >
> > -Will-
> > ++ 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>
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: