I am getting the following autodiscover error Id : 1013 Type : Error Message : When contacting https://**internal server FQDN**/autodiscover/autodiscover.xml received the error The remote server returned an error: (404) Not Found. I attempt to navigate to the file with a browser and I get a 404 error as well. I checked the permissions on the file and they were only set for authenticated users (which is what I expect to access it anyway, but I added everyone read as well.) Does anyone have any idea how to fix this issue?

What version of Exchange are you running? You probably just need to reset your virtual directory in exchange, you can do this through the shell: set-ClientAccessServer -Identity Servername -AutodiscoverServiceInternalUri https://owa.domain.com/autodiscover.autodiscover.xml updating the appopriate fields with your values. You shouldn't mess with the default NTFS permissions, the default should be 'Autenticated users - Read, Read & Execute' 'system - full' 'Administrators - Full'. But instead check within IIS and look at Authentication under the Autodisover Virtual Directory, make sure the following are enabled: - Anonymous Autentication - Basic Authentication - Windows Authentication Jorge R. Diaz, PMP, CCNA, MCSA, MCSE, MCTS Senior Microsoft Consultant Planet Technologies, Inc. Check out My Blog!

The ClientAccessServer is set correctly. I did check the Authentication options under the VD and enabled the anonymous connections, after which I did an iisreset, but I still get the error when I test-outlookwebservices. I am running Windows Server 2008 SBS with built in Exchange.

Did you by chance disable IPv6? Jorge R. Diaz, PMP, CCNA, MCSA, MCSE, MCTS Senior Microsoft Consultant Planet Technologies, Inc. Check out My Blog!

Yes I have, would re-enabling it work?

Well, it depends on how you disabled it. If you just unchecked the IPv6 box in your NIC properties then yes it will break many things on your system, more than just your autodiscover. If you want to properly disable it you need to change a setting in the regisry and reboot, then uncheck IPv6. I'd recommend turning IPv6 back on. It can't hurt anything and doesn't require any additional configuration at this point. Go ahead and re-enable, then reboot and test again for me and let me know what happens. Thanks, Jorge R. Diaz, PMP, CCNA, MCSA, MCSE, MCTS Senior Microsoft Consultant Planet Technologies, Inc. Check out My Blog!

Thanks, a reboot will have to wait until this evening, I will let you know how it goes tomorrow.

Sounds good, I am assuming you hadn't done the registry setting so yeah, this should fix the problem, and future problems you probably haven't seen yet ;) Jorge R. Diaz, PMP, CCNA, MCSA, MCSE, MCTS Senior Microsoft Consultant Planet Technologies, Inc. Check out My Blog!

I re-enabled IPv6 and rebooted the server, but I am still getting the error.