Hi guys,

We have just 'beaten' our Lync installation until it decided to work with mobility, however the clients (IOS) complain that it "Can't connect to Exchange Web Server". Entirely possible its our own fault!

 

My question is:

What exactly do I need to configure to make this work?

DNS records,

Firewall rules,

etc. 

We are running:

Exchange 2010 on-premise

TMG 2010

 

Cheers

Dave

As far as I am aware Lync requires the outlook autodiscover service to be published, and EWS (exchange web services) as this is where it downloads the calender content.

Running https://www.testexchangeconnectivity.com/ will point you in a good direction with what is wrong with you exchange publishing.

Also the TechNet article on publishing exchange via TMG http://www.microsoft.com/download/en/confirmation.aspx?displaylang=en&id=8946

 

Hi

Exchange Web Services synchronization, notification, availability, and Automatic Replies

Tested OK

Attempting to test potential Autodiscover URL https://<DomainName>/AutoDiscover/AutoDiscover.xml

Failed

but

https://autodiscover.<DomainName>/AutoDiscover/AutoDiscover.xml

Tested OK

Anymore clues?

 

Dave

Hi Dave,

Can you try following;

• Hold control key and right click on Lync client.
• Select configuration information and verify following URL.

Make sure that above URL is working and valid .

 

Thanks

Saleesh

 

 

Hi Saleesh,

This seems promising, both URLs are blank (and the Sharepoint Search Center URL as well. We do run Sharepoint).

 

How do I fix this?

 

Dave

Running the command from exchange management shell will allow you to check what your EWS (exchange web services) URL's are set as.

 

Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

 

 

 

you need to setup an SRV record that points to your EWS service port on your Exchange server.  That'll light up your EWS settings in LYNC.

I think, per my memory ... it's like this.  You need this record in there.  Without it, your EWS won't work - and things work way better with it there.

Service:  _autodiscover
    Protocol: _tcp
    Port  Number: 443
    Host:  mail.cocompany.net

Already done, and has been since day one of our Exchange install

 

Anything else?

Dave

So, the EWS service is located at:

https://exchange/ews/exchange.asmx

Can you access that?  You will be redirected to a wsdl page where you can view XML.

This is the EWS stuff and not nessesarily the "autodiscover" that you're looking for.  The SRV record points the client to look at port 443 on the exchange server for the /ews/ information.   See if you can access /ews/exchange.asmx on the FQDN that yo uhave the SRV record pointint to.

If you can't ... then youre issue is with EWS on the Exchange and NOT on Lync.  Check it.

Hi Dave,

The Lync 2010 mobile client for iPhone and iPad has a Meeting tab that lists meetings for the day from the Exchange calendar. The client uses simple Exchange Autodiscover processes to determine the location of the Exchange server of the user who is signed in. The SIP Uniform Resource Identifier (URI) of the user is used in the attempt to discover the Exchange Web Services (EWS) endpoint. However, if the user’s SIP URI and email address are different, the Autodiscover process will fail, the Meeting tab will be blank, and Exchange Unified Messaging (UM) voicemail in the Phone tab will not sync.

For disjointed email and SIP URIs, the Lync 2010 mobile client for iPhone and iPad lets the user specify a different set of credentials for Exchange integration. For the Exchange Autodiscover process to work correctly, the necessary DNS records must be available. To confirm that Autodiscover is working, use Microsoft Remote Connectivity Analzyer at http://www.testexchangeconnectivity.com (http://www.testexchangeconnectivity.com/) .

In addition, please also refer to this document Lync 2010 Integration. Hope helps.

Hi Greg,

I was redirected to the wsdl page, so i guess EWS is fine.

 

Any more thoughts?

Cheers

Dave

 

Hi Noya

My sip URI and email address are the same and as per my last post (replying to Greg) I can access the EWS service.

 

As per my 2nd post to this thread, I have used the Remote Connectivity Analzyer and everything checked out fine.

 

Any other ideas?

 

Dave

I'm in the same boat, have you found anything to resolve this? There isn't too much info on what is actually required.

 

Thanks

Hi

Unfortunately not. A nice authorititive guide detailing the steps required would be nice!

*cough*

....hint hint dear MS

If I do get this working, I'll update the thread.

Dave

I have the same problem--Lync on iPhone/iPad give the error "Can't connect to Exchange Web Server".  My e-mail addresses also match my SIP uri's, although my domain doesn't point directly to the Exchange server.  For example, an e-mail address would be name@domain.com, but my Exchange server is externally name mail.domain.com.  Autodiscover points to mail.domain.com, and the Exchange connectivity test works.  From the Lync mobile logs (impossible for me to understand) it seems Lync is trying to connect to various URLs, some with correct credentials, and some with no credentials.  Maybe a bug in Lync mobile?

Are you using a public certificate for your exchange services? autodiscover and ews?

Hi,

Yes they are all public certificates

 

Dave

 

How is TMG configured for Autodiscover and EWS?

Hi,

In what way should they be configured. The tests from:

 https://www.testexchangeconnectivity.com/

as I mentioned earlier in this thread report everything is ok

Dave

 

I am beginning to get the feeling that this is a Mobile Client issue, quite a few similar posts around the same issue, which, needless to say, we are also experiencing.

EWS checks out fine internally and externally from all sorts of different clients (laptops, macs) but the iPad's claim they can't connect to the Exchange Web Server.

http://social.technet.microsoft.com/Forums/en-US/ocsmobility/thread/fa942c70-b7cf-45aa-b50f-3219eeb6f98e

Hi,

Feedback to everyone watching this thread.

I have had no success at all getting the mobile client connecting to EWS since initial implementation. All remote test for connectivity to EWS report back fine. Test are run from the Microsoft Remote Connectivity Analzyer

Either this is :

a) A bug

b) We have misconfigured something, but the documentation is very light!

Sorry I can't give a more positive result to this guys.

Dave

I have been troubleshooting remote Lync IPhone connectivity for a while. My IPhone Lync Client logs show that the /ews/exchange.asmx access is on the InternalURL value and not the ExternalURL value. I have checked the URL settings using:

Get-WebServicesVirtualDirectory |fl identity,internalurl,externalurl

And these appropriately show the correct URLs are set. I have even gone as far to make InternalURL and ExternalURL values both my External URL value. And still no success, I see the internal URL in the logs still.

I have done extensive searching on this and have not found an answer. If you enable the Logging on the client, are you seeing your internal URL in the /ews/exchange.asmx entries?

Mike

Curiously - is the FQDN in the SRV record in the same domain as your sip domain?  For example, if your sip domain is me@woodstock.com is your SRV record pointing to exchange.snoopy.com or is it pointing to exchange.woodstock.com?

My SIP domain and public server names are all in same domain.com environment. The Internal Lync FE server and Exchange Server are on an internal domain.int domain.

Public Domain -> FW -> TMG Forefront Reverse Proxy-> FW -> Internal Domain

exchange.domain.com Translates through TMG Reverse Proxy to servername.domain.int

lyncdiscover.domain.com Translates through TMG Reverse Proxy to lyncserver.domain.int.

I am expecting from Public domain view to see https://exchange.domain.com/ews/exchange.asmx, but in the Lync IPhone log I am seeing https://servername.domain.int/ews/exchange.asmx.

Thanks, Mike

Despite having the autodiscover DNS entry there and working, I could not get the Lync EWS/calendar information to work without putting the SRV record in place.  After I did that, it worked great.

Lync = convoluted for sure.

I am facing the same problem for environment with Microsoft Lync 2010 and Exchange 2010, hence tested the above and found below error:

ErrorCode<ERRCA0017>:SubStatus<ES0001>:There is a temporary failure. Please retry later. The entire error report is listed below. Hide Report
Date: 4/24/2014 1:27:26 PM
Server: CO1MSSRCALWB03
Type: Microsoft.ApplicationServer.Caching.DataCacheException
Message: ErrorCode<ERRCA0017>:SubStatus<ES0001>:There is a temporary failure. Please retry later.
Correlation ID: 453a6940-6789-46d7-a68a-d99e5fd48807

Please help, how to resolve it and where to get easy steps to do so.

Thanks//Jewel