I'm running Exchange 2013 and I have Outlook 2010 and Outlook 2007 clients. I've been able to access PF from Outlook 2010 but not 2007. I'm using NTLM authentication with RPC over HTTPS. When I open Outlook 2007 it opens fine, however when I try to access public folders it prompts for a username and password continuously. So if Outlook 2007 is in mail view it works fine, but when I put it on Folder List view then it prompts continuously. Any reason why only Outlook 2007 is having this issue?

Edit: It looks like Outlook 2007 will prompt for credentials no matter what view I have it on. But Outlook 2010 does not prompt for credentials a

I eliminated this issue by clearing the msExchHomePublicMDB on all Exchange 2013 mailbox databases.  I was able to do that, however, only because the customer was abandoning public folders in their upgrade.

Otherwise, I believe you're going to have to fix Outlook Anywhere access to the public folder servers.

From what I've seen in autodiscover, Outlook is using the internal FQDN of the server for mail but the external FQDN for public folders. Since I have to put the internal FQDN in the CN space on the cert, when it tries to connect to the external FQDN it messes up because the external FQDN is not in the CN. I'm trying to get Exchange to hang out only the external FQDN in autodiscover so I can just change the cert and all the names will be the same.

I'm not sure how that's happening, but I recommend that you implement split-brain DNS and these shorts of issues should go away.

unfortunately it's not a DNS issue

Hi

Please try this

Keep the Authentication with NTLM. and change the InternalHostName to CAS itself FQDN.

If that not working

Have another try to set LmCompatibilityLevel on the client to a value of 2 or 3

1. Click Start, click Run, type regedit in the Open box, and then press ENTER.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\
3. In the pane on the right side, double-click lmcompatibilitylevel.
4. In the Value data box, type a value of 2 or 3 that is appropriate for your environment, and then click OK.
5. Exit Registry Editor.
6. Restart your computer.

Hope those helps

Cheers

I had already tried the lmcompatibilityleve and that didn't fix it. What I ended up doing was setting Outlook Anywhere to use the external FQDN for both internal and external sides and that has resolved the issue. I had to reissue the cert with the external FQDN in the CN field of the cert and now the Windows XP clients are connecting.

Well, that is basically what we told you to do!