Re: (ASCEND) Busy Signals (max 4048)

To: Troy Wollenslegel <twollens@bordersgroupinc.com>
Subject: Re: (ASCEND) Busy Signals (max 4048)
From: Phillip Vandry <vandry@mlink.net>
Date: Tue, 15 Sep 1998 08:44:49 -0400 (EDT)
cc: ascend-users@bungi.com
In-reply-to: Your message of "Mon, 14 Sep 1998 16:35:25 EDT." <35FD45CD.D4340439@bordersgroupinc.com>
Sender: owner-ascend-users@max.bungi.com

> We get busy signals on our Max 4048 (T1) when people call in (at least
> win95
> reports it as a busy signal) 

(Yeah, a lot of good that "report" is)

You'd really need to know if it is indeed a busy, of a fastbusy, or
something else (by listening to it) to diagnose it.

> We also have a problem where the user (win95) gets a "security error"
> and told they entered the wrong password. This happens between 12% & 22%
> of the connects. I don't believe our users (all corporate) have that fat
> of fingers that they mis-type their passwords that often. We are using
> Steel Belted Radius (Novell) and have the radius timeout set to 30
> seconds.

Are you capturing the syslog output from the Max(es)? See if it
contains any errors, RADIS timeouts, or otherwise.

-Phil
++ 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:

(ASCEND) Busy Signals (max 4048)

From: Troy Wollenslegel <twollens@bordersgroupinc.com>

Prev by Date: Re: (ASCEND) cisco
Next by Date: (ASCEND) "MPP - no NULL msg timeout"
Prev by thread: (ASCEND) Busy Signals (max 4048)
Next by thread: RE: (ASCEND) Busy Signals (max 4048)
Index(es):
- Main
- Thread