Hello,
my lync deployment is a single server 2012 with lync 2013 standard edition. so far enabled lync clients are able to login successfully. I setup mobiliity, set the ports with the following commands:
Set-CsWebServer -Identity lync-mfd.domain.intl -McxSipPrimaryListeningPort 5086
Set-CsWebServer -Identity lync-mfd.domain.intl -McxSipExternalListeningPort 5087
ensured that the CsMcxConfiguration exposed web url is set to internal. the certificate SAN has all the required records:
lyncdiscoverinternal.domain.intl
lync-mfd.domain.intl
lync.domaingroup.com (this is the external web link) there is a dns record that points to my FE server. I don't have edge or proxy at first I want to test mobility from the internal network.
when I test the mobility server configuration with Test-CsMcxP2PIM the result is success. when testing with lync connectivity analyzer for mobility with autodiscover on I get "Your deployment meets the minimum requirements for Lync Mobile 2013 App."
but with the server discovery set at manual to lync-mfd.domain.intl I get "can't be resolved by dns server" but I can resolve with nslookup.
the problem is I can't sign in with any mobile 2013 app, android or ios.
if I use autodiscover I get "Can't connect to the server"
if I use https://lyncdiscoverinternal.domain.intl I get nothing just stuck signing in.
if I supply lync-mfd.domain.intl I get " we can't sign you in please check your account info and try again". my sip uri is the same as my UPN. user@domain.intl. this step is the closest I have come to fixing the issue, this means my client sees the server but can't get a webticket for some reason.
Note: if I manually try to access the webtickiting service with ie 10 I get a response from the server. but only using https://lync-mfd.domain.intl.... if I use https://lyncdiscoverinternal.domain.intl.... I get 403 forbidden.
sorry for making it long but this will help answering the question faster. :) I appreciate any help and any idea.