Some limitations?
I noticed that I could not get radiusNT to accept more than 16 characters
for my NAS when using database.....this was a real problem I had to drop
all ref to DNS to the NAS machines due to the fact that my root domain =
name
alone is longer than that.
Also, has anyone configured radius to give out static ips and routes ok
with Access database? I can't seem to get it to do that at all, doesn't
like an IP address for a value of the Framed-Address attribute. And =
would
you have to setup a profile for EACH user with a different static ip.
Using Access db, ODBC, radius.6, NT4 SP3
On Thu, 22 May 1997 18:17:32 -0700 (), Dale E. Reed Jr. so eloquently
wrote:
>
>On Wed, 21 May 1997, Brian Johnson wrote:
>
>> Thanks for the quick responses on the install problem I had. Now I =
still
>> have one question. What is the advantage of using Radius over the
>> typical username/password? I understand that Radius encrypts the
>> traffic between the server and the portmaster, but how does that =
equate
>> to increased authentication? I read the FAQ but I'm still a bit foggy.
>
>The main adcanatge is a central user database. If you point the
>information into the local user table of the NAS, you then have to put =
the
>information to the local user table of ALL terminal servers. Thats a
>lot of work with many NASes. :( The Accounting (especially with a =
package
>like Emerald) is invaluable to a business, as well.
>=20
>> Also will this work with token cards (SDI or CryptoCard)
>
>We have been trying to work with Security Dynmaics.
>
>Dale
>
>
>
> ----------------------------------------------------------
> RadiusNT Mailing List listserver@emerald.iea.com
>