Before putting our Exchange 2013 server into production, I am testing a few things using a modified hosts file on a Windows 7 PC.
One of the issues I have is Lync 2013 constantly prompts for Exchange credentials, which are never accepted. Looking at the Lync configuration, both the Internal and External EWS paths are not filled out. So I decided to right click on the Outlook 2013 icon and test email autodiscover internally. I get constant password prompts and I can never get past this, even putting in the correct credentials. Therefore testing autodiscover fails.
In my hosts file I have the new Exchange 2013 server IP's in there for autodiscover.
Once everything is working, I will eliminate these lines from the hosts file and then swap the IP's in DNS for webmail, mail and autodiscover.
On Exchange under the Autodiscover application just Windows Authentication was enabled. I also tried Anonymous Authentication and Basic Authentication and after an iisreset later, I still have the same problem.
I found a post about this issue between Lync 2013 and Exchange 2010 and the solution was to do a Set-AutodiscoverVirtualDirectory but when I try that on my Exchange 2013 powershell as administrator, I get "A parameter cannot be found that matches parameter name 'InternalUrl'. It seems this command does not work in 2013.
Modified hosts file for the internal test contains this line, and using PING by these names, it is returning the correct IP address:
10.1.1.10mail mail.domain.com autodiscover autodiscover.domain.com webmail webmail.domain.com
A trusted wildcard cert *.domain.com is on the Exchange server.
Any help is greatly appreciated.