Hello,
I have implemented a Lync 2013 Standard environment at my facility. I have 1-FE server, 1-Edge server, and 1-Reverse Proxy server running ARR. All the functions I’m looking to implement are working fine internally and externally for the PC clients. However the issue lies with the 2013 mobility client. I can connect from external networks, but I CANNOT connect from our internal network for some reason. I went through many of the post here and can’t seem to find the hang up. Here are the steps I’ve verified already.
Internal DNS records applicable:
Lync (external web services) – pointing to the external address of the reverse proxy
LyncDiscover - pointing to the external address of the reverse proxy
LyncDiscoverInternal - pointing to the internal address of the FE
Reverse Proxy Server Farm applicable:
Lyncdiscover - pointing to the FE (httpPort 8080, httpsPort 4443)
Lync - pointing to the FE (httpPort 8080, httpsPort 4443)
Reverse Proxy Cert
lync.mydomain.com
meet.mydomain.com
dialin.mydomain.com
lyncdiscover.mydomain.com
lyncowa.mydomain.com
Exposed Web URL is set to “External”
I can relay my entire configuration if needed but I’m pretty sure there is an issue with how the 2013 mobile client tries to autodiscover. Internally if I’m not mistaken it should look for lyncdiscoverinteral. If it doesn’t resolve that it should look at lyncdiscover, and with the DNS entry pointing back to the external address of the reverse proxy it should route it to the server farm for lyncdiscover and in turn to go to the FE.
The strange thing that doesn’t make sense to me is the fact that it works externally, just not internally.