Re: Problems with upgrade!

Dale E. Reed Jr. ( (no email) )
Mon, 22 Jun 1998 23:34:30 -0700

webmaster wrote:
>
> RadiusNT Enterprise Initialized...
>
> radrecv: Request from host cd98a421 code=1, id=240, length=105
> User-Name = "abcd"
> Challenge-Response = "\001\360V+\306S/y\2423[\237u\315C+E"
> NAS-IP-Address = ###.###.###.##
> NAS-Port = 20102
> NAS-Port-Type = Async
> Request from ###.###.###.## - Malformed Packet

If you update to RadiusNT 2.5.124, it allows Malformed Packets by
defualt. The earlier versions require you to add a registry setting,
which is noted in the release notes for RadiusNT 2.5.

> Here are some excerpts from the users file:
> ace Password = "????????????"
> User-Service = Framed-User,
> Framed-Protocol = PPP,
> Framed-Address = 0.0.0.0

Framed-Address of 0.0.0.0 is most likely incorrect. If you want dynamic
assigned addresses, use 255.255.255.254.

> These same settings worked without a hitch in v2.2. Our modem racks are
> using V.90 software, could that be causing the Malformed Packet entry? For
> the DOS Prompt data, there was no logfile entry. This was pasted directly
> out of the dos screen! The logfile was with logfile declared!

RadiusNT 2.5 is much more strict and RADIUS compliant. 2.2 was more
relaxed.

-- Dale E. Reed Jr.  (daler@iea-software.com)_________________________________________________________________       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  |   http://www.iea-software.com