Lync 2013 - ipad


I have a lync 2013 environment setup along with a reverse proxy server for mobile users.

Desktop users can sign in fine using the 2013 client, however apple devices are unable to sign in unless they use the 2010 application.

Is this down to settings on the server or somethign that needs changing on the apple devices?

If i try to sign in using the  2013 application it states: ‘Cant connect to the server. It may be busy or unavailable. Please try again’

Who is Participating?
supportguy360Connect With a Mentor Author Commented:
I have the following hairpin rule in place on our sonicwall:

Original Source: Firewalled Subnets
Translated Source: Public IP address
Original Destination: Public - Public IP address
Translated Destination: DMZ IIS ARR Server IP address
Original Service: HTTP and HTTPS
Translated Service: Original
Inbound Interface: Any
Outbound Interface: Any
Comment: Loopback policy
Enable NAT Policy: Checked
Create a reflexive policy: unchecked

I was able to log into one of the apple devices on the 2010 App again earlier, but after a short time i logged out and unable to connect again now.

This is a known issue:

Take a look here for the resolution:
Are iOS device the only mobility clients which cannot connect (meaning Android and WP8 work) or are those the only mobility client's you have tested?

If the latter than you probably do not have the correction configuration allowing traffic hair-pinning to the reverse proxy.  the requirements between the 2010 and 2013 clients are quite different.

See this article for more details:
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

supportguy360Author Commented:
Mnay thanks.

I have the server root certificate installed ont he ipad along with the Front end certificate.  

The front end certificate is added to the bindings on the Reverse proxy server already and the front end server.

I will look into the hair pin rule on the firewall and let you know the outcome.

supportguy360Author Commented:

The hairpin rule was added to the firewall and the same issue is happening.  I removed the hairpin rule as it seemed to prevent 2010 app signing in, now both 2010 and 2013 apps are unable to login.
supportguy360Author Commented:
The issue was down to an IP trypo in the firewall rule.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.