Hello All . I have outlook anywhere authnitication problem , it's not connect using https , it's use TCP/IP instead , I think the problem exist on the exchange certificate name , am geting this error after configuring outlook anywhere . " There is a problem with the proxy server's security certificate , the name on the security certificate is invalid or does not match the name of the target ... "I tried to create new exchange self signed certificate , and when i request the certificate through web from our CA , when i click submit i recieve this error : Your certificate request was denied. Your Request Id is 0. The disposition message is "Error Parsing Request The request subject name is invalid or too long. 0x80094001 (-2146877439)". even i type every possible DNS name in the subject name filed while am creating the certificate . Any Help Please .

Featured Links*

I take it that you are attempting to connect to a mailbox from inside the LAN? What happens when you try to connect from outside the network? What is the internal name of the exchange server? Is this name on the certificate?

Check the properties of the Outlook profile. In the Exchange HTTP Settings page, do you have both "on fast networks, connect using...." and "on slow networks, connect using..." selected??

The self generated certificate within Exchange is not supported for use with Outlook Anywhere or Exchange ActiveSync. If you want to use Outlook Anywhere then you must purchase a certificate. I have outlined the full procedure here: http://www.sembee.co.uk/archive/2008/05/30/78.aspx

Thanks alot to reply . yes I am trying to connect to a mailbox from inside my LAN , and basically i want to test from inside the LAN first , i dont try to test it externally . CAS Server name is cas.mydomain.com , and I type all the possible names inside the self signed certificate including mail.mydomain.com , cas.mydomain.com , casServerName.mydomain.com , autodiscover.mydomain.com , NetBiosCasName . Yes i did , i checked it to use HTTPS first in both cases ? what do u think about the Sembee post ??????Wait your reply . Bye Bye

What has that got to do with things? That is referring to Wildcard certificates. I made the point that self generated certificates are not supported. Making that post reminded me of an unpublished blog posting, which I have now blogged: http://www.sembee.co.uk/archive/2008/10/16/87.aspx

When I saw this thread I was pretty disheartened. I wanted to use our internal certificate authority to generate the Subject Alternative Name Web certificate. After maybe the 8th iteration of generating the requests I got it. Here was steps:

When I saw this thread I was pretty disheartened. I wanted to use our internal certificate authority to generate the Subject Alternative Name Web certificate. After maybe the 8th iteration of generating the requests I got it. Here was steps: