登录
 
主页技术资源库学习下载支持社区论坛
IT 专业人士的资源 >
> 
> 
Lync is experiencing connection issues with the exchange server/Microsoft Lync MAPI COM Server

Answered Lync is experiencing connection issues with the exchange server/Microsoft Lync MAPI COM Server

  • 2011年6月15日 23:21
     
     
    登录进行投票
    0
    Hello,

    We have Lync 2010 deployed internally through an enterprise pool and externally through and edge pool, using UAG as the reverse proxy. Everything works fine internally but when logging in externally the Lync client displays the error at the bottom right of the client that says "Lync is experiencing connection issues with the exchange server."

    Then, a short amount of time later a pop up box that says "Microsoft Lync MAPI COM Server" appears. If you enter your password, the red error on the bottom of the client goes away.

    Or, if you open Outlook and enter your password to login to Outlook Anywhere, the error also goes away and the MAPI COM window never even pops up....  Sometimes....  This is true for 3 out of the 4 users we're testing with.  The other user, which is me, the error never goes away.

    OWA, Outlook Anywhere, ActiveSync, Autodiscover and EWS are all published though UAG and appear to all be working fine from a user standpoint.

    Also, all test ran using the the Exchange Remote Connectivity Analyzer found https://www.testexchangeconnectivity.com/Default.aspx are successful.


    Our UAG trunk for exchange is named exchange2010, and our Authentication and Authorization Servers are named Domain Controllers, fyi.

    In the UAG Application log when the Lync client is first logging in, there is a warning that says
    "User with source IP address failed to log into the trunk exchange2010 (secure=1) using authentication server Domain Controllers with session ID longstringoflettersandnumbers. Error code is Missing credentials.

    So, this is very weird. Does anyone have any insight into this issue? I feel like the issue may lie with the UAG security/authentication configuration.

    Outlook Anywhere is set to use Basic authentication over SSL, as is Autodiscover. We have both an A record and SRV record for Autodiscover, both of which work correctly.

    There are also no certificate issues. Certificates for the Front End Pool, the Edge Pool, Client Access Server and UAG Server/Listener are all installed and configured correctly.
    Thanks,
    Simon
    Simon
     

全部回复

  • 2011年6月17日 8:28
    版主
     
     建议的答复
    登录进行投票
    0

    Hi,Simon,

    Please check if you  select "Use Kerberos Constrained delegation for single sign-on" in the authentication method on your UAG.

    You can refer the follwing link:

    http://support.risualblogs.com/blog/2011/04/07/lync-is-experiencing-connection-issues-with-the-exchange-server-lync-will-attempt-to-repair-the-connection-until-it-is-fully-restored/

    Regards,

    Sharon

    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. This can be beneficial to other community members reading the thread.
     
  • 2011年6月21日 2:21
    版主
     
     
    登录进行投票
    0

    Hi,Simon,

    Have you fixed your problem?

    Any updates please kindly let me know.Thanks!

    Regards,

    Sharon

    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. This can be beneficial to other community members reading the thread.
     
  • 2011年6月22日 2:02
     
     已答复
    登录进行投票
    0

    Hello Sharon,

    Sorry for the delayed response. We do not use KCD authentication. I had the logon authentication set to use 'both' 401 request and html form, but that did not work. I finally broke down and called Microsoft and was eventually passed through to the UAG support group.

    They told me Lync is not supported under UAG. While you can publish the web content download rules through TMG, Lync has trouble accessing Exchange Web Services (EWS) through UAG.

    Therefore, I changed the way Lync accesses EWS and it is working without any errors.

    They said there is high demand for Lync/UAG support and are working towards compatibility.

    Simon

     

    Simon
     
  • 2011年6月23日 10:42
    版主
     
     
    登录进行投票
    0

    Hi,Simon,

    I am glad that you make it work using EWS,and thank you for updating the information here.

    Regards,

    Sharon

    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. This can be beneficial to other community members reading the thread.
     
  • 2011年6月29日 13:43
     
     
    登录进行投票
    0

    Hi Simon,

    What did you exactly chang on UAG? I got same problem here.

    Ivan
     
  • 2011年6月30日 15:40
     
     
    登录进行投票
    0

    Hey Ivan,

    You know how when you set your EWS URL, and your OWA and Outlook Anywhere use that same URL?  Well when you publish EWS, OWA and Outlook anywhere through UAG, the Lync client does not like that.

    So basically, you need to modify your config in such a way that the Lync client contacts the Exchange Client Access server directly for EWS.

    So I didn't really change anything on UAG to make it work, I just stopped publishing EWS through UAG.

    Does that make sense?

     

    Simon

    Simon
     
  • 2011年7月2日 17:31
     
     
    登录进行投票
    0

    I talked to MS today. My issue is traced and it seems quite strange.

     

    All the machines who were external were logged on with cached credentials. Now as soon as we logged on with local user no problems. From a lync perspective my configuration was fine. We also noticed slow logon to lync front end when logged on with cached credentials. A VPN connection solved the issue.

     

    Now i find this behavior kind of strange. So al my users who are domain joined and have cached credentials need VPN. Others out of domain don't. Microsoft says: We don't see users who are external in a domain. Really strange.

     

    anyone got same issue?

    Ivan
     
  • 2012年5月23日 20:36
     
     
    登录进行投票
    0

    I have exactly the same problem. Domain joined computers are unable to establish the Exchange connection. Non-domain members can use Lync client as aspected. Whats going wrong here?

    If I disable SSO on EWS application I have no errors. But I think that is not a security best practice. 

     
  • 2013年1月10日 17:48
     
     
    登录进行投票
    0

    I have got the same issue

    On the LAN – EWS fine

    Non domain client across internet – ews fine

    Domain client across internet EWS issue

    So its seems the domain client is the poor partner in this relationship

    We are publishing via UAG

    I have a ticket open with MS, as they published a white paper on delivering autodiscover and ews via UAG/TMG at the end of last year.

    I suspect we will end up breaking ews away from UAG and handling it either via TMG or direct – not ideal  

    Will post back with outcome - have lost days to this issue, and as Simon says I 'finally' broke and gave in to calling to PSS :-)