Online users can't present content in on-premises hosted meetings in a Skype for Business hybrid deployment
Online hosted users report that they receive the following error message when they try to present or view meeting content that's hosted in an on-premises Skype for Business meeting when they're connected to an internal corporate network: Note
When users are connected externally, they can share content.
This issue occurs because the user’s Skype for Business client can't resolve the DNS entry for the Edge server’s web conferencing service FQDN. This issue typically occurs because a split DNS has been configured for the sip domain, and there is no entry in the internal DNS zone for the Edge server’s external DNS A records for the web conferencing service.
Add DNS A records for the Edge server's web conferencing service for all Skype for Business Edge servers. For example, add the DNS A host record for webcon.contoso.com
so that it resolves to the external edge IP address for this service. Make sure that you add one record for each Edge server.
Users who are homed online will connect to meeting content through the Edge proxy service. If the DNS record can't be resolved, these users will be unable to connect. In this situation, the Skype for Business local tracing log will display the following error in the diagnostic header in the Service out message error report for the failed connection attempt:
54503;reason="Connection to the Web Conferencing Server could not be established due to client DNS configuration"
If DNS A records exist but resolve to the wrong IP address, the client UI will display the following diagnostics:
Additionally, the tracing log will display the following error, together with an explanation that the probe was completed but did not succeed:
54000;reason="Connection to the Web Conferencing Server could not be established"
for other considerations.
Article ID: 3161393 - Last Review: 05/11/2016 15:33:00 - Revision: 3.0