(ASCEND) Restricting ODBC-SQL Profiles to 'Called-Station-Id' and/or 'NAS- Port-Type'?

To: "'support@ascend.com'" <support@ascend.com>
Subject: (ASCEND) Restricting ODBC-SQL Profiles to 'Called-Station-Id' and/or 'NAS- Port-Type'?
From: "Rogers, Kirk" <Kirk.Rogers@trw.com>
Date: Tue, 20 Oct 1998 09:56:54 -0700
Cc: "'Ascend Mailing List'" <ascend-users@bungi.com>
Sender: owner-ascend-users@max.bungi.com

Another Bug perhaps?
We are running AAC RADIUS Ai11 on an (2) NT servers (primary and backup),
MSSQL 6.5 for accounting and authentication, and have (3) MAX4000's
utilizing this configuration.  I've just converted most of our 'flat file'
profiles over without incident, but now have a problem with
'Called-Station-Id' and 'NAS-Port-Type' auth. Attributes.  The AAC RADIUS
log file returns:

Mon Oct 19 11:00:45 1998: odbc_auth_machine(): Check-item Called-Station-Id
missing
Mon Oct 19 11:00:45 1998: odbc_auth_machine(): Check-item NAS-Port-Type
missing

And the user does not get connected.  The column names in SQL are:

Called_Station_Id  varchar  20 NULL
NAS_Port_Type  int  4  NULL

Can someone verify this for me and let me know if these work?  The
documentation for AAC does not state any problem and includes them in the
list of 'check-items' for ODBC authentication attributes.

Kirk




++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

Prev by Date: Re: (ASCEND) Mixing Modem Packs
Next by Date: No Subject
Prev by thread: No Subject
Next by thread: (ASCEND) TNT for sale
Index(es):
- Main
- Thread