DNS changes were made several weeks ago.  It actually does get to the correct 
site initially since that’s the proxy server it’s hitting, but the redirect 
later is failing because of the name.  I suppose I could try a shell session on 
the phone to see if it resolves correctly though.


--
There are 10 kinds of people in the world...
         those who understand binary and those who don't.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Kennedy, Jim
Sent: Tuesday, January 24, 2017 11:14 AM
To: [email protected]
Subject: RE: [NTSysADM] Any Lync / Skype gurus about?

From what I have seen, cell phone companies are VERY slow to propagate DNS 
changes.  It may just be that lag.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Melvin Backus
Sent: Tuesday, January 24, 2017 11:04 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [NTSysADM] Any Lync / Skype gurus about?

IDK, I’ve been secondary on this. I’ll pass it along.
Thanks

--
There are 10 kinds of people in the world...
         those who understand binary and those who don't.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Micheal Espinola Jr
Sent: Tuesday, January 24, 2017 10:02 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [NTSysADM] Any Lync / Skype gurus about?

Have you reviewed this: Lync Server 2010 - Technical Requirements for 
Mobility<%20https:/technet.microsoft.com/en-us/library/hh690030(v=ocs.14).aspx>


--
Espi


On Tue, Jan 24, 2017 at 5:00 AM, Melvin Backus 
<[email protected]<mailto:[email protected]>> wrote:
We’ve been beating our heads against this one for a while with no luck.  We’re 
running Lync 2010 servers and trying to get the mobile access working.  For 
some reason when mobile users try to connect to a meeting from outside the 
network the initial page comes up then immediately redirects to the internal 
address of the backend server. Since that is pointing to an internal only 
domain name it won’t resolve and they get a 404 error.  We’ve been through 
everything we can find and changed it to point to the external address but 
still no luck.  This all works fine for external PC clients, only fails with 
mobile.  Mobile works fine as well if it connects to the internal guest 
wireless.

Lync Server 2010 Standard – 1 backend server, one frontend server, reverse 
proxy running on IIS with Adv URL rewrite.

Any suggestions as to where we might have missed?  We’ve been Googling for 
weeks and while we obviously aren’t the only ones who’ve run into this, no one 
has published whatever fixed it, assuming that happened. ☺

Thanks

--------------------
Service Desk | 404-497-1599<tel:(404)%20497-1599> | 
https://servicedesk.byers.com<https://servicedesk.byers.com/>
Melvin Backus | Sr. Systems Engineer | Byers Engineering Company | 
404.497.1565<tel:(404)%20497-1565>
--
There are 10 kinds of people in the world...
         those who understand binary and those who don't.


Reply via email to