Dmitry,
Any chance that you can explain the reason w2k3 white papers told me to
raise the functinoal level to 2003? I think that is the only difference
between my 2 setups, and the 2003 way it never prompted, it just
automatically verified the cert, where now it can't verify it automatically.
We are just trying this method, and want it to be quicker and easier then
the ones our Linux guys are testing.
Open the certificates console for your user and check Trusted Root
Certification Authorities store. Is there a certificate of your Enterprise
Root CA? It should be, if your workstation is connected to the same forest
where CA is installed. If not, just install it manually or using GP.
--
Dmitry Korolyov [
[email protected]]
MVP: Windows Server - Active Directory
Dmitry,
I set this up in a w2k3 test env, followed teh white papers, raise the
domain functional level to 2003 (not sure why but white papers said to, and
the wireless worked like a charm, never prompted to trust cert.
Now that I moved it into my 2k AD, it doesn't seem to trust the cert. We
want a wireless user to just have it authenticate their domain\user and pwd.
Can you shed any light on this?
Thanks again,
Jeff
Place the root CA's cert in Truster Certification Authorities store on your
client computer. This should automatically ensure trust to all downlevel
certificates issued by this CA.
--
Dmitry Korolyov [
[email protected]]
MVP: Windows Server - Active Directory
We have a problem with wireless authentication. I have a CA setup on a
member server w2k3, IAS on another member server w2k3 (with a cert from the
CA), in an active directory native mode 2000. The access point is cisco.
We can connect and authenticate properly, however it prompts us to ask if we
trust the certificate. If we don't click yes quickly, it will fail.
Any ideas on how to automatically trust and verify the cert, or how to
increase the timeout (now about 2 seconds).
Thanks in advance
