Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

OK guys, I've managed to get things working... It was a samba issue as mentioned before, I've had to include following line in smb.conf: winbind forcesamlogon = true took a little while googling but first of all my freeradius server was configured correctly... Thanks all for your time Lukas --

Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

Hi Alan, Thanks for quick reply I have read the log several times however nothing points me to the right direction...thats why I posted a question here... when I use usern...@domain.com I get access-reject as ntlm authentication fails so from this point its working ok I guess. Also I dont

Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

Pretty new to FR as well but from what it looks like to me is your using Workstation login not user login. The portion [suffix] No '@' in User-Name = host/W400210.interoute.com, looking up realm NULL [suffix] No such realm NULL ++[suffix] returns noop [eap] EAP packet type response id 198

Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

Hi Alan, my previous config is for FR 1.x, now I want to use FR 2.1.x so I dont think I can use same config files as there are some differences between FR 1 2, right? Its really strange as I've tried to build the system on FC10 last year already - configured from scratch but now with FC14

Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

here's the output of radius -X: (hope its long enough:)) [suffix] No such realm NULL ++[suffix] returns noop [eap] EAP packet type response id 245 length 59 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP # Executing group from file /etc/raddb/sites-enabled/default +-

Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

complete debug here: including configuration file /etc/raddb/radiusd.conf including configuration file /etc/raddb/proxy.conf including configuration file /etc/raddb/clients.conf including files in directory /etc/raddb/modules/ including configuration file /etc/raddb/modules/smbpasswd including

Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

lucky79 wrote: complete debug here: If you're not going to read it, then I don't see why you're asking questions here. The debug output contains instructions for solving the problem. Read it, and follow the instructions. Alan DeKok. - List info/subscribe/unsubscribe? See

Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

Hello everyone, is there any progress resolving this issue? I have samba 3.5.6 on FC14 and have the SAME problem like I've had with FC9/10, Freeradius2 and samba included with distribution. The problem is I cant rollback to older Samba version as it does not support Windows 2008R2 domain

Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

Hi, first off, i dont think this is a SAMBA issue...thats just me though - the SAMBA issue manifests itself in the authentication phase where ntlm_auth blows up (or rather is a damp squib) is there any progress resolving this issue? I have samba 3.5.6 on FC14 and have the SAME problem like

Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

Alan Buxey wrote: first off, i dont think this is a SAMBA issue...thats just me though - the SAMBA issue manifests itself in the authentication phase where ntlm_auth blows up (or rather is a damp squib) Sometimes ntlm_auth returns the *wrong* results, and only the client PC knows that

RE: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

users mailing list Subject: Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem Mike Loosbrock wrote: Check the versions of your samba packages. I'm running Debian and the exact same FreeRADIUS configuration works with 3.0.24 (stable) but fails with 3.2.5 (testing). The failure

RE: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

mailing list Subject: Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem Hi, Yeah that's got to be it. Fedora 8 uses 3.0.34 while fedora 10 uses 3.2.8. I'll have to try it with the old version of samba. I'll post back if it works. is this a confirmation that ntlm_auth doesnt work with samba 3.2.8

RE: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

To: FreeRadius users mailing list Subject: Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem Hi, Yeah that's got to be it. Fedora 8 uses 3.0.34 while fedora 10 uses 3.2.8. I'll have to try it with the old version of samba. I'll post back if it works. is this a confirmation that ntlm_auth doesnt

Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

On Feb 12, 2009, at 8:06 PM, Casartello, Thomas wrote: I have exactly the same problem with Fedora 9 and 10 only. It works perfectly fine in Fedora 8 with the exact same configuration. I have spent hours trying to fix this, and could not figure it out. Check the versions of your samba

Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

Mike Loosbrock wrote: Check the versions of your samba packages. I'm running Debian and the exact same FreeRADIUS configuration works with 3.0.24 (stable) but fails with 3.2.5 (testing). The failure is such that the mschap module returns success, but the very last EAP-MSCHAPv2 challenge

Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

Hi I configure Freeradius 2.1.3 how it describes in http://wiki.freeradius.org/FreeRADIUS_Active_Directory_Integration_HOWTO but it doesn't work. here is debug output: FreeRADIUS Version 2.1.3, for host i386-redhat-linux-gnu, built on Dec 8 2008 at 16:00:08 Copyright (C) 1999-2008 The

Re: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

andrey.trubni...@unicreditgroup.ru wrote: Hi I configure Freeradius 2.1.3 how it describes in http://wiki.freeradius.org/FreeRADIUS_Active_Directory_Integration_HOWTO but it doesn't work. ... Sending Access-Challenge of id 130 to 10.6.0.86 port 1645 EAP-Message =

RE: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem

...@unicreditgroup.ru Sent: Thursday, February 12, 2009 8:58 AM To: freeradius-users@lists.freeradius.org Subject: Freeradius2.1.3 + Fedora9 + PEAP + AD = problem Hi I configure Freeradius 2.1.3 how it describes in http://wiki.freeradius.org/FreeRADIUS_Active_Directory_Integration_HOWTO but it doesn't work