DUN Protocol Errors

Kent Runyan ( (no email) )
Thu, 22 Jan 1998 22:37:32 -0700

This is a multi-part message in MIME format.

------=_NextPart_000_001C_01BD2786.543C97C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

We have recently seen a huge increase in "Dial-up adapter was unable to =
negotiate a compatible set of network protocols..."

We are running 2 Livingston PM2e (analog Sportster modems) and 1 USR =
Total Control (digital Channelized T-1 for X-2 support) . We have =
always had a few of these errors from time to time (5-10 a week) , but =
now we see at least 5 a day and we haven't made any changes here lately. =
We use RadiusNT 1.16.60 and authenticate to a SQL database.

Does anybody have an idea where I might find a solution to this problem? =
Some people tell me that they sometimes have to try 2 or 3 times before =
they can get through.

Kent Runyan, Operations Manager
Konnections, Inc.
2650 Washington Blvd. Ste 208
Ogden, UT 84401
801-621-8511
http://www.konnections.com

------=_NextPart_000_001C_01BD2786.543C97C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">

We have recently seen a huge =increase in=20"Dial-up adapter was unable to negotiate a compatible set of =network=20protocols..."
 
We are running 2 Livingston PM2e (analog Sportster =modems) and=201 USR Total Control (digital Channelized T-1 for X-2 support) .  We =have=20always had a few of these errors from time to time (5-10 a week) , but =now we=20see at least 5 a day and we haven't made any changes here lately.  =We use=20RadiusNT 1.16.60 and authenticate to a SQL database.
 
Does anybody have an idea where I might find a =solution to=20this problem?  Some people tell me that they sometimes have to try =2 or 3=20times before they can get through.
 
 
Kent Runyan, Operations =Manager
Konnections,=20Inc.
2650 Washington Blvd. Ste 208
Ogden, UT =84401
801-621-8511
http://www.konnections.com
<=/DIV>------=_NextPart_000_001C_01BD2786.543C97C0--