To follow up on Alan's reply.
Angelos's Guidelines for debugging radius.
A) Windows errors don't mean a thing even to microsoft
b) A "Login OK" does not mean that your dialup will be successful, where a
"Login Incorrect" is always a failure
c) Keep at hand the Access Server Admin
d) run "tcpdump -X -s 1500 udp and port 1645 or port 1812"
e) Watch the output REAAAAAALLLYYYYYYY carefully you will see entries like
10:30:27.769065 radion.unix.gr.datametrics >
fasteth00-00.the03.cas.unix.gr.datametrics: rad-access-accept
151 [id 153] Attr[ Service_type{#519} Framed_proto{#268}
Framed_mtu{1500} Framed_compress{#284} Idle_timeout{15:00 min} Service_type{#519}
Framed_proto{#264} Framed_ipaddr{NAS_select}
Session_timeout{229:29:36 hours} Reply{Login succefull. Maximum
session time 9 days 13 hours 29 minutes 36 seconds} ] (DF)
f)Verify these settings with the Access Server
in case of mismatch you have problems like the weird windows error codes
Your milage may vary
On Wed, 20 Nov 2002, Alan DeKok wrote:
> William Ragsdale <[EMAIL PROTECTED]> wrote:
> > Right, Except that the Windows Dialup User doesn't get a "invalid
> > password error" (691) they get a "The PPP link control protocol was
> > terminated" (734).
>
> The RADIUS server doesn't control those error messages.
>
> > The old radius generates the 691 error, while every version of Freeradius
> > generates the 734. I do not understand what is different about FreeRadius
> > that is causing this.
>
> Then use 'tcpdump' to find out. Look at the Access-Reject sent by
> the other server, and look at the Access-Reject sent by FreeRADIUS.
> They will contain different attributes.
>
> Configure FreeRADIUS to send the same attributes as the old server,
> and you will get the old error in PPP.
>
> Alan DeKok.
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
>
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
