(RADIATOR) Radiator on Win2k w/MS-SQL 2000 problem

Justin Scott jhs at ocs-tx.com
Tue Jan 15 11:49:38 CST 2002


Hey guys... sorry if my previous message went through... my connection to the house (and my normal mutt mailer) is down, and I'm having to use work's web-based email.

Anyhow... long story short, we're trying to get AuthBy SQL working with MS-SQL 2000 (running on the same machine with Radiator, accessing via ODBC), and we're having "Bad Password" replys constantly, even though we know the user/pass combo is correct.

Here's the config:

Foreground
LogStdout
LogDir          c:/radiator/logs
DbDir           c:/radiator/raddb
Trace           4
<Client DEFAULT>
        Secret mysecret
        DupInterval 0
</Client>

<Realm DEFAULT>
        <AuthBy SQL>
        DBSource        dbi:ODBC:Radiator
        DBUsername      mydbusername
        DBAuth          mydbpassword
        AuthSelect select PASSWORD from tblsubscribers where USERNAME = %0
        </AuthBy>
   AuthByPolicy ContinueUntilAccept
   RejectHasReason
</Realm>

And here's the debug dump from radiator (checked via radpwtst):

Tue Jan 15 11:10:00 2002: INFO: Server started: Radiator 2.19 on OCSAUTH
Tue Jan 15 11:11:04 2002: DEBUG: Packet dump:
*** Received from 127.0.0.1 port 3879 ....
Code:       Access-Request
Identifier: 171
Authentic:  1234567890123456
Attributes:
        User-Name = "balz"
        Service-Type = Framed-User
        NAS-Identifier = "203.63.154.1"
        NAS-Port = 1234
        Client-Port-DNIS = "123456789"
        Caller-Id = "987654321"
        NAS-Port-Type = Async
        User-Password = "<197><143><172><17><(<193><190><249><231>0<0>,u><212>"

Tue Jan 15 11:11:04 2002: DEBUG: Handling request with Handler 'Realm=DEFAULT'
Tue Jan 15 11:11:04 2002: DEBUG:  Deleting session for balz, 203.63.154.1, 1234
Tue Jan 15 11:11:04 2002: DEBUG: Handling with Radius::AuthSQL
Tue Jan 15 11:11:04 2002: DEBUG: Handling with Radius::AuthSQL:
Tue Jan 15 11:11:04 2002: DEBUG: Query is: select PASSWORD from tblsubscribers w
here USERNAME = 'balz'

Tue Jan 15 11:11:04 2002: DEBUG: Radius::AuthSQL looks for match with balz
Tue Jan 15 11:11:04 2002: ERR: Attribute number 79 is not defined in your dictio
nary
Tue Jan 15 11:11:04 2002: DEBUG: Radius::AuthSQL REJECT: Bad Password
Tue Jan 15 11:11:04 2002: DEBUG: Query is: select PASSWORD from tblsubscribers w
here USERNAME = 'DEFAULT'

Tue Jan 15 11:11:04 2002: INFO: Access rejected for balz: Bad Password
Tue Jan 15 11:11:05 2002: DEBUG: Packet dump:
*** Sending to 127.0.0.1 port 3879 ....
Code:       Access-Reject
Identifier: 171
Authentic:  1234567890123456
Attributes:
        Reply-Message = "Bad Password"

Anyhow, I know the password is right, the table name is right, the ODBC DSN is right, the db user/pass are right.  I don't get any connection errors, it just is convinced that the PASSWORD is incorrect.

These are PLAIN TEXT passwords in the database, and need to stay that way for my client's other internal needs.

I've been through the manual and a few months of list archives, and didn't find anything quite like this.

Anyone have a clue they could lend? :)

cheers,
j
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.


More information about the radiator mailing list