Website Security Certificates with RWW and RPC over HTTP.
Posted on 2008-11-14
No matter how hard I try or read, there seems to be one area about the Internet or networking that I just can't seem to understand. I really need some step by step help.
I continue to have problems with website security certificates which I think are keeping me from doing certain things. I am having trouble getting Outlook to connect to Exchange Server via RPC over HTTP. I have decided not to do any more troubleshooting until I can rule out the certificate error. Since, when I use RWW from home, I have to click through the certificate error by clicking on "Continue to this website (not recommended)" I am guessing that Outlook can't do that on its own.
So....there are two areas I have questions on. One is on the server and one is on my browser at home. When I ran CEICW for the first time, I allowed SBS to make its own certificate for SSL. I did not purchase one. So far, that has worked, and I have been able to get to Exchange with no issues I believe. Is it better to purchase a certificate from GoDaddy? What would be the advantage? And, does that certificate have anything to do with connecting error free for RWW via 443 or for RPC over HTTP for that matter?
And as to my client computer at home. I continue to click through the warning which brings me to the first page of RWW. But, the certificate error says Mismatched Address. I am able to left click there, choose View Certificate and then install it. It may allow me to access RWW once without the error, but eventually the error comes back. Would purchasing a certificate or using a trial certificate work? And, if I do just use the certificate provided, is installing it to the default location as good as choosing one of the Trusted Folders?
Again, my main goal here is to understand these certificates and set them up so I can RWW without the certificate error.