I see that there has been mention of subject problem here. My question
is will the forthcoming release of RadiusNT 2.2.? be able to address any
of this problem?
It's clear that MS is not sending the proper accounting info and
therefore RadiusNT is rejecting the accounting data. Seems to me that
there might be some way to have RadiusNT accept some of the data, since
some data is being sent.