none
Secure Connection

    Question

  • why is outlook telling me secure connection cannot be verified when the certificate has the right fqdn name of the exchange server

    and the ca is trusted?

    any ideas?

    Friday, July 28, 2006 3:24 PM

All replies

  • What exact error are you getting from Outlook, and what version of Outlook?  Are you connecting with an "Exchange server" type of account, or POP/IMAP?  Also, does the certificate have a subject that is the same name as you are connecting as, from Outlook?
    Saturday, July 29, 2006 6:42 AM
  • hi

    i am getting a something like "a secure connection with the server cannot be verified....."

    the server has a certificate with the exact server fqdn name

    and the Ca is trusted by the workstation

    also when i click view detailts on the certificate its listed ok so thats not the problem for sure

    outlook connects when i click YES

    http/rpc(outlook anywhere) works too if i enable it so its not a certificate issue.

    and yes

    i am connecting with outlook as exchange type account

    Tuesday, August 01, 2006 1:46 AM
  • latest version odf exchange 2007 beta 2

    and outlook 2007 beta 2

    ca is trusted

    http/rpc works if i enable it

    outlook is using exchange server account

    certificate i installed on the server has the fqdn of the server and looks fine

    clicking YES on the warning enables me to login

    warning is: "a secure connection to the server cannot be verified...." or something like that

     

    Tuesday, August 01, 2006 1:49 AM
  • Hi.

    Try again following :

    At firtst, you can remove Web Server Cert, and then create Web Server Certification (Identity Common Name of web server cert on Rpc proxy server is Common name of Root CA.).

    And, at an outlook client, download or reinstall CA Chain.

    Thank you.

    Tuesday, August 01, 2006 3:50 AM
  • as i said

    it doesnt look as ca thing

    because ca is trusted on client

    and the certificate itself looks fine(trusted from top down)

    fqdn is ok too

    simple domain

    one dc that is exchange server also

    and one client

    thats it

    owa https works without any prompts

    Tuesday, August 01, 2006 7:42 PM
  • We have had the same issue ever since rolling out Office 2007 and Exchange 2007, word from MS support is that is was a bug in Office which has been fixed in later builds. So watch this space and bare with it.

    Don't forget it is still beta :)

     

     

    Monday, August 28, 2006 2:38 PM