My mistake on the above. Digging a little deeper, I found the
problem with it (I has something backwards). I was able to
get new code for RadiusNT 2.2 to work with the Windows NT
RADIUS client. Thats the good news. The bad news is it looks
like the accounting is pretty bad. For example, here is an
accounting pair:
radrecv: Request from host cf358111 code=4, id=5, length=69
Acct-Status-Type = Start
User-Name = "user"
CHAP-Challenge =
"\023l\222\266\271U\010*\320\025\364\373\354z\274\001"
Challenge-Response = "\002o\374R;\2120\034\003X\312\002?\2145\356t"
radrecv: Request from host cf358111 code=4, id=6, length=69
Acct-Status-Type = Stop
User-Name = "user"
CHAP-Challenge =
"\023l\222\266\271U\010*\320\025\364\373\354z\274\001"
Challenge-Response = "\002o\374R;\2120\034\003X\312\002?\2145\356t"
Now thats about useful. No NAS-Identifier, NAS-IPAddress, NAS-Port, or
NAS-Port-Type. Not even an Acct-SessionID or Acct-Session-Time, and
whats
all that CHAP-CRAP doing in accounting?
Moral of the story: Stick with Livingston, the people who invented
RADIUS,
and you'll be a much happier camper. :)
-- Dale E. Reed Jr. (daler@iea.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.emerald.iea.com