I have an outstanding Skype admin and passed this thread on to him for comment. Here is his response:
Ughhhhhhh. That's nasty. I agree with the DNS issue though. Also curious they're not deploying edges either. I'd parallel build and migrate people to a brand new Skype for business 2015 instance. /jim ----- James Rupprecht IT Architect, Enterprise Systems KU Information Technology Phone: +1 785 864-0116 Skype/Email: [email protected]<mailto:[email protected]> From: [email protected] [mailto:[email protected]] On Behalf Of Melvin Backus Sent: Tuesday, January 24, 2017 2:15 PM To: [email protected] Subject: RE: [NTSysADM] RE: Any Lync / Skype gurus about? I think we may have found it. The problem is it can’t be changed. The tech who originally set things up used the internal domain name instead of the external domain name when he setup the pool. Since we were told it would never be available externally that may have made since, but hey, things change. Unfortunately there doesn’t appear to be a reliable way to change that short of building a new server. That may force the timing on us upgrading, or push the whole thing to the cloud. -- 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 1:57 PM To: [email protected]<mailto:[email protected]> Subject: Re: [NTSysADM] RE: Any Lync / Skype gurus about? Its been a while for me, but I concur that this could easily be a DNS issue. Also, isnt there a server setting where you have to manually put in the external FQDN? -- Espi On Tue, Jan 24, 2017 at 7:31 AM, Michael B. Smith <[email protected]<mailto:[email protected]>> wrote: Not really my area of expertise, but in my limited experience this kind of thing is usually caused by a DNS error. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Melvin Backus Sent: Tuesday, January 24, 2017 8:01 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] Any Lync / Skype gurus about? 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.
