I have FE/BE exchange 2003 setup, and I am trying to implement RPC over HTTPS. The following are my server details: BackEnd: NetBIOS: DADSRV Domain: domain.local FQDN: mail.domain.com FrontEnd NetBIOS: DADWEBMAIL Domain: domain.local FQDN: webmail.domain.com SSL Certificate from 3rd party (GeoTrust): CN = webmail.domain.local O = webmail.domain.com Setup Configuration details: Backend: RPC-HTTP as BackEnd FrontEnd: RPC-HTTP as FrontEnd IIS - RPC Properties - Authentication Method: Basic Authentication (checked) Domain: domain.local (selected from list) Secure Communication: Required SSl -- 128 bit Outlook 2003 Exchange proxy settings: URL: https://webmail.domain.com Principle: msstd:webmail.domain.com Authentication: Basic Now is there any conflicts in FQDN of the SSL cert (webmail.domain.com) and the FE server(DADWEBMAIL.domain.local). OWA is working perfectly. Also I cannot have a HTTPS connection internally to webmail.domain.com, but when i change outlook setting to mail.domain.com, I can connect to the server via TCP/IP connection, not HTTPS. www.testexchangeconnectivity.com show a failure at the last stage, the IIS authentication, after passing the SSL certificate and the SSL port 443. Please put some light on what mistake I am making, it is frustrating Thank you.

Hi, I think that the certificate is incorrect on the FE server. You should have webmail.domain.com in the Common Name (CN) instead of Organization (O) To check certificate issue, you can access the following URL on the problem Client: https://webmail.domain.com/rpc/rpcproxy.dll If any certificate warning is received, it indicated a certificate issue. Mike

Sorry for Replying So late. I had fix the problem, it kindaf weird, my bad. At the time of authentication, we need to add the local domain name to get the access successful. So it would be : Username: domain.local\username Password: <password> So this was my mistake, as i was using FQDN: Username: domain.com\username Password: <password> Which wont work.