> They have not completely "gone away", but have definitely improved! When
> RadiusNT was on the same box, the CPU spikes would last for several minutes
> only to allow a couple seconds of normal activity. Now that RadiusNT is on
> a different box, the CPU spikes are still occurring (really odd), but they
> only last for a couple seconds at most followed by about 10-20 seconds of
> normal activity.
We were seeing this two, without pattern. As far as we good determine,
there were no performance issues related to the spikes, though.
> I know you love to hear this question asked, but when will the next version
> be available to the public?
I don't know, and I really don't think it will resolve the problem.
> >The other thing is this could be and ODBC issue. What version of the
> >SQL ODBC driver is on the other machine (not running SQL 7). Maybe
> >this is an issue with the SQL 7.0 ODBC driver?
> >
>
> This could be an ODBC driver issue.. as you can see above, Radius is much
> happier on the outside NT box that is running the 3.50.0305 driver than it
> is residing on the 3.70.06.23. As I recall we also had to fight a
> malformed packet problem when we first installed it on the SQL 7 box
> running 3.70.06.23 that does not exist on the older ODBC driver.
I'm running ODBC 3.5 with the SQL ODBC 3.7 Driver. Most people get
really confused on ODBC versions. There is the ODBC version itself
(the Manager, etc) and then there is the version for each of the
drivers.
The malformed packet is an option you control in the RadiusNT Admin.
> Right now I am spending the weekend trying to build another SQL7 box to
> test on. I'll let you know the results.
--Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list, including removal, pleasesee this URL: http://www.iea-software.com/maillist.html