Message 2: Re: CallsOnline - table vs query?
from "Dale E. Reed Jr." <daler@iea-software.com>
Message 3: Re: Radius start error (solved)
from Scott Lagos <slagos@net1plus.com>
Message 4: Re: Y2K and Radius: maExpireDate above 12-31-1999 (year 2000)
produces login failures
from Mike Miller <michael@abraxis.com>
Message 5: maExpireDate not working
from "Majordomo@essex1.com" <majordomo@essex1.com>
Message 6: Re: Access performance
from Ted Olson <tolson@ocsnet.net>
Message 7: ServerPorts works!
from Ted Olson <tolson@ocsnet.net>
Message 8: Re: maExpireDate not working
from "Dale E. Reed Jr." <daler@iea-software.com>
Message 9: Re: Crashed when reloaded
from "Dale E. Reed Jr." <daler@iea-software.com>
Message 10: Re: ServerPorts works!
from "Dale E. Reed Jr." <daler@iea-software.com>
Message 11: Re: ServerPorts works!
from Ted Olson <tolson@ocsnet.net>
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.
| Message 1 |
'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'
Subject: Re: Radius start error (solved)
From: "Dale E. Reed Jr." <daler@iea-software.com>
Date: Sun, 26 Jul 1998 23:25:24 -0700
Ted Olson wrote:
>
> RECAP
> The good news is that all is running great again! I still have a question
> mark about what actually happened to cause the problem in the first place,
> but that may never be known. Would a reinstall of 1.16 have solved it?
> Maybe, but by the time we reached that point it didn't make sense not to
> move up to 2.5 (if that had not worked we would have backtracked).
I don't know exactly why 2.5 works better with the ODBC 3.x and higher
drivers, but its does. At an API layer, we are using the same calls.
However, at an implementation level, it was completely re-written to
be optimized for speed and flexibility.
What I would be interested in Access is what the performance different
(whether good or bad) is with RadiusNT 2.5, since it opens two
connections
to the database (one for accounting and one for authentication).
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 2 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: CallsOnline - table vs query?From: "Dale E. Reed Jr." <daler@iea-software.com>Date: Sun, 26 Jul 1998 23:35:50 -0700
Ted Olson wrote:> > Just a low-key question: What are the reasons or opinions, one way or the> other, for setting up a CallsOnline table versus just running a query?> We've been using the query method for quite some time now, just curious> about the rationale or possible uses/advantages for the table...
A query is a one of providing data without having to understand the details of where the data is coming from. The advantage on theuser side of a query is that the query can be adapted to what theuser wants. Queries are a way of dynamically re-shaping data.
In SQL Server a stored procedure (like a query) can be pre-compiledand offer significant performance benefits over just executing aquery.
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 3 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Radius start error (solved)From: Scott Lagos <slagos@net1plus.com>Date: Mon, 27 Jul 1998 08:14:35 -0400
I'd be willing to test this and provide you with details if there was db inAccess95...I'm lazy and dont want to RTFM.
Does anyone have the structures already in Access95?
At 11:25 PM 7/26/98 -0700, you wrote:>Ted Olson wrote:>> >> RECAP>> The good news is that all is running great again! I still have a question>> mark about what actually happened to cause the problem in the first place,>> but that may never be known. Would a reinstall of 1.16 have solved it?>> Maybe, but by the time we reached that point it didn't make sense not to>> move up to 2.5 (if that had not worked we would have backtracked).>>I don't know exactly why 2.5 works better with the ODBC 3.x and higher>drivers, but its does. At an API layer, we are using the same calls.>However, at an implementation level, it was completely re-written to>be optimized for speed and flexibility. >>What I would be interested in Access is what the performance different>(whether good or bad) is with RadiusNT 2.5, since it opens two>connections>to the database (one for accounting and one for authentication).>>-- >Dale E. Reed Jr. (daler@iea-software.com)>_________________________________________________________________> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs> Internet Solutions for Today | http://www.iea-software.com>
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 4 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Y2K and Radius: maExpireDate above 12-31-1999 (year 2000) produces login failuresFrom: Mike Miller <michael@abraxis.com>Date: Mon, 27 Jul 1998 11:23:25 -0400
Yes, the 2050 thing was verified in SQL as 2050. As for the saExpireDate,I have not tested the saExpireDates yet, only the maExpireDate. Right nowwe don't actually use the saExpireDate's here.. just leave them null. Isuppose if there is an issue with the saExpire it would be good to know,just in case we should decide to begin using it.
At 03:48 PM 7/25/98 -0700, you wrote:>Yes, 8 digit dates take care of it once and for all. I just wanted to point>out SQL Server's default behavior for 6 digit dates. If you're curious,>paste the following SQL into ISQL and execute it and you'll see exactly what>I'm talking about.>>select convert(datetime, '12/31/49')>select convert(datetime, '1/1/50')>>The first select returns Dec 31 2049 12:00AM>The second one returns Jan 1 1950 12:00AM>>I'm very comfortable with 2.5's Y2K compliance. I did notice in 2.2 that if>I put in an saExpireDate >= 1/1/2000 authentication would think that the>account was expired, but no problem in 2.5.>>
==================================================== /\ Mike A. Miller == /--\ \/ Abraxis Networks ==/ \ B R A /\ I S == / == N E T W O R K S michael@abraxis.com====================================================
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 5 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: maExpireDate not workingFrom: "Majordomo@essex1.com" <majordomo@essex1.com>Date: Mon, 27 Jul 1998 11:21:59 -0500
Howdy; Ever since we converted over from Access to SQL the maExpireDate stoppedworking. The saExpireDate works, just not the Master Account one. We usethis field to put accounts with expiring credit cards on old, but we canuse the saExpireDate field instead. Any ideas on why Radius doesn't usethis field? It looks fine in SQL. I do have a request for a future feature. What is the possibility of a'Start On Date' field. The majority of our new users start at the first ofthe month and it would be very convenient to enter the information ahead oftime and simply set the date that their account will become active.
Thanks :) R. Laughlin Majordomo@essex1.com Essex Internet Sterling, IL 61081 (815) 625-8893
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 6 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Access performanceFrom: Ted Olson <tolson@ocsnet.net>Date: Mon, 27 Jul 1998 09:20:55 -0700
At 11:25 PM 7/26/98 -0700, you wrote:>What I would be interested in Access is what the performance different>(whether good or bad) is with RadiusNT 2.5, since it opens two>connections >to the database (one for accounting and one for authentication).
Hmmm ... if our transition to 2.5 had been planned rather than impromptu,we could have run some before-and-after execution time tests. Now, anyfeedback on this would only be subjective, no way to compare real numbers.If we notice any obvious change one way or the other I'll let you know.
-Ted
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 7 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: ServerPorts works!From: Ted Olson <tolson@ocsnet.net>Date: Mon, 27 Jul 1998 12:43:31 -0700
When running 1.16.49, the FramedAddress in ServerPorts was never correct -that is, it never matched the address in the Calls table, which *was*correct. Looks like that's fixed in 2.5 (maybe also in 2.2, I don't knowsince we skipped that release). Thank you, that's very handy! :)
-Ted OlsonOCS Software
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 8 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: maExpireDate not workingFrom: "Dale E. Reed Jr." <daler@iea-software.com>Date: Mon, 27 Jul 1998 12:50:26 -0700
Majordomo@essex1.com wrote:> > Howdy;> Ever since we converted over from Access to SQL the maExpireDate stopped> working. The saExpireDate works, just not the Master Account one. We use> this field to put accounts with expiring credit cards on old, but we can> use the saExpireDate field instead. Any ideas on why Radius doesn't use> this field? It looks fine in SQL.
Make sure that is not NULL, and the the extension and overdue fields are0.RadiusNT adds all of those together to come up with the final date.However,it only uses the saExpireDate is the saExpireDate is not NULL. Therefore,if you want to use the maExpireDare, you MUST make the saExpireDateNULL.Remember, MS Access mode doesn't support the saExpireDate field.
> I do have a request for a future feature. What is the possibility of a> 'Start On Date' field. The majority of our new users start at the first of> the month and it would be very convenient to enter the information ahead of> time and simply set the date that their account will become active.
Its already there; RadiusNT just doesn't use it. I've been meaning toput it in (as an option) buyt haven't gotten around to it (its low onthelist).
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 9 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Crashed when reloadedFrom: "Dale E. Reed Jr." <daler@iea-software.com>Date: Mon, 27 Jul 1998 13:01:40 -0700
Wilyono Jusuf wrote:> > Each time I tried to reload users database, the RadiusNT service> always crashed. And I had to restart the machine, since restarting> the service didn't help. Dr. Watson errors were displayed during> the reboot process.> > Below is what authentication log showed:
We are working on a fix for this (its a new bug in RadiusNT 2.5).
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 10 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: ServerPorts works!From: "Dale E. Reed Jr." <daler@iea-software.com>Date: Mon, 27 Jul 1998 15:31:46 -0700
Ted Olson wrote:> > When running 1.16.49, the FramedAddress in ServerPorts was never correct -> that is, it never matched the address in the Calls table, which *was*> correct. Looks like that's fixed in 2.5 (maybe also in 2.2, I don't know> since we skipped that release). Thank you, that's very handy! :)
Don't be shocked if you find a lot more things that work betteras well. Although 1.16.x worked very well for its time, it is athree year old "dinasour" in computer age. This is one of thereasons we can't support it anymore (besides the fact that I don'tremember msot of its features/bugs. :)
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 11 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: ServerPorts works!From: Ted Olson <tolson@ocsnet.net>Date: Mon, 27 Jul 1998 16:22:58 -0700
Those are the kinds of shocks we like! Thanks for the good work Dale...
-Ted
At 03:31 PM 7/27/98 -0700, you wrote:>Ted Olson wrote:>> >> When running 1.16.49, the FramedAddress in ServerPorts was never correct ->> that is, it never matched the address in the Calls table, which *was*>> correct. Looks like that's fixed in 2.5 (maybe also in 2.2, I don't know>> since we skipped that release). Thank you, that's very handy! :)>>Don't be shocked if you find a lot more things that work better>as well. Although 1.16.x worked very well for its time, it is a>three year old "dinasour" in computer age. This is one of the>reasons we can't support it anymore (besides the fact that I don't>remember msot of its features/bugs. :)>>-- >Dale E. Reed Jr. (daler@iea-software.com)>_________________________________________________________________> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs> Internet Solutions for Today | http://www.iea-software.com>