Hello All, I know this issue has come about a lot, but I cannot get it fixed so I hope somebody can shed some light on it for me. Background: SBS Server 2008 running Exchange 2007 Self Certified Certificate installed on server and exchange "remote.abc.co.uk" Outlook 2003 Clients OK Outlook 2007 Clients are first getting a popup asking for their password which does not work so you have to click on cancel then a security warning is displayed with an x displaying "The name of the security certificate is invalid or does not match the name of the site" The name on our certificate is "remote.abc.co.uk" The name on the top of the above security warning is showing as "AutoDiscover.abc.co.uk" which is guessing why it is failing because our certificate is "remote.abc.co.uk" Things Tried: Article http://support.microsoft.com/kb/981954 which changes the InternalURL in Exchange, this has not fixed it, I have made all the changes and then restarted the pool, still no luck We cannot buy a valid ssl cert due to budgets All updates and SP applied to both SBS 2008 and Exchange 2007 We have setup a few SBS boxes with self-certified certs and never had this problem. Please Help Thank You In Advance

A commercial certificate will cost $60 from certificatesforexchange.com. That will probably resolve a lot of your issues. I don't know how much you are paid, but for most people that is a lot less than the hours you have been spending on this issue. If you have been searching for commercial certificates then you will have seen Verisign's high prices. No need to pay those. I have instructions on how to configure SBS with a certificate on my blog here: http://blog.sembee.co.uk/post/SBS-2008-Certificate-Installation.aspx Did you configure the SBS server using the wizards? If not, then that can cause problems. Outlook will attempt to connect to autodiscover.example.com (where example.com is your public domain name) so you need to ensure that does NOT resolve to a valid host. Many web hosts will put a wildcard in to the domain so that anything.example.com will resolve - that needs to be removed. The reason your credentials fail is because it isn't Exchange, but a public server that you are most likely connecting to. Correct the DNS, with autodiscover pointing to the SBS Server, put in a commercial certificate. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources

Hello, Thanks for the response, I would like to avoid paying for a cert as this company is a small charity. However I did find the answer, I will try and explain the best I can. please watch this space and I will write it up :)

My problem was as follows: I have SBS 2008 which has obviously has local DNS with the Primary Zones “abc.local” and “remote.abc.co.uk” When on a LOCAL client machine and I pinged AutoDiscover.abc.co.uk (this is the address that was displayed at the top of the security warning) it was replying with an address. This is strange because I never setup an A record on our external DNS for that, I then pinged “sdfsdsd.abc.co.uk” and that also replied with the same IP which made no sense. I then found out that our external DNS provider have some weird thing with DNS so they always re-direct any A record to their web servers. So what was happening is Outlook was finding a web server on “AutoDiscover.abc.co.uk” and also finding that it was enabled for SSL thus displaying a certificate (from the DNS providers). This did not match the one on the server so failed. I fixed it by adding a Primary DNS zone on our SBS DNS called “abc.co.uk” and then flushed the dns on the client and then pinged “autodiscover.dentsecurity.co.uk” presto it did not reply or get an address, restarted Outlook and no Security warnings, however the login box was still getting prompted so I installed Exchaneg 2007 SP3 and that fixed that. Job Done, Thanks to www.BrightVisions.co.uk who helped me with this one. I know this should have not been overlooked but I hope that helps somebody.