This incorrect password issue was solved once the proper server
certificate was used by FreeRADIUS' EAP.conf file.
Thanks for all you help!
Marc
Solution to get correct cert to work with Windows XP SP2 supplicant:
1) From Linux box:
openssl genrsa -des3 -out server1.key 2048
You will be
Hi Marc,
are you aware of
PEAP authentication is not successful when you connect to a third-party
RADIUS server
http://support.microsoft.com/kb/885453
Maybe it is somehow related?
Other updates I installed on XP SP2 for WLAN 802.1x and PEAP/EAP-TLS are
Hotfix 917021 (Wireless Client Update)
Hi.
[EMAIL PROTECTED] wrote:
either use your current tool but include the XP extensions as required,
Just to be precise. The named extensions are PKIX extensions for serverAuth
(OID 1.3.6.1.5.5.7.3.1) (at the RADIUS server) and clientAuth (OID
1.3.6.1.5.5.7.3.2) (for EAP-TLS on the supplicant).
Hi, it looks like I used a certificate with the wrong OID. I used a
cert minted with their SubCA template which doesn't have the (OID
1.3.6.1.5.5.7.3.1).
In playing with the Microsoft CA on Windows 2003 server, I've found
that the Certificate made using the Web Server template is the one
hi,
rlm_eap_tls: TLS 1.0 Alert [length 0002], fatal access_denied
TLS Alert read:fatal:access denied
rlm_eap_peap: No data inside of the tunnel.
rlm_eap: Handler failed in EAP/peap
rlm_eap: Failed in EAP select
okay. so thats the main issue. were your certificates generated with
the XP
Ok, that's what I thought (about the root Certificate not being pleasing
to XP).
FYI: I'm using a version of Linux by Novell called SLES (SUSE Linux
Enterprise Server) version 9 Service Pack 3 and the FreeRADIUS is from
Novell's Web site (freeradius-1.0.2-0.i586.rpm,
Hi,
If someone could give me the quickest and easiest way to creating a
root certificate that's works with Windows XP, that would be great.
either use your current tool but include the XP extensions as required,
or use the 1.1.6 FreeRADIUS source code - to simply use the script in
that to
7 matches
Mail list logo
