WW
-----Original Message-----
From: Josh Hillman <admin-maillist@talstar.com>
To: RadiusNT@iea-software.com <RadiusNT@iea-software.com>
Date: Wednesday, April 15, 1998 5:57 PM
Subject: Re: Malformed packet and Ascend Max
>> From: WebWiz <webwiz@atlcon.net>
>> Steve, I am running 2 Ascend Max 2012(s) with 5.0Ap48 on one and 6.0.2
>on
>> the other and both are authenticating from a single RadiusNT2.2 machine
>with
>> MSSQL database, not single problem has occured here. They have been up
>for a
>> while now, at least since 6.0 came out.
>
>The "malformed packet" message only shows up when using RadiusNT 2.5 -- not
>2.2.
>
>Josh Hillman
>hillman@talstar.com
>
>> -----Original Message-----
>> From: Josh Hillman <admin-maillist@talstar.com>
>> To: RadiusNT@iea-software.com <RadiusNT@iea-software.com>
>> Date: Wednesday, April 15, 1998 12:47 PM
>> Subject: Malformed packet and Ascend Max
>>
>>
>> >> Steve Luper wrote:
>> >> > 2.5 looks good and I can do ODBC with WINNT using radlogin but when
>> >> > trying to use 2.5 in conjunction with an Ascend Max 2012, I get
>> >> > "Malformed packet" everytime a user tries to authenticate.
>> >>
>> >> From: Dale E. Reed Jr. <daler@iea-software.com>
>> >> If you send me a -x15 -X capture of the packet, I'll quote the
>> >> RFC telling you why its Malformed so you can send it to Ascend.
>> >> You might want to check which version of AOS you are running.
>> >> Anything before 5.0Ap42 is pretty problem proned.
>> >
>> >For the record, Maxes with 6.0.2 do the same thing. I added the
>registry
>> >entry and that "fixed" the problem. Have you (Dale) sent
>> >support@ascend.com anything on this issue?
>> >
>> >Josh Hillman
>> >hillman@talstar.com
>
>
> ----------------------------------------------------------
> RadiusNT Mailing List lists@iea-software.com
>