Dear Eliot Gable,

Try to use shorter secret.

--Tuesday, December 2, 2003, 6:08:17 PM, you wrote to [EMAIL PROTECTED]:

>>From the NAS realms.conf file: 

EG> realm homenode.greatlakes.net {
EG>         type=radius
EG>         authhost=208.244.161.200:1812
EG>         accthost=208.244.161.200:1813
EG>         secret=076q2345hudp89YASIJF7890QW4
EG>         nostrip
EG> }

>>From the server's clients.conf file:

EG> client homenode.greatlakes.net {
EG>         secret          = 076q2345hudp89YASIJF7890QW4
EG>         shortname       = homenode
EG> }


EG> The NAS is running "FreeRADIUS Version 0.9-pre, for host i686-pc-linux-gnu, built 
on Feb 21 2003 at 15:58:26".

EG> The Server is running "FreeRADIUS Version 0.9.3, for host i686-pc-linux-gnu, built 
on Dec  1 2003 at 16:31:07"

EG> I cannot change what is running on the NAS, but I can change what is running on 
the server if it is a version conflict or something.

EG> -----Original Message-----
EG> From: 3APA3A [mailto:[EMAIL PROTECTED] 
EG> Sent: Tuesday, December 02, 2003 5:27 AM
EG> To: Eliot Gable
EG> Subject: Re: MS-CHAPv2 + MySQL + group authtype failure

EG> Dear Eliot Gable,

EG> Make  sure  shared  secret  configured  for  NAS and password entered by
EG> client are valid. Check cleartext and MS-CHAP (v1) authentication.

EG> --Tuesday, December 2, 2003, 3:04:02 AM, you wrote to [EMAIL PROTECTED]:


EG>> I've been trying to get a Windows XP machine to authenticate against freeRADIUS 
0.9.3 using MS-CHAPv2. It seems to be working to start with, but then I get a 
group-check failure. I can't figure
EG>> out why I'm getting that. I modified the rlm_mschap.c file to print out the two 
strings it is comparing where the failure takes place. I didn't format it nicely, so 
it looks like gibberish, but
EG>> it at least shows how different the strings are. I'm using MySQL to store the 
username/password and group information. 



-- 
~/ZARAZA
Впрочем, важнее всего - алгоритм!  (Лем)


-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to