PEAP - cannot logon using wireless with IAS, WPA

Zebis_nz used Ask the Experts™
Hi all,

I am testing our wireless network to change from WEP to WPA encryption with RADIUS (IAS) authentication with certificates.
I have read through and followed the steps outlined in Microsoft's "Securing Wireless LANs with PEAP and Passwords"

On a test laptop, I cannot log onto the client from the logon screen with wireless enabled. It hangs with "Loading / Applying your personal settings"
After logon if I enable the wireless, I get a successful 'connected' wireless message, get assigned a correct DHCP address and can ping internal servers. I can perform successful DNS lookups.
However I cannot browse any servers using '\\servername', or connect to any file & printer shares, or access any AD info.

I get errors in the event logs of the server and client:

Event ID 2
User <not present>  was denied access.
 Fully-Qualified-User-Name = DOMAIN\Guest
 Proxy-Policy-Name = Use Windows authentication for all users
 Authentication-Provider = Windows
 Authentication-Server = <undetermined>
 Policy-Name = <undetermined>
 Authentication-Type = EAP
 EAP-Type = <undetermined>
 Reason-Code = 34
 Reason = Authentication failed because the user account is not enabled. Before the account can be authenticated, a person with administrative rights for either the computer or the domain must enable the user account.

On the client:

Event ID 1053
Windows cannot determine the user or computer name (An internal error occured)
Event ID 15
Automatic certificate enrollment for local system failed to contact the active directory (0x8007041d)
Event ID 40960
The Security System detected an attempted downgrade attack for server <server name>.
Event ID 40961
The Security System could not establish a secured connection with the server <server name>.

Do I have to do something with the Guest account? - when using PEAP - I didnt read anything in the manual.

Where should I start looking?

Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®


Also when I do a netstat -a on the client I get:
TCP 1337 / 1340 / 1341 / 1342 ESTABLISHED

But when I try to access the server I get:
TCP 1340 / 1341 TIME_WAIT
after more time I get:
TCP 1337 / 1343 / 1360 / 1366 / 1370 / 1373 / 1377 FIN_WAIT_2

There is no firewall enabled on the client or the server.

Is the machine\user joined to the domain?  Is the Guest account enabled or disabled on the DC?  On the test laptop, what account are you using to log on (e.g. an AD user, a workgroup account, etc.)


>> Is the machine\user joined to the domain?
Yes the client is a domain intergrated PC (works fine off cable)

>> Is the Guest account enabled or disabled on the DC?
The Guest accound is currently disabled. Ive had the same fault with it enabled. I feel enabling the account opens other security risks.

Both the PC and the User are a member of the allowed group - however I do have one other test to try - I suspect the RADIUS server is setup to allow/pass User AND Computer - however initally there is only a 'Computer' account, so I really need User OR Computer.
Will experiment in the next few days.

>> On the test laptop, what account are you using to log on (e.g. an AD user, a workgroup account, etc.)
I am logging on the domain with my own domain user account (which has administrative privileges)
okay great.  I wouldn't enable the Guest account for the reason you stated.   No need.  Getting event ID 2, you are logically led in that direction.  I almost went down that route with this article, but didn't do it....

So, without messing with the Guest account, I setup a Cisco 1200  and IAS RADIUS/PEAP (however, I used WEP and open auth) and was running into the same problem as you loggin Event 2 and 1053.  Once I figured out what was wrong (suggestions below) and everything was successful, the domain user is prompted for credentials when connecting from a device not on the domain and if on the domain and the "Use Window Logon" is set, it is automatically connected.  For me, it turned out that I had misconfigured the client and that was it.  As you probably know the client side wireless adapters have many flavors and the applications that manage the connections can differ - and often times do.

HEre are the things I did and went through if they help you.....

Client --------

On some devices there was a setting for "Roaming Identity".  This was INDEPENDENT of UserName, Domain, and Password settings.  I had to set the Roaming Identity to match username.

Additionally, for some devices (mostly Pocket PCs) I had to manually install the cert prior to connecting. I still don't understand why I had to do that, but I did and it worked.


On server how did you create the Policy?  For me, I did the folllowing...

I created a security group in AD called WirelessUsers and I added members to that group (these users were part of another group, so I just added that group).  

In IAS, I right-clicked Remote Access Policies>New Remote Access Policy and followed the wizard like so...

--Left default "Use the wizard to set up a typical..."
--named the policy (e.g. wireless access)
--Selected Wireless
--Added my group WirelessUsers

After created, I selected the policy>properties and made sure "Grant access permission" was set.
Click Edit Profile button>Authentication tab.

Set MS-CHAP v2 and MS-CHAP.  Click on EAP methods button...

Select Protected EAP (PEAP) and click on Edit button.  Is the Certificate issued field display the server properly and is Issuer correct for your local Cert. Authority?

Under the Encryption tab, I only selected Strongest encryption (MPPE 128 bit).

And that was about it.  Check your IAS log files and see if the user name is showing up for the attempted connections.  If not, then the AP is not communicating with IAS.  If it is, then probably a client setting is incorrect.

Hope some of this helps.


I am still working on this solution however no luck at my initial attempt. Got other things on the go but will be trying and posting back within the next few weeks with more results / errors.


I think i have solved it.

I have created two seperate Remote Access Policies, one for the Computer, then a second for the User.
This way the computer is granted access when there is no user logged in (at the login prompt), and then after logon the user is granted access on a seperate policy.
It fully works with No Encryption, and appears to work although much slower with encryption enabled. I am just working on the speed issues but appears using two access policies has solved my problem.
PAQed with points refunded (300)

EE Admin

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial