I'm having an issue with Windows XP and Exchange 2013. My Windows XP clients cannot access Public Folders but they can get email fine. I have the server.internaldomain.local in the CN of the cert. I was going over the autodiscover.xml from the Outlook test. I noticed that the publicfolderserver value is the server.externaldomain.com name and not the internet name. I'm wondering how I can go about changing that? I'm pretty sure it would help alleviate

You really ought to be getting off of Windows XP.

Run:

Get-WebServicesVirtualDirectory -Server <public folder server name> | fl ExternalUrl

Is that set to the correct value for external access?

Oh I'd love for them to be off Windows XP but it's not in my power at the moment. That is set to the correct value for external access yes.

This is the part of the autodiscover that I'm referring to. Instead of publicfolderserver showing the external name it should show the internal name. At least that's what it does on several Exchange 2010 servers I've checked.

@externaldomain.com/cn=Microsoft Private MDB</MdbDN>
        <PublicFolderServer>mobile.externaldomain.com</PublicFolderServ

Are the two servers in the same Active Directory site?

What two servers? I'm only talking about one server.

Edit: I've resolved the

What two servers? I'm only talking about one server.

Edit: I've resolved the issue. Since I was not able to change the publicfolderserver value in Autodiscover I had to change Outlook Anywhere to hand out the external FQDN for both internal and external sides. This allowed the Windows XP clients to access

It's not good form to mark your response as an answer without providing the answer.

I did provide the answer