Ok, bear with me guys - this issue has me totally stumped.I have an SBS 2003 server SP2 running Exch 2003. For the last year I have been successfully running RPC over HTTP on it, using a Trusted cert from GoDaddy rather than the SBS-created one. Everything was working fine until last week, then all of a sudden it just stopped. When I pull up an rpcdiag, it shows the Directory connections successfully connecting with HTTPS, but no Mail or Public Folder connections whatsoever. When I test inside the network, it all uses TCP/IP.I have gone to www.testexchangeconnectivity.com and my results are as follows:Attempting to Resolve the host name mail.xpresstel.com in DNS.Host successfully ResolvedAdditional DetailsIP(s) returned: 75.148.212.33 Testing TCP Port 443 on host mail.xpresstel.com to ensure it is listening/open.The port was opened successfully. Testing SSL Certificate for validity.The SSL Certificate failed one or more certificate validation checks.Test StepsValidating certificate nameSuccessfully validated the certificate nameAdditional DetailsFound hostname mail.xpresstel.com in Certificate Subject Common name Validating certificate trustCertificate trust validation failedAdditional DetailsThe certificate chain has errors, Chain status = PartialChain I've tried removing and readding the cert - no luck.I've tried uninstalling and reinstalling RPC and then using CEICW - no luck.I've verified the permissions on the VD's in IIS - no luck.I've looked at the IIS logs and they show successful connections using ports 593, 6001 and 6002, but not 6004 - although they're all correct in the registry.I've browsed to the rpc directory from the outside and gotten the correct response of the 3 logins - no luck.I've browsed to the https: site and validated that the cert is trusted.I'm absolutely at a loss at this point. I can say that there's only one thing that changed - I tried using OpenDNS for the first time with our site. Once I started having all of this trouble I removed the network from OpenDNS, and currently it is not using any forwarders. I had split-dns at one time as well, but removed it to try and troubleshoot this problem.Any help at this point would be great. Thanks!

*tap tap* is this thing on?Anybody got any suggestions?

Hi,Can we send/recieve email from internent via OWA or Outlook?Is there any MX record and A record on Internet DNS?Please ensure that you have a valid SSL certificate from a trusted certification authority (CA). Please try to use https://fully.qualified.domain.name/RPC/rpcproxy.dll to check if you will have a Security Alert, if yes,then I think it could be a certificate related issue.Besides,please try to configure outlook anywhere outside and then send/recieve email,post the error informaiton here for furhter troubleshooting.How does Outlook Anywhere work (and not work)? http://msexchangeteam.com/archive/2008/06/20/449053.aspxHow can I configure RPC over HTTP/S on Exchange 2003 (single server scenario)?http://www.petri.co.il/how-can-i-configure-rpc-over-https-on-exchange-2003-single-server-scenario.htmTroubleshoot RPC over Httpshttp://www.msexchange.org/tutorials/Troubleshooting-RPC-over-HTTPS-Part2.htmlRegards,Xiu