<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<title>Re: MS 8021.x PEAP failing</title>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1768043225;
mso-list-type:hybrid;
mso-list-template-ids:438962668 67698699 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:3;
mso-level-number-format:bullet;
mso-level-text:\F0D8;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p><font size=3 color=navy face="Times New Roman"><span style='font-size:12.0pt;
color:navy'>> </span></font>Yup, that line is there. Much of the doc online
is WAY out of date, so I'm wondering if by actually RTFM first I broke something?<br>
<br>
<font color=navy><span style='color:navy'><o:p></o:p></span></font></p>
<p><font size=3 color=navy face="Times New Roman"><span style='font-size:12.0pt;
color:navy'>Ok. This may sound crazy and it may not be your problem, but,
I thought I’d mention it anyway.. Look at the samAccountName
attribute in A/D for a user that is failing and see if it is all lowercase. If
not and the userid wasn’t entered with the exact case in A/D, then you may
receive Logon failure in some circumstances. Check to see if your debug
output shows “Logon failure” from ntlm_auth. If so, you may
be having the same problem I’ve seen (incorrect MS-CHAPv1 challenge
created by rlm_mschap because the User-Name attribute doesn’t exactly
match the userid in the MS-CHAPv2 response packet’s Name field). I
have a patch for this problem that I just finished testing earlier today. I
need to clean it up a bit (remove excess debug code) and then I will submit it.
If this is affecting you, logging on with cached credentials, entering
the user/password manually or logging on with the userid in correct case is a
workaround.<o:p></o:p></span></font></p>
</div>
</body>
</html>