locked
Lync and Outlook re-connection issues switching between wireless and LAN connections RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    *Originally posted here.  Was asked to post in Lync forum.

    (This affects users on all Windows and Office versions)

    • Lync Server 2013 on Prem
    • Exchange 2013 on Prem

    Users on laptops and Surface devices:  When switching from a LAN connection to wireless and wireless to LAN, are disconnected from Lync and Outlook (only when Cached mode is disabled). 

    • Sometimes the connection comes up quickly after the new connection is established.
    • Sometimes the connection takes over a few minutes for Lync, Outlook, or both.
    • Sometimes one or both will not reconnect at all, until the user cancels and signs back in, or closes and reopens the app.

    I'm trying to discover the reason for this inconsistent behavior.

    The Lync issue is more annoying.  But for Outlook, sometimes users loose drafts when they are forced to sign out or restart outlook.  Neither prompts for credentials when these issues occur.

    If more information is needed on current infrastructure, let me know.

    Thanks,

    -Matt

    There's no place like 127.0.0.1

    Monday, August 29, 2016 5:58 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Matt,

    Few questions

    1. Do you have pst files stored on your network?

    2. Have you checked the event viewer to see if there are any errors?

    3. Have you tried running OffCAT?

    -Don

    Monday, August 29, 2016 7:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No PST files.

    No relevant Event Viewer errors.

    OffCat reports no issues. 

    There's no place like 127.0.0.1

    Monday, August 29, 2016 8:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Matt,

    This kind of issues could be caused by many reasons, and the root cause analysis might be difficult to be performed in the short term.

    Anyway, please make sure all your servers and clients are fully patched. If there is any load balancer/proxy server/any other intermediate equipment between the affected clients and servers, try to bypass them by adding records in localhost file on the client side.

    If the issue still can be produced after above steps, try to capture network trace to see where the delay happens.

    Best Regards,
    Jessie Yuan


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, August 30, 2016 2:40 AM