I saw the following in the mail archives:
> 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
There's a referecned to a a registry entry. What is this registry entry
that needs to be fixed?
thanks
George
--------------642EE3DADEDAF99D0D298E3A
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
I saw the following in the mail archives:
> Steve Luper wrote:There's a referecned to a a registry entry. What is this registryentry that needs to be fixed?
> > 2.5 looks good and I can do ODBC with WINNT using radlogin butwhen
> > 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
thanks
George--------------642EE3DADEDAF99D0D298E3A--