Outlook Authentication Issue

[Cytrine]

thread1582-1503709

I have the exact problem that was posted under thread1582-1503709.

The individual that originally posted this question worked with Microsoft to resolve his problem and he stated that he would provide the details to everyone else once he received the detail from Microsoft. The thread is now closed, and nothing more was posted so I am hoping that someone will be able to provide me with the information so that I can resolve the problem on my server as well.

Thank you in advance for any help that you can provide!

 

[ShackDaddy]

At what stage in the thread you mention have you arrived?

In my experience, this is what's been important:

1. *** Use a public SAN/UCC cert that includes the following:
- the full external FQDN users will use for OWA and OA (make this the common name on the cert!)
- autodiscover.yourdomain.com
- the internal netbios name of your CAS server (like exchange01)
- the internal FQDN of your CAS server (like exchange01.domain.local)
You can no longer say that public certs are too expensive to justify the cost, unless you work for free and all your software and hardware was donated... I even buy them for lab environments, since they cost as little as $11/year.

2. Make sure that when you run the Exchange Best Practices Analyzer it doesn't give you any errors about Global Catalog

3. Set Outlook Anywhere to use Basic auth, not NTLM. This tends to make a significant difference when you are working with non-domain joined workstations in the field.

4. Focus on making sure that Autodiscover works properly. Use the TestExchangeConnectivity.com site to do that. Don't worry if you get some Autodiscover errors there, since the Autodiscover process is an iterative one and tries multiple options but only needs to succeed at one of them to be effective. Also use the "Test E-Mail Autoconfiguration" tool in Outlook 2007 to help you out. Ctrl+click the Outlook icon in the systray to find that tool.

Dave Shackelford
ThirdTier.net