Ive had similar weirdness, where if I went and re-assigned the user the SAME password (we have it set where radius uses unix for password verification), it would work fine again. To me this smells like a crypt bug in one or more places. On Mon, 3 Jun 2002, Jason Straight wrote: > >From syslog: > LAN security error, username [MBID 21] > > >From radius.log: > Error: Acct: Invalid STOP record. [] STOP record but zero session length? > > Can anyone tell me what this means? I'm getting this now and then on a few > accounts and of course the user cannot login. I also get the accompanying > stop record with zero lenght error in radius logs after the connection. > > The connection is established, IP# and DNS are assigned and then the > connection drops before allowing any traffic to pass. > > > The last user it happened to I was able to reboot the NAS and he could then > login. The odd part is that it was happening to him based on user account. > His username/pwd would yeild the same results when we tried from his windows > box, or my linux. Both could log in with my username which has the same > radius check and reply options. > > > Thanks > > -- > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Jason Straight > President > BlazeConnect Internet Services > Cheboygan Michigan > www.blazeconnect.net > Phone: 231-597-0376 > > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to ascend-users-request at bungi.com > Archives: http://www.nexial.com/mailinglists/ > ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/