locked
Walkthough for Lync Mobile Clients RRS feed

  • Question

  • Hello Everybody,

         Ive been going in circles and at this point I'm completely lost. I am trying to allow the both internal and external Lync 2010 mobile clients connect to our internal lync 2013 infrastructure. Here is our current setup: 1 Lync 2013 front end pool, 1 edge server, and 1 TMG server. 

         From inside of our network all desktops are able to sign into lync desktop client but are unable to connect using the mobile app. I read somewhere that a TMG server is needed so I setup one following this guide http://social.technet.microsoft.com/wiki/contents/articles/9807.how-to-configure-forefront-tmg-2010-as-reverse-proxy-for-lync-server-2010.aspx 

         I have created the following internal dns records: meet, admin, dialin, lyncdiscoverinternal, and srv record which all point to the front end server. 

       Our system administrator created the following dns entries: meet, admin, dialin, lyncdiscover which points to the reverse proxy server external address. 

       How ever when I try to connect using the mobile app on my ipad or android it times out any suggestions would be greatly appreciated. 

    Monday, March 4, 2013 12:15 PM

Answers

  • Hi,

    Please refer to Jeff's blog to check if all required steps have been finished.

    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.

    Please double check the DNS record:

    One of the following internal dns records:

    CNAME  lyncdiscoverinternal.<sipdomain>  Internal Web Services FQDN for your Director pool, if you have one, or for your Front End pool if you do not have a Director

     A (host)  lyncdiscoverinternal.<sipdomain>  Internal Web Services IP address (virtual IP (VIP) address if you use a load balancer) of your Director pool, if you have one, or of your Front End pool if you do not have a Director

    One of the following external dns records:

    CNAME  lyncdiscover.<sipdomain>   External Web Services FQDN for your Director pool, if you have one, or for your Front End pool if you do not have a Director

     A (host)  lyncdiscover.<sipdomain>  External or public IP address of the reverse proxy


    Kent Huang
    TechNet Community Support

    • Proposed as answer by Kent-Huang Monday, March 11, 2013 9:38 AM
    • Marked as answer by Kent-Huang Monday, March 11, 2013 9:38 AM
    Tuesday, March 5, 2013 3:10 AM
  • Here are the details at a high level.  Internally you need lyncdiscoverinternal.domain.com and it should point to your front-end servers (VIP on HLB).  Internally you should also have a DNS record for your external web services (lyncrp.domain.com for example) that should resolve to your public IP address.  That public IP address should be pointing at your reverse proxy on port 443 which should bridge to port 4443 of your front-end servers.

    This is the important part, internally your users need to be able to successfully connect to that public IP address on port 443.  This will require you to make sure that hair-pinning of your network traffic works.  So from an internal computer you should be able to do this:

    telnet public.ip.address.xxx 443

    Externally, the only two records you need for mobility is lyncdiscover.domain.com and your external web services (lyncrp.domain.com for example) and again both of those should be pointing at your reverse proxy.

    Hopefully that makes sense.

    Thanks,

    Richard


    Richard Brynteson, Avtex, Lync MCM, Blog - www.masteringlync.com

    • Proposed as answer by Kent-Huang Monday, March 11, 2013 9:38 AM
    • Marked as answer by Kent-Huang Monday, March 11, 2013 9:38 AM
    Tuesday, March 5, 2013 3:13 AM

All replies

  • Hi,

    Please refer to Jeff's blog to check if all required steps have been finished.

    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.

    Please double check the DNS record:

    One of the following internal dns records:

    CNAME  lyncdiscoverinternal.<sipdomain>  Internal Web Services FQDN for your Director pool, if you have one, or for your Front End pool if you do not have a Director

     A (host)  lyncdiscoverinternal.<sipdomain>  Internal Web Services IP address (virtual IP (VIP) address if you use a load balancer) of your Director pool, if you have one, or of your Front End pool if you do not have a Director

    One of the following external dns records:

    CNAME  lyncdiscover.<sipdomain>   External Web Services FQDN for your Director pool, if you have one, or for your Front End pool if you do not have a Director

     A (host)  lyncdiscover.<sipdomain>  External or public IP address of the reverse proxy


    Kent Huang
    TechNet Community Support

    • Proposed as answer by Kent-Huang Monday, March 11, 2013 9:38 AM
    • Marked as answer by Kent-Huang Monday, March 11, 2013 9:38 AM
    Tuesday, March 5, 2013 3:10 AM
  • Here are the details at a high level.  Internally you need lyncdiscoverinternal.domain.com and it should point to your front-end servers (VIP on HLB).  Internally you should also have a DNS record for your external web services (lyncrp.domain.com for example) that should resolve to your public IP address.  That public IP address should be pointing at your reverse proxy on port 443 which should bridge to port 4443 of your front-end servers.

    This is the important part, internally your users need to be able to successfully connect to that public IP address on port 443.  This will require you to make sure that hair-pinning of your network traffic works.  So from an internal computer you should be able to do this:

    telnet public.ip.address.xxx 443

    Externally, the only two records you need for mobility is lyncdiscover.domain.com and your external web services (lyncrp.domain.com for example) and again both of those should be pointing at your reverse proxy.

    Hopefully that makes sense.

    Thanks,

    Richard


    Richard Brynteson, Avtex, Lync MCM, Blog - www.masteringlync.com

    • Proposed as answer by Kent-Huang Monday, March 11, 2013 9:38 AM
    • Marked as answer by Kent-Huang Monday, March 11, 2013 9:38 AM
    Tuesday, March 5, 2013 3:13 AM