No certificate found - WIFI

Hey

We have some XP machines SP3.

The PKI has issued a certificate to the computer, and we see the certificate on the computer.

After installation they got a computer certificate for WIFI, but when connecting to the AP XP just says "No certificate found"

The settings for the WIFI is correct.

If we plug in a LAN cable and run GPUpdate the computer now suddenly can connect to the AP.

Any ideas?
LVL 1
mikeydkAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Keith AlabasterEnterprise ArchitectCommented:
If you had run gpupdate - before putting in the lan cable - did it still fail?

Now you have one of the machines working over the LAN, if you go back to wireless, does it still work or fail again?
0
Jakob DigranesSenior ConsultantCommented:
first of all - you need to check that certificate is indeed enrolled to computer,
start MMC - add snap-in Certificates and choose Computer Account - and look in Personal and make sure that there's a computer certificate that is valid. If it is - make sure that certificate has the correct  intended use
more here:
One such requirement is that the certificate is configured with one or more purposes in EKU extensions that correlate to the certificate use. For example, a certificate used for the authentication of a client to a server must be configured with the Client Authentication purpose. Similarly, a certificate used for the authentication of a server must be configured with the Server Authentication purpose. When certificates are used for authentication, the authenticator examines the client certificate, seeking the correct purpose object identifier in EKU extensions. For example, the object identifier for the Client Authentication purpose is 1.3.6.1.5.5.7.3.2. When a certificate is used for client computer authentication, this object identifier must be present in the EKU extensions of the certificate or authentication will fail.

http://technet.microsoft.com/en-us/library/cc772401%28WS.10%29.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Keith AlabasterEnterprise ArchitectCommented:
Interesting point Jakob - I thought about the use perspective but figured that if that was the case then it would have failed regardless of the nic-type over which the traffic was passing?
0
mikeydkAuthor Commented:
Looking into it
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.