Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.
SSL Error in Exchange System Manager (ID no: c103b404)
I am receiving an SSL error when trying to view Public Folders in the Exchange System Manager, the error ID number is c103b404. My servers name is MUNKA and the DNS suffex is RWJD.local but my domain name used for OWA is https://munka.rwjd.net/Exchange (check it, it works). The SSL certificate is generated just fine and it works great. I've already read over http://support.microsoft.com/default.aspx?scid=kb;en-us;324345 but that doesn't help me any because the FQDN is MUNKA.RWJD.local but the SSL certificate is for a "real" domain munka.rwjd.net; how can I get this to work properly?
I have already reviewed several other of the same questions about this issue but all of the answers are pointing at http://support.microsoft.com/default.aspx?scid=kb;en-us;324345 which does not resolve the problem.
Please help me. I am making this worth 500 points since it seems to be quite a difficult issue that nobody has resolved yet.
I have already reviewed several other of the same questions about this issue but all of the answers are pointing at http://support.microsoft.com/default.aspx?scid=kb;en-us;324345 which does not resolve the problem.
Please help me. I am making this worth 500 points since it seems to be quite a difficult issue that nobody has resolved yet.
Asked:
3- +1
1 Solution
Don't confuse the setting to require SSL and being able to use SSL. You don't need to have require SSL on to use SSL.
If you don't want to send usernames and password across in the clear when users access public folders through OWA, then you would use an SSL secured site. If you want to ensure that they can't use http, then simply block port 80 on the firewall. As long as port 80 access is available inside then everything will work correctly.
ESM uses the OWA interface for public folders when managing it - which is why you changed the setting in IIS Manager.
Simon.
If you don't want to send usernames and password across in the clear when users access public folders through OWA, then you would use an SSL secured site. If you want to ensure that they can't use http, then simply block port 80 on the firewall. As long as port 80 access is available inside then everything will work correctly.
ESM uses the OWA interface for public folders when managing it - which is why you changed the setting in IIS Manager.
Simon.
mstumpo - this is an old question. Unlike a forum it is not possible to "bump" questions back up the list. The only people who will see your post are those that have already participated. Instead you should post your question as a new question in the Exchange Server Zone which will allow other experts the chance to see the question and respond.
Simon
Exchange Server Zone Advisor.
Simon
Exchange Server Zone Advisor.
For me, the above solution was not sufficient, but when I implemented this: http://www.isi.cc/jmcalister/Lists/Posts/Post.aspx?ID=43 it worked.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.
One of a set of tools we're offering as a way to say thank you for being a part of the community.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
If so, remove it.
Simon.