locked
Screen sharing on mobile RRS feed

  • Question

  • Hi everyone,

    We have a very strange situation and I hoped someone could clear up why this happens.

    We have an on-premise SfB environment in which screen sharing to mobile works only by clicking "Meet Now". If we on the other hand open a normal conversation and add a 3rd person in, screen sharing to mobile won't work.

    This doesn't happen in our Office 365 SfB, both methods work.

    So that raises the question - Is using Meet Now different in any way from simply creating a conference in regards to screen sharing?

    Thank you.

    Tuesday, November 14, 2017 1:12 PM

Answers

  • Hi Alice,

    thank you for your reply.

    I've been digging around the internet and found that the problem was caused by misplaced certificates.

    Root and Intermediate certificates were scattered around and I had to put each one in its right place.

    It works now,

    Thanks.

    • Proposed as answer by Alice-Wang Friday, November 24, 2017 1:42 AM
    • Marked as answer by Agat S Sunday, November 26, 2017 8:21 AM
    Thursday, November 23, 2017 12:00 PM

All replies

  • Hi,

    Would you please tell us did the issue only happen to specific user?

    What error message did you see when you try to share screen?

    For this issue, we suggest you test with another user check if there is the same issue.

    For SFB server side, please try to check if there are any event IDs in application log, if there are any errors, please provide it for us to do troubleshooting.


    Regards,

    Alice Wang


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, November 15, 2017 6:49 AM
  • After having a look at the logs it looks like this error log repeats itself A LOT.

    Skype for Business Server 2015, File Transfer Agent cannot get replication status from Replica Replicator Agent on Edge

    Edge machine: edge.[my.domain]
    Exception: System.ServiceModel.Security.MessageSecurityException: The HTTP request was forbidden with client authentication scheme 'Anonymous'. ---> System.Net.WebException: The remote server returned an error: (403) Forbidden.
       at System.Net.HttpWebRequest.GetResponse()
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       --- End of inner exception stack trace ---

    Server stack trace: 
       at System.ServiceModel.Channels.HttpChannelUtilities.ValidateAuthentication(HttpWebRequest request, HttpWebResponse response, WebException responseException, HttpChannelFactory`1 factory)
       at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.Rtc.Xds.Replication.Common.IReplicationWebService.DownloadFiles(String senderFqdn, String sourceDirPath, String tempDirPath)
       at Microsoft.Rtc.Xds.Replication.FileTransfer.FileTransferTask.CopyFilesFromReplicaUsingWcf(String fromDir, String tmpDir, String toDir)
    Cause: Service may be unavailable or Network connectivity may have been compromised.
    Resolution:
    Verify that Replica Replicator Agent service is running on the Edge machine, network connectivity is available and TLS is configured correctly. For details, see http://support.microsoft.com/kb/2464556

    The service on the Edge is running and ICMP testing succeeds between the two.

    Is it possible there's a connection between this log and the screen sharing? Seems odd to me.


    • Edited by Agat S Thursday, November 16, 2017 11:45 AM
    Thursday, November 16, 2017 8:29 AM
  • Hi Agat,

    Thanks for your reply.

    So according your logs, it seems CMS replication failed on Edge server. Is it the Event ID 1047?
    Based on my experience, you could try the following steps to resolve this issue first:
    1. Open Register Editor on the Edge server;
    2. Navigate to “HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL”,
    3. Add two DWORD Values: ClientAuthTrustMode (Value 2), SendTrustedIssuerList (Value 0).
    4. Restart the Edge server;

    After this, run the command “Invoke-CSManagementStoreReplication -ReplicaFqdn edge.domain.com” on the FE server, and wait a couple of minutes, check the replication status in control plane.
    If the replication issue fixed, then test your scenario again.
    If the problem still reproduces, please check on Edge server to see if there are other related Lync server Event logs.
    Thanks a lot!


    Regards,

    Alice Wang


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, November 21, 2017 5:58 AM
  • Hi Alice,

    thank you for your reply.

    I've been digging around the internet and found that the problem was caused by misplaced certificates.

    Root and Intermediate certificates were scattered around and I had to put each one in its right place.

    It works now,

    Thanks.

    • Proposed as answer by Alice-Wang Friday, November 24, 2017 1:42 AM
    • Marked as answer by Agat S Sunday, November 26, 2017 8:21 AM
    Thursday, November 23, 2017 12:00 PM
  • Hi Agat,

    Thanks for your sharing, you can mark your reply as an answer, it will help others who has similar isssue


    Regards,

    Alice Wang


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, November 24, 2017 1:42 AM