Outlook Anywhere setup where local domain is same as company domain

I have just migrated a SBS 2003 domain to SBS 2008. The previous IT guy set up the network so the local domain is the same as the company domain (so company.com.au not company.local). Everything works except Outlook Anywhere. When I run Exchange BPA it reports that there is a certificate mismatch. Now I am using a 3rd party certificate linked to the external FQDN of the SBS Server. RWW and OWA work fine. But the detail of the Exchange BPA says that the principal name is set to domain.com.au not office.domain.com.au. I have used the Exchange Management Shell to update the principal name as suggested by the BPA but this has made no difference.

So any suggestions on how to fix this situation?

Regards,
Ben
muaddib32Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PlusITCommented:
yes the behaviour of outlook anywhere changed in 2008.  The mismatch error on the SSL certificate is because teh client first tries to connect to autodiscover.domain before connecting to the outlook anywhere FQDN.

There are different solutions to this:
- use a self signed certificate that you trust on your domain (all pc's using outlook any should be in the domain!)
- use a 600$ ssl certificate which supports multiple cn's
- use one host to connect and change DNS settings according to KB940881 (this is what i do) this makes sure it works with a single cn ssl cert.

If you need further assistance just let me know but i'm sure with the information i just gave you you'll find it out.  Make sure you write this so you understand how the new behaviour is: http://technet.microsoft.com/en-us/library/bb232838.aspx
0
muaddib32Author Commented:
This is the third SBS2008 server I have configured. I have not configured autodiscover on the other two and yet Outlook Anywhere works fine on them.  If your theory is correct, shouldn't it fail on the other two also?

And the Outlook 2003 RPC/HTTP test at https://www.testexchangeconnectivity.com/ fails and that is not using Autodiscover.

Are you sure that Autodiscover is the problem?
0
PlusITCommented:
yes and no, it shoudn't fail if you are using self signed ceritifcates and those computers are domain joined, if the cert is domain wide trusted you dont get ssl errors.

You said it yourself you are using a third party ssl cert, can you check how many CN fields it has?  If it only has one CN field then you will have to go around this problem with the info provided on KB940881
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

muaddib32Author Commented:
After further tests is has become apparent that the error message I am getting about the mismatched principal name is a red herring.  The step that is failing is the authentication at the TS Gateway.  RWW and TS services are failing as well as Outlook Anywhere.  Apparently this is commonly caused by the authentication settings for the RCP website being modified. But not this time! I have Microsoft PSS on the case but they are puzzled too.
0
PlusITCommented:
my english is not that good, what do you mean with a red herring?

btw is their an ISA server between it or any other web proxy?
0
muaddib32Author Commented:
Red herring just means a clue that leads in the wrong direction. So I don't think my problem has anything to do with the mismatched principal name. I can access other SSL sites without any problem - OWA, Sharepoint (through port 987)

No, no ISA server. That is not included with SBS 2008 Premium.
0
PlusITCommented:
yes but arent you accessing those with a domain joined computer, have you tried with a computer that is out of the domain to see if you get a cert warning then?
0
muaddib32Author Commented:
I have only been testing it with non-domain computers. Without any problems with the certificate. As expected, since it is a third-party certificate.
0
muaddib32Author Commented:
Please close this question as I still have the problem and no-one seems to have any suggestions. No points awarded.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.