asked on

SSL Certificate server name incorrect ID No:c1035404

Hi there,

I get this error when I am trying to access the security permissions on our Public folders but I can't.

We have an SSL Certificate that our field staff use for Outlook Web Access.

The url that they use is https://blablabla.bla.com which is what the SSL certificate is registered with but internally if we want to access it we use https://blablabla.bla.co.uk

Any ideas?

marc_nivens

Open Internet Services Manager on the Exchange server. Expand default website, right click on the exadmin folder and go to properties. Go to directory security and open the secure communication settings. Uncheck the box that says require secure channel as well as the require 128 bit encryption. Restart the website and you should be able to get to public folders now. Check this out:

You receive an SSL Certificate error message when you view public folders in Exchange System Manager
http://support.microsoft.com/default.aspx?scid=kb;en-us;324345

ddh76

ASKER

I have done this as per the KB Article and your entry and it gives the same error.

marc_nivens

If you have multiple Exchange servers you need to do this on all of them. Also, you can check the w3svc log for more information. This log is in system32\logfiles\w3svc\1\ and will be named by date. Open the most current and search for exadmin. The entry in the log may give you more information. Other than that I'm not sure what to tell you... I've seen this many times and every time unchecking the SSL requirement has fixed it. You might want to go check it again to make sure the setting is not propagating back after you change it.

ddh76

ASKER

Yes, I have already checked that the setting stayed and it did. I only have 1 Exchange Server too. Logwise - there is nothing referring to Exadmin!

ASKER CERTIFIED SOLUTION

marc_nivens

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ddh76

ASKER

Ah yes - Excellent - the ADSI Edit worked a treat. Can you explain this?

marc_nivens

Glad to hear it! Now the explanation... certain properties in Active directory are replicated to the IIS metabase via a process called DS2MB. This replication is one way only, AD to IIS. Some settings for Exchange are set in both AD and the metabase. For these, making the change directly in the metabase may not be enough, because this change will never get updated on the AD object. In these cases you have to make the change yourself, and this was one of those cases. The msExchSecureBindings attribute tells the exadmin folder to bind to the SSL port when started, so removing this unbound SSL from that folder. Now that SSL is gone its only going to connect with port 80 which has no certificate, hence the error goes away. Clear as mud? :-)

ddh76

ASKER

No that makes sense - thanks a lot for the explanation and help generally.