Hi 

I had several attempts to connect into my Lync 2013 server via mobile (Android, iPhone). The error message: "An error occured in Lync. Please retry. If the problem persists, contact your support team" I know its not much information even tho I tried to send the logs over but sadly they were blank.

My environment setup is as such, 

 - Two split domains contoso.local and contoso.com (internal and external dns zones) 

 - I have added all required DNS entries to the DNS server and the alternative subject names for the generated SSL.

 - The pool names are different for internal and external link (external: felync.contoso.com)

 - The certificate subject name holds the server name(contoso-lync.contoso.local)

 - DNS Names are as below: (autodiscover.contoso.com, autodiscoverinternal.contoso.com, contoso-Lync.contoso.local, felync.contoso.com)

 - I had a CNAME records pointing from contoso.com to contoso.local, even replacing them with A records didnt help

 - I am trying to connect vai WLan such as, email address: allias@contoso.com, login: contoso\username. 

 - No TMG implementation in the environment, I understand the purpose would be for remote external access 

Previously, lync was notifying me "Lync is attempting to redirect you to: contoso-lync.contoso.local" then throws the same earlier error message.

Hi

TMG is for a few of features of remote external access. If you want to deploy Lync mobility for both internal and external, TMG must to be deployed. If the mobility services are to be restricted to internal mobile clients only, TMG is not required but you have to set the value of ExposedWebUrl to Internal using Set-CsMcxConfiguration. Here is a great blog deploy Lync mobility:

http://blog.schertz.name/2011/12/deploying-the-lync-2010-mobility-service/

Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

Hi Kent-Huang,

Thanks for your quick response, I actually came across a blog suggesting to run "Set-CsMcxConfiguration" and set the Exposed Url to Internal after posting my question.

'http://social.technet.microsoft.com/Forums/en-US/lyncprofile/thread/186f6d09-106b-46de-973c-1e658f3ee18d'

But sadly that didnt help, I still have the same issue with Lync Mobile :(

I intend to have internal access only for now, thanks for clearing my doubts about not requiring TMG server for internal use.

I also followed the blog by Elan Shudnow's 'http://www.shudnow.net/2012/03/12/using-lync-2010-mobility-on-your-corporate-wifi-networks/'

where you would enter the "https://lyncdiscoverinternal.domain.com/autodiscover/autodiscoverservice.svc/root/domain" url in the browser to view the connection details:

Current Response:

{"code":"NotFound","message":null}

Expected Response:

{AccessLocation:Internal,Root:{Links:[{"href":"https:\/\/InternalWeb.domain.com\/Autodiscover\/AutodiscoverService.svc\/root\/domain","token":"Domain"},{"href":"https:\/\/InternalWeb.domain.com\/Autodiscover\/AutodiscoverService.svc\/root\/user","token":"User"},{"href":"https:\/\/InternalWeb\/Autodiscover\/AutodiscoverService.svc\/root\/oauth\/user","token":"OAuth"}]}}

I suspect that would be the cause? or maybe not?

Many thanks

Try wync on the app store. It may work for you.

You can also see it at www.wync.me

Thanks for your suggesting for using WYNC, I haven't had the chance to try using mobility on iPhone yet because my main handset is an Android phone. But I am sure it would work because I have downloaded Lync 2010 for Android and I was able to connect successfully.

Seems that Lync 2013 for Android has some extra requirements that I can't realize what it could be, for the past 4 days I have been investigating the issue but didn't come across the resolution yet.

Just for the records to other users to import your internal certificate into your Android phone you would require to export the certificate as a .pfx including your private key, otherwise no luck to do so via a .cer or .cert format even tho a notification of successful certificate import was made but when you check the certificate collection it won't be listed. 

I came across this post that had a similar error message as mine but not identical as its involving Lync 2013 + Office 365 communication.

http://silbers.net/blog/2013/03/12/lync-on-premise-mobility-configuration-can-cause-issues-with-lync-online-o365-meetings/

 My next debuging steps is to deploy a TMG server and take it from there.

Hi,

I am glad to hear Lync 2010 for Android is successful. Have you applied the latest version of update for Lync Server?

You can try to use Lync Connectivity Analyzer for further troubleshooting. For details:

http://blogs.technet.com/b/nexthop/archive/2013/03/13/lync-2013-mobile-clients-release-faq.aspx

http://technet.microsoft.com/en-us/library/jj907302.aspx

Hi,

After installing Lync 2013 I ran windows update which I believe it did update the Lync instance, I tried downloading the CU for Lync to run it manually and all the boxes were ticked as green which meant Lync is upto date. To eliminate this doubt I even ran the backend database steps which you would usually execute after applying the CU manually but no luck with that.

I used the Analyzer tool and it reported that my configuration meets the minimum requirements for Lync mobile apps, except when I click on show detailed results I could see duplicate messages as below:

 1. 'Failed to obtain the WS-Metadata Exchange (MEX) document using POST for https://Contoso-Lync.Contoso.local/Mcx/McxServices.svc/mex. The service did not require authorization.' under tests for Mobility (MCX) service

I tested the link by pasting it into the browser and I could see the xml data.

Ok finally I got Lync 2013 mobility working on Android, iPhone and Windows 8 mobile. In the end I had to setup a TMG2010 server and deploy a HTTPS listener and HTTPS web hosting.

After going through the hassle of figuring out what is the requirement for getting the Mobility working. If you take a second look on this link from microsoft Technical Requirements for Mobility you could see that external link of Lync 2013 is pointing to reverse proxy.