* This is the VOP Radius mailing list *
I've seen things like this using VOPRadius and an Access database.  Deleting
the record and re-creating it always fixes it.  I always assumed it was a
corrupt database record.

Randy Sweeten                          Technical Support
Central House Internet                www.centralhouse.net
Central House Technologies         www.centralhouse.com
(209)245-5900 x3                       [EMAIL PROTECTED]

Central House University
Online Training / Classes for End-Users, Business, Technical Certification
Over 400 Classes Available, as low as $55.00 per year
http://www.centralhouse.net/training/




-----Original Message-----
From: Brenda Donovan [mailto:[EMAIL PROTECTED]] 
Sent: Friday, October 04, 2002 1:56 PM
To: [EMAIL PROTECTED]
Subject: [VOP RADIUS] Adding new user errors


* This is the VOP Radius mailing list *
Twice within the past week, I've added two dialup users to the VOPDB just
like all the others I've added in the past...  However, the tech on the
other end could not get the username or passwords to work.  We tried a bunch
of variations.  To check his setup, I had him put in the generic test
account and password I have, and all worked just fine.  He was authenticated
and put online.

My uplink's radius uses mine via realm and these two are the only ones I've
ever had a problem with. They aren't duplicates, there is nothing unusual
about them.  The whole dialup db is only 356 users. 

When I created a totally different username and pw for these particular
users, the connections worked.

Both remote computers were using WinXP.  Nothing I did, including rebooting
the computers allowed those first choices of username to log on. Is XP
caching things?  

Any one seen or had any of these kinds of problems?


**
To leave this list, send an email to [EMAIL PROTECTED] and put
the word "LEAVE" in the BODY of the email.

**
To leave this list, send an email to [EMAIL PROTECTED]
and put the word "LEAVE" in the BODY of the email.

Reply via email to