IAS - PEAP - Signature Not Verified

I am trying to get my wireless users to be able to authenticate to my
wireless LAN.
We are using WPA. For users that have a laptop that is joined to the
domain and have a certificate authentication is not a problem. However,
for clients whose laptops are not joined to our domain whenever they try to
authenticate to the wireless LAN I get the following error in my system
event log:

Authentication-Provider = Windows
Authentication-Server = <undetermined>
Policy-Name = new-remote-access
Authentication-Type = PEAP
EAP-Type = <undetermined>
Reason-Code = 262
Reason = The supplied message is incomplete. The signature was not
verified.

I have configured the wireless client NOT to verify the server certificate,
but this does not fix the problem. This occurs with Vista clients.
I've googled pretty much every version of this error and everything seems to
say just tell the client not to verify the server certificate but that does
not fix the problem.

Any other ideas?

Anyone??

"Ken Teleis" <(E-Mail Removed)> wrote in message
news:9A7D9076-A695-42E3-9B10-(E-Mail Removed)...
>I am trying to get my wireless users to be able to authenticate to my
>wireless LAN.
> We are using WPA. For users that have a laptop that is joined to the
> domain and have a certificate authentication is not a problem. However,
> for clients whose laptops are not joined to our domain whenever they try
> to authenticate to the wireless LAN I get the following error in my
> system event log:
>
> Authentication-Provider = Windows
> Authentication-Server = <undetermined>
> Policy-Name = new-remote-access
> Authentication-Type = PEAP
> EAP-Type = <undetermined>
> Reason-Code = 262
> Reason = The supplied message is incomplete. The signature was not
> verified.
>
> I have configured the wireless client NOT to verify the server
> certificate, but this does not fix the problem. This occurs with Vista
> clients.
> I've googled pretty much every version of this error and everything seems
> to say just tell the client not to verify the server certificate but that
> does not fix the problem.
>
> Any other ideas?
>