Some Lync Clients Unable to Connect

Hello,

I am in the process of deploying Lync 2013 to our environment. Internally, client connections are fine. Externally, our Windows 7 laptops with Office 2013 can connect and the clients for Office for Mac 2011 can connect. The Lync 2013 client will not connect on any smartphone or tablet, be it ipad, windows phone 8, android etc.

Can anyone help me figure out what this could be?

The error that is reported is "Cant connect to the server. It may be busy or temporarily unavailable."
LVL 1
AshleySPMAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mohammed HamadaSenior IT ConsultantCommented:
What reverse proxy are you using for Lync mobility?
Clients mechanism for connecting with Lync varies from Desktop to tablets and smartphones.

Desktop Client connects to the edge server from the internet while Tablet and smartphones have to connect to reverse proxy to authenticate with Lync FE and Edge.

If you don't have RP, you will have to deploy one and configure it properly with Lync.

IIS ARR (Application Request Routing) is the most common and free choice that people deploy for small/medium organizations.

There are some deployment documentation on how to do so ..follow this one if you may.
http://y0av.me/2013/07/22/lync2013_iisarr/
0
Jeff_SchertzCommented:
Most likely you do not have Autodiscover configured correctly for your reverse proxy to the Internet.  Take a look at the articles in this link for more details on how the various Lync client perform autodiscovery tasks (as the process vary between the Windows, Mac, and Mobile clients).

http://blog.schertz.name/tag/autodiscover/
0
AshleySPMAuthor Commented:
I apologize for the delayed response - I didn't see the emails that there were responses. I think I have Autodiscover correctly deployed. I have been using the Lync connectivity analyzer and all the server discovery works. This is the error I get in the "Starting Requirement tests for Lync Mobile 2013 App":


Starting tests for Mobility (UCWA) service
Verifying internal Ucwa service: https://internalurl.company.com/ucwa/v1/applications
Successfully created the UCWA service
Completed tests for Mobility (UCWA) service

Verification failed for Mobility (UCWA) service. The service could not be reached from an external network.

Your deployment meets the minimum requirements for Lync Mobile 2013 App.



My mobile devices still can't connect though so it's definitely still broken.

Any help would be much appreciated and I will keep an eye on the thread so the responses don't take forever.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Mohammed HamadaSenior IT ConsultantCommented:
What reverse proxy are you using? and if it's ARR how is the NICs configured ?
0
AshleySPMAuthor Commented:
I am using ARR. I have two NICs, one internal, one external. Only the external has a default gateway.
0
Mohammed HamadaSenior IT ConsultantCommented:
You need to set the DNS on the internal NIC and make sure that you change the NIC order in the network settings so that Internal is on top.

Then you have to also edit the Windows host file and make sure you have Lync Front end FQDN and IP written.

%systemdrive%\windows\system32\drivers\etc\hosts

After you make these changes you will need to make sure that you can ping Lync front end with it's local host name and IP to make sure that you have connectivity.

You need to make sure that you update the ARR machine as well. in case this doesn't fix it then you might have something missing on your ARR config.
0
AshleySPMAuthor Commented:
OK I will try all this today
0
AshleySPMAuthor Commented:
So I still get this from the Lync Connectivity Analyzer when I run it for external connectivity:

Verification failed for Mobility (UCWA) service. The service could not be reached from an external network.

The only URL I can't get to is my external web url via :4443. IIS is listening, I've followed all the steps and I am not sure what to do from here.

Internally, the LCA says everything is fine but even if I am connected to my internal network it doesn't work on mobile clients.
0
AshleySPMAuthor Commented:
Is there a way I can test my reverse proxy settings? I'm almost certain the problem is there
0
AshleySPMAuthor Commented:
Also, when i try to connect from a mobile device I can see the attempt in the IIS logs and a 404 is the return code.
0
AshleySPMAuthor Commented:
I had a few problems here:

1. I did not have the certificate from my front end server installed on the reverse proxy
2. My office web apps server farm URL did not match the office web URL in the CA certificate
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AshleySPMAuthor Commented:
What I found resolved the issue.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Chat / IM

From novice to tech pro — start learning today.