Bindings in IIS on Exchange 2010 causing Test-outlookwebservices to fail on Autodiscover

Question

Exchange 2010 is coexisting with Sharepoint 2013 Foundation.
Exchange 2010 have 2 internal IP's (1 for Exchange and 1 for Sharepoint).
Under IIS we had set up binding on port 443 to 1st IP, and second IP was used to bind it to 80 port for SharePoint. That kind of configuration gave as an error for: outlookwebservices, for Autodiscover, which is logical because both IP's have an A record
which points to servername.domain.com.
This are our configuration for EWS internal/external URL's and AUTODISCOVER internal/external URL'S:
EWS URL's
InternalUrl                     :
https://mail.domain.com/ews/exchange.asmx
ExternalUrl                     :
https://mail.domain.com/ews/exchange.asmx
AUTODISCOVER URL's
InternalUrl                     :
https://mail.domain.com/autodiscover/autodiscover.xml
ExternalUrl                     :
https://mail.domain.com/autodiscover/autodiscover.xml
This are the error messages for: Test-outlookwebservices
RunspaceId : 5ee30248-5bec-436f-808a-c56180a8a6d9
Id         : 1113
Type       : Error
Message    : When contacting
https://SRVNAME.domain.com:443/autodiscover/autodiscover.xml received the error Unable to
              read data from the transport connection: An existing connection was forcibly closed by the remote host.
RunspaceId : 5ee30248-5bec-436f-808a-c56180a8a6d9
Id         : 1113
Type       : Error
Message    : When contacting
https://SRVNAME.domain.com:443/autodiscover/autodiscover.xml received the error An existi
             ng connection was forcibly closed by the remote host
The "workaround" solution, because Sharepoint only goes thru PORT 80 on this server was chosing bindings 443 to all the ips (then Test-Outlookwebservices goes thru), but doing that we are unable to use anything else on port 443 on that server in
the future.
I was wondering if changing InternalNLBBypassUrl in our scenario would be a possible workaround or there would be no effect on this scenario?
Set-WebServicesVirtualDirectory -Identity "Contoso\EWS*" -InternalNLBBypassUrl
https://mail.domain.com/ews/exchange.asmx
With best regards,
bostjanc

Answer 1

Hi Bostjan,
This was working fine before, Is it the first time we are facing the problem.
Make sure that all the exchange services are started.
Did you select the proper certificate at the Organization level and check the permission settings.
For the Autodiscover, please access
https://localhost/Autodiscover/Autodiscover.xml on the CAS. The 600 error code will be displayed.
Try to find the Error by running the Below cmdlets.
Get-ExchangeCertificate | FL
Get-WebServicesVirtualDirectory –Server ServerName | FL
Get-AutodiscoverVirtualDirectory –Server ServerName | FL
Get-ClientAccessServer 
| FL 
Than press Ctrl+right click the Outlook icon in the System Tray, select Test E-mail AutoConfiguration, uncheck Use Guessmart and Secure Guessmart Authentication, click Test button.
If found the problem is related to web services and basic authentication than try with the below cmdlet and the
Link
Set-WebServicesVirtualDirectory -identity "BOXEDUC-EXC1\EWS (Default Web Site)" -externalurl https://mail.domain.com/ews/exchange.asmx -internalurl https://mail.domain.com/ews/exchange.asmx -BasicAuthentication:$True
Mark as Answer/Helpful Post if it helps
Regards.
Naren Neelam, Messaging Consultant, ITBigBang (P) Ltd Www.ITBigBang.Com | Hire Us for Messaging Consulting