locked
Users can participate in conferences only via Web RRS feed

  • Question

  • Hi,

    We have a problem with users that they can access the conferences only via Web. 

    Via Skype for Business client they can only Chat (starting audio or video is not possible).

    Where should we troubleshoot?

    Thank you for all for help.

    Regards

    Iron

    Sunday, May 19, 2019 1:24 PM

All replies

  • Hi iron_flower,

    About your issue, I would collect some more information:

    Which version of Skype for Business server do you use, Skype for Business server 2015 on-premise or O365?

    What is the version of Skype for Business client, Office 2013/2016 or O365?

    Is there any error on the client side when the issue happened?

    How many users have this issue, most of all or only specific user?

    If most of all had this issue, I think you may first check the policies (client policy/ conferencing policy) on the server side to see if there is any configuration related this. 

    If only specific user had this issue, compare the configuration (client policy/ network configuration) with others, and try to clean the user profile temp files (%userprofile%\AppData\Local\Microsoft\Office\1x.0\Lync\Sip_xxx) and re-login the client to see if it helps.

    Best Regards,
    Shaw Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    • Edited by Shaw_Lu Monday, May 20, 2019 6:28 AM
    Monday, May 20, 2019 6:28 AM
  • Hi,

    It pertains only some users.

    This is SfB 2015 on premise.

    The client's policies are the same for all users.

    Other info: it pertains only the conferences created by other companies.

    The affected users can access these conferences via Web not via client.

    Monday, May 20, 2019 8:38 AM
  • I made other tests:

    P2P connection between LAN user and External user:

    1. LAN (affected) - External  - no media set

    2. LAN (good user) - External - media set

    After comparing Wireshark I can see that in Case 1 after sending STUN Allocate Request User the error is sent back:

    "ERROR-CODE 436 (*Unknown error code*): The Username supplied in the request is not known".

    In Case 2 the Allocate Success is sent with mapped Address.

    Could it have aything to do with the certificates?

    Tuesday, May 21, 2019 12:44 PM
  • It looks like the problem described here:

    http://ucadministrators.blogspot.com/

    But it pertains Skype for Business Client so it is stranger.

    Tuesday, May 21, 2019 2:34 PM
  • Hi,

    Thanks for your sharing.

    Are the affected machine and the good one in the same LAN? Check if there is any other difference, such as: anti-virus application.

    In addition, check the required port (3478) is opened in the network.


    Best Regards,
    Shaw Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, May 22, 2019 9:07 AM
  • Hi,

    As I said the STUN protocol error answered appear which means that the port is opened.

    There is no difference between computers of working and non working users.

    Regards,

    Iron

    Wednesday, May 22, 2019 11:05 AM
  • Hi iron_flower,

    If the affected user login on the good machine, could it work?


    Best Regards,
    Shaw Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    • Edited by Shaw_Lu Thursday, May 23, 2019 9:39 AM
    Thursday, May 23, 2019 9:39 AM
  • Hi,

    Is there any update on this case?

    Please feel free to drop us a note if there is any update.


    Best Regards,
    Shaw Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, May 27, 2019 7:15 AM
  • No unluckily not.

    But bad one can log on bad machine.

    This could be somewhere inside on the Windows settings?

    Monday, May 27, 2019 8:51 AM
  • Hi,

    How about using “netsh” to reset the windows network?

    netsh winsock reset

    netsh int ip reset 

    ipconfig /flushdns 


    Best Regards,
    Shaw Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    • Edited by Shaw_Lu Monday, May 27, 2019 9:33 AM
    • Proposed as answer by Shaw_Lu Wednesday, June 5, 2019 9:29 AM
    • Unproposed as answer by iron_flower Wednesday, June 19, 2019 7:41 AM
    Monday, May 27, 2019 9:33 AM
  • Hi,

    Do you have any further issue on this topic?

    Meanwhile, if there is no issue, please remember to mark helpful reply as answer to close the thread. Your action would be helpful to other users who encounter the same issue and read this thread.

    Thanks for your understanding.


    Best Regards,
    Shaw Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, May 31, 2019 9:29 AM
  • We will rebuild Edge server in order to see if it has anything to do with Edge's server.

    After it I will inform you after tests.

    Monday, June 17, 2019 12:36 PM
  • Try doing a meet now. Go to the Skype client, on the right side of the client, click on the down arrow next to the gear and click on meet now. 

    Since the meeting works via the Web. We can rule out the IIS being the issue.

    what version are you running on the client. 

    Monday, June 17, 2019 3:41 PM
  • Guys,

    Problem was with certificates.

    This rejection of STUN protocol was caused by not properly working authentication.


    • Proposed as answer by Shaw_Lu Wednesday, June 19, 2019 7:48 AM
    Wednesday, June 19, 2019 7:42 AM
  • Thanks for your sharing! 

    Best Regards,
    Shaw Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, June 21, 2019 7:30 AM