locked
Lync 2010 - Desktop Sharing Disconnect RRS feed

  • Question

  • Thank you in advance for any help.

    We are running the Lync 2010 with 2 Edge Servers, DNS load balanced with NAT. 

    Desktop sharing between an internal and external user or sharing between external/external is having an issue. The issue is that the sharing session can be initiated from either user.  For this scenario, User A initiates the sharing.  Then User B takes over sharing and all works ok.  Then User A takes sharing back, the session starts to connect and you begin to see the sharing on User B's screen.  Then it disconnects "sharing ended due to network issues.  try again later".

    I have monitored on both Edge Servers and cannot see any errors.  The client logs don't seem to find any issues either.  The firewall is open.  Users connect using either Edge server for the first two sharing attempts without issue.  The failure occurs (monitoring via netstat) with users connecting on either Edge Server. 

    Please let me know what further information would be useful.  Any help is greatly appreciated.  Thanks

    Wednesday, October 17, 2012 3:35 PM

Answers

  • Hi,W1nqs,

    "I have monitored on both Edge Servers and cannot see any errors.  " Does this mean you have enabled Lync server logging tool on both Edge servers ?Which items did you selelct?Would you please enable Lync server logging on Lync FE server since the dataMCU on Lync FE server is involved in Desktop sharing session.

    Also please run NetMon or Wirrshark on your clients and Lync servers then reproduce the issue to see how the traffic goes to,maybe you will find where and why it disconnects.

    Besides,here is a great blog posted by Elan describes different conferencing scenario,it may help you understand the connection between different clients via Edge server.

    http://www.shudnow.net/2010/12/06/lync-server-2010-port-ranges-and-audiomedia-negotiation/ 

    Another blog talking about Lync Edge and Load balancing with NAT for your reference.

    http://www.shudnow.net/2012/04/25/lync-2010-edge-servers-and-ip-requirements-nat-vs-public-ip/ 

    Regards,

    Sharon 


    Sharon Shen

    TechNet Community Support

    ************************************************************************************************************************

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

    • Proposed as answer by Sharon.Shen Friday, November 2, 2012 2:01 AM
    • Marked as answer by Sharon.Shen Tuesday, November 6, 2012 2:14 AM
    Thursday, October 18, 2012 9:25 AM
  • I would look at the client logs and search for ICEWarning and then reference Chapter 9 - External User chapter of Resource kit (http://www.microsoft.com/en-us/download/details.aspx?id=22644). Desktop/app sharing requires TCP, which is dependent on TCP 443 on the A/V role of the Edge server or the internal Edge interface if the client is internal. I have seen some filtering/firewall issues internally which blocks this traffic. The warning should provide some info. If you past the warning text, would be happy to assist on deciphering.

    Cheers,

    Jeff

    • Proposed as answer by Sharon.Shen Friday, November 2, 2012 2:01 AM
    • Marked as answer by Sharon.Shen Tuesday, November 6, 2012 2:14 AM
    Sunday, October 21, 2012 6:05 AM

All replies

  • Hi,W1nqs,

    "I have monitored on both Edge Servers and cannot see any errors.  " Does this mean you have enabled Lync server logging tool on both Edge servers ?Which items did you selelct?Would you please enable Lync server logging on Lync FE server since the dataMCU on Lync FE server is involved in Desktop sharing session.

    Also please run NetMon or Wirrshark on your clients and Lync servers then reproduce the issue to see how the traffic goes to,maybe you will find where and why it disconnects.

    Besides,here is a great blog posted by Elan describes different conferencing scenario,it may help you understand the connection between different clients via Edge server.

    http://www.shudnow.net/2010/12/06/lync-server-2010-port-ranges-and-audiomedia-negotiation/ 

    Another blog talking about Lync Edge and Load balancing with NAT for your reference.

    http://www.shudnow.net/2012/04/25/lync-2010-edge-servers-and-ip-requirements-nat-vs-public-ip/ 

    Regards,

    Sharon 


    Sharon Shen

    TechNet Community Support

    ************************************************************************************************************************

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

    • Proposed as answer by Sharon.Shen Friday, November 2, 2012 2:01 AM
    • Marked as answer by Sharon.Shen Tuesday, November 6, 2012 2:14 AM
    Thursday, October 18, 2012 9:25 AM
  • I would look at the client logs and search for ICEWarning and then reference Chapter 9 - External User chapter of Resource kit (http://www.microsoft.com/en-us/download/details.aspx?id=22644). Desktop/app sharing requires TCP, which is dependent on TCP 443 on the A/V role of the Edge server or the internal Edge interface if the client is internal. I have seen some filtering/firewall issues internally which blocks this traffic. The warning should provide some info. If you past the warning text, would be happy to assist on deciphering.

    Cheers,

    Jeff

    • Proposed as answer by Sharon.Shen Friday, November 2, 2012 2:01 AM
    • Marked as answer by Sharon.Shen Tuesday, November 6, 2012 2:14 AM
    Sunday, October 21, 2012 6:05 AM