RadiusNT: [RadiusNT] Radius Configuration Requests from Ascend MaxTNT's.

------=_NextPart_000_00BD_01BEE4C5.177C60B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

We've been running RadiusNT for quite some time. We have very few =
problems these days. We use MSSQL and ODBC, no problems. Something new =
has come up since our recent upgrade of our TNT's to a 7.X.X version of =
Ascend code...

We monitor failed authentications of all types, whether it be for Server =
Port Access, bad passwords, user not found, etc... and since we upgraded =
our Ascend products, we are getting flooded with tons of stuff like =
this:

Bad Password 08/10/99 02:45 PM |initial-banner|
|(4=18l=C10&|
|bogus|
Bogus=20

We get about 100 of these failures a minute from all of about 20 =
MaxTNT's. Ascend support told us to create usernames with a password of =
"bogus" for all the different "Radius Configuration Requests" coming =
from our terminal servers... The idea is that if the authentication =
fails (apparantly, the TNT's are looking for a password of "Ascend") the =
radius daemon will send back a reject to the server and the servers will =
stop sending these annoying requests. According to Ascend, the terminal =
servers will send all these requests any time the server is reset, or if =
the routing is changed, or for that matter if the configuration of the =
TNT is altered. Well, we don't modify our config too often, and we only =
cycle the power once a month on each server, so we can live with that... =
Anyway, we've created all the accounts they told us to create, and the =
problem persists. They said to talk with IEA-Software about it, =
according to Ascend there are others running Emerald Radius that have =
overcome this problem. Anybody seen this?

------=_NextPart_000_00BD_01BEE4C5.177C60B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

We've been running RadiusNT for quite =some=20time. We have very few problems these days. We use MSSQL and =ODBC,=20no problems. Something new has come up since our recent upgrade of =our=20TNT's to a 7.X.X version of Ascend code...

We monitor failed authentications of =all types,=20whether it be for Server Port Access, bad passwords, user not found, =etc... and=20since we upgraded our Ascend products, we are getting flooded with tons =of stuff=20like this:

We get about 100 of these failures a =minute from=20all of about 20 MaxTNT's. Ascend support told us to create =usernames with=20a password of "bogus" for all the different "Radius Configuration =Requests"=20coming from our terminal servers... The idea is that if the =authentication=20fails (apparantly, the TNT's are looking for a password of "Ascend") the =radius=20daemon will send back a reject to the server and the servers will stop =sending=20these annoying requests. According to Ascend, the terminal servers =will=20send all these requests any time the server is reset, or if the routing =is=20changed, or for that matter if the configuration of the TNT is =altered. =20Well, we don't modify our config too often, and we only cycle the power =once a=20month on each server, so we can live with that... Anyway, we've =created=20all the accounts they told us to create, and the problem persists. =They=20said to talk with IEA-Software about it, according to Ascend there are =others=20running Emerald Radius that have overcome this problem. =Anybody seen=20this?

Regards,

Gerry Catalano

PDQ.net, Inc.

(713)830-3170 voice

(713)830-3270=20fax