Fortunately or unfortunately, Windows doesn't just let you bypass an incorrect certificate without some hoops.

windows xp peap validating identity-77

See this for certificate requirements, the top section pertains to server certificates.

summarize the requirements (taken directly from the site): - The Subject name contains a value.

You might have read that Ms Chap can be broken Might consider using a public certificate, cost you something like $99 a year Here's some resources around certificates and NPS: as a work around - you can configure "less secure authentication methods" and allow for Mschap V2 without PEAP --- that solves your problem, but impose a security risk - and should only be used as a last resort to buy you some time to come up with a proper solution https:// thanks for the replies: - why are the i OS devices ok using the NPS cert but win pc's not?

- I already have a Wildcard ca cert, but this has the name of our external domain name *.rather than our internal windows domain. - surely access to the wireless network is protected by having a domain UN and PW, what difference does the level of PEAP etc make?

this really needs to be set somehow globally (on the NPS server?

) as it is student (non domain) laptops and we don't want them to have to configure anything, is this possible?Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking.It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.i Os devices have an easier way to install root certificates, than PCs - mainly due to the way they're supposed to work, while PCs mainly are supposed to be domain joined, and will get certificates automatically when joining domain.The name on the certificate must match the name of the NPS.Just to make sure: YOu've configured NPS Remote Access Policies to authenticate PCs (and i Os devices) using PEAP-Ms Chap V2 ?