Sounds to me like your intermediate certificate expired. Are you using a third party certificate or an internal certificate?
It would help if we knew the domain so we can look at the certificate ourselves. ________________________________ From: Jay Dale [[email protected]] Sent: Friday, May 08, 2009 3:24 PM To: MS-Exchange Admin Issues Subject: RPC over HTTPS problem I'll give these boards a try, since I haven't heard much at EE regarding this problem: I use Outlook 2007 with Exchange 2003 SP2, and yesterday RPC over HTTP just stopped working all of a sudden. I started getting Security Alerts for autodiscover, pointing to myregisteredsite.com. So I changed our DNS so there were no wildcards thinking this would help. I even removed the split-DNS our server was using just to see if it made a difference, but it hasn't helped. The server is SBS Standard with SP2. I've run the Internet Connection Wizard several times, removed and replaced the Outlook profile, removed and replaced the cert, which is a 3rd party cert from GoDaddy, and I get as far as /rpcdiag showing the Directory connecting fine with HTTPS but the Mail or Public Folders not showing up at all. I can pull up OWA without any cert errors. All of my registry entries are correct. As I mentioned, everything was working fine for almost a year, then it just stopped this past Monday. Nothing on the server has changed, nothing on my Outlook has changed - just whammo. On the test site, I'm assuming I'm using the Outlook 2003 test even though I'm using Outlook 2007 because I'm not using Exchange 2007? It fails pinging 6001, even though the registry entries are correct under the Rpcproxy key. When I do the same launch of Outlook 2007 from my home PC, with the exact same setup, it prompts for a username and password, meaning it's actually contacting the Virtual folders in IIS I'm assuming? Once I log in, it just shows as Disconnected down at the bottom. Again, RPCDIAG shows 4 or 5 connections to Directory as HTTPS, but no Mail or Public Folder connections. Upon testing within the environment with RPCDIAG, all connections are made but show up as TCP/IP and not HTTPS. Then I tried using www.testexchangeconnectivity.com<http://www.testexchangeconnectivity.com/> and it comes back saying it failed on the certificate, HOWEVER, the failure is not on the cert name, but on the trust, and comes back with the error "The certificate chain has errors, Chain status = PartialChain ". What could have happened to cause this mess? Thanks for any advice, Jay ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
