Please read this entire posting before downloading the beta version of
RadiusNT. This message includes release notes, downloading
instructions, and support/feedback instructions.
RadiusNT 2.5 Beta 5 Release Notes
All support and discussion of RadiusNT 2.5 is to be
done on the following mailing list ONLY. Any posting or
discussion of RadiusNT 2.5 outside of this forum will
most likely remove you from testing future software.
The best quality we can have in a beta tester is the
ability to follow directions!
To subscribe to the RadiusNT-Beta mailing list, send a
message with a blank subject and the first line as
to firstname.lastname@example.org. This is the same list server
as the RadiusNT normal list.
This RadiusNT test is good through the end of April, 1998.
We expect to have a released version of RadiusNT 2.5
before the end of April, 1998.
If you are using MS Access, you may need to add some additional
fields to your database. The RadiusNT documentation covers
all the fields RadiusNT needs.
If you are using SQL Server or Emerald, there is a script
called rad25_up.sql which you need to run against your
database. This will add the appropriate tables and fields
to make sure RadiusNT 2.5 works with a database that
RadiusNT 2.2 worked with. You may want to actually look
at the script before running it (especially for non-Emerald
This release includes support for Oracle and Sybase. You
can download the preliminary scripts for these from
their directories in /radiusnt/beta on the FTP site. These
scripts have not been fully tested.
The documentation for RadiusNT 2.5 is available in the beta
directory. PLEASE read through the docs before installing 2.5.
I know reading docs is a terrible thing, but since you make
us write them, we should make you read them! The docs are
current for 2.5 and cover all aspects of the RadiusNT 2.5 and
its features. Please let us know if you see anything missing
or incorrect in the docs.
PLEASE READ THE DOCS BEFORE POSTING TO THE BETA LIST. There
is a really good chance your question might be answered in
There are two known issues with late workarounds that may or
may not be in the documentation with this beta.
USR/3COM customers may receive Malformed packet warning from
RadiusNT 2.5, although RadiusNT 2.2 worked fine. This is
because RadiusNT 2.5 adheres more strictly to the RADIUS
protocol. USR is sending an attribute with length of two
in their accounting packet (blank string) and the RFC
specifies the length must be 3 or more.
To allow RadiusNT to accept these packets, add a registry
value of the following:
of type REG_SZ with the value of 1 and restart RadiusNT.
RadiusNT 2.5 also had a new feature to trim out spaces
before and after usernames. It will do this for
authentication and accounting records (at the packet
decode level to be consistent). You can enable this
option in the RadiusNT administrator. You can not
have usernames with spaces in them if you enable this
option (sometimes allowed with the NT SAM).
This beta is an un-supported beta by IEA Software, Inc.
If you are not familiar with RadiusNT and your operation, you
should NOT try this beta. IEA Software will NOT support this
beta via normal support channels (the only support is via the
Please read the Beta and End-User license agreement for exact details
when you install RadiusNT 2.5.
Downloading the Beta
Obtain RadiusNT 2.5 Beta 5 from
RNT25B5.zip: RadiusNT 2.5 Beta 5, Zipped
rad25docs.zip: RadiusNT 2.5 Beta 5 Documentation in Microsoft Word
rad25_up.sql: SQL query to add additional fields to your database
We look forward to your feedback regarding your experiences with
RadiusNT 2.5. Please remember to use the mailing list as your forum
for discussion - this will not only allow you access to the knowledge
base of other testers, but will help us be more efficient as we move
from this open beta to the supported and released RadiusNT 2.5
The IEA Software Staff