Are you sure? Nothing works when I include quotes in those fields. Only
without the quotes will our Ascend MAX correctly pull up the proper outbound
profile and try to dial out. We're not getting authenticated connections,
but I'm still looking for a customer that can spend a little time sitting at
the other end telling us what they're seeing.
On the other hand, if you have a working example of an outbound route and
outbound profile entry for Ascend ISDN in SQL Server I'm sure it would be
-Robert F. O'Connor
System Administrator, Metro.Net
[mailto:email@example.com]On Behalf Of Dale E. Reed Jr.
Sent: Wednesday, August 19, 1998 8:59 PM
Subject: Re: Text backup from database - more
Kurt Lange wrote:
> I was playing with radusers.exe and ran in to a problem with attributes
> have more then one parameter. It appears that attributes with a space in
> them i.e. Framed Route, won't load from the text file. When I put the
> in with quotes around it it will load from the file and appears to auth OK
> but the route doesn't work in the NAS (it does work when NOT in quotes).
Framed-Route should be "Framed-Route". Attriubute names can not have
spaces in them. This is reall the Emerald compatability issue that
I was referring to with the newer version of radusers.
> Framed Route "188.8.131.52/24 184.108.40.206 1"
> Loads text file in RadiusNT but doesn't work on NAS (USR TC
> Framed Route 220.127.116.11/24 18.104.22.168 1
> Works on NAS but RadiusNT gives the following error on load:
> radius: attribute name 22.214.171.124 not found
> radius: Parse error -95 for user USERNAME
> 1778 users loaded!
It should be:
Framed-Route = "126.96.36.199/24 188.8.131.52 1"
For string attributes, you must include the begin/end quotes in the
data field of the RadConfigs/RadATConfigs tables.
--Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com