Exchange 联机用户不能访问非面向 Internet 的 活动目录(AD) 站点中的用户的忙/闲信息

重要说明:本文是由 Microsoft 机器翻译软件进行的翻译并可能由 Microsoft 社区通过社区翻译机构(CTF)技术进行后期编辑,或可能是由人工进行的翻译。Microsoft 同时向您提供机器翻译、人工翻译及社区后期编辑的文章,以便对我们知识库中的所有文章以多种语言提供访问。翻译的文章可能存在词汇、句法和/或语法方面的错误。Microsoft 对由于内容的误译或客户对内容的使用所导致的任何不准确、错误或损失不承担责任。

点击这里察看该文章的英文版: 3057905
注意:不再支持包含在 Microsoft Exchange Server 2010年中 Exchange 管理控制台混合配置向导。因此,应不再使用旧的混合配置向导。相反,使用可从 Office 365 混合配置向导 http://aka.ms/HybridWizard.有关详细信息,请参阅 Office 365 的 Exchange 2010 的混合配置向导.
问题
请考虑以下情形:
  • 您有混合部署 Microsoft Exchange Online 和内部 Microsoft Exchange Server。
  • 混合环境有两个 活动目录(AD) 站点。
  • 一个 活动目录(AD) 站点是面向 Internet 和其他站点的非-面向 Internet。
在这种情况下,具有联机 Exchange 邮箱的用户无法访问非面向 – Internet 的 活动目录(AD) 站点中拥有邮箱的内部用户的忙/闲信息。

此外,的事件 ID 4002 类似于以下内容的条目是记录在应用程序日志中每次联机 Exchange 邮箱中面向 Internet 的网站使可用性请求到内部非 – 面向 Internet 站点中的邮箱。

Log Name: ApplicationSource: MSExchange AvailabilityEvent ID: 4002Task Category: Availability ServiceLevel: ErrorKeywords: ClassicUser: N/AComputer: <InternetfacingServer>.domain.comDescription:Process 6424: ProxyWebRequest CrossSite from UserA@contoso.mail.onmicrosoft.com tohttps://<FQDN of non-Internet-facing Exchange>:443/ews/exchange.asmx failed. Caller SIDs: WSSecurity. The exception returned isMicrosoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException:System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive.---> System.IO.IOException: Unable to read data from the transport connection: An existing connectionwas forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connectionwas forcibly closed by the remote host  at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)  at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)  --- End of inner exception stack trace ---  at System.Net.Security._SslStream.EndRead(IAsyncResult asyncResult)  at System.Net.TlsStream.EndRead(IAsyncResult asyncResult)  at System.Net.PooledStream.EndRead(IAsyncResult asyncResult)  at System.Net.Connection.ReadCallback(IAsyncResult asyncResult)  --- End of inner exception stack trace ---  at System.Web.Services.Protocols.WebClientAsyncResult.WaitForResponse()  at System.Web.Services.Protocols.WebClientProtocol.EndSend(IAsyncResult asyncResult,Object& internalAsyncState, Stream& responseStream)  at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)  at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)  at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)  at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)  at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling():<Noresponse>. The request information isProxyWebRequest type = CrossSite, url = https://FQDN of Non-Internet facing Exchange>:443/ews/exchange.asmxMailbox list = <User B>SMTP:UserB@fabrikam.com, Parameters: windowStart = 3/8/2015 1:00:00 PM,windowEnd = 4/7/2015 1:00:00 PM, MergedFBInterval = 30, RequestedView = Detailed. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred ona receive. ---> System.IO.IOException: Unable to read data from the transport connection: An existingconnection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existingconnection was forcibly closed by the remote host  at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)  at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)  --- End of inner exception stack trace ---  at System.Net.Security._SslStream.EndRead(IAsyncResult asyncResult)  at System.Net.TlsStream.EndRead(IAsyncResult asyncResult)  at System.Net.PooledStream.EndRead(IAsyncResult asyncResult)  at System.Net.Connection.ReadCallback(IAsyncResult asyncResult)  --- End of inner exception stack trace ---  at System.Web.Services.Protocols.WebClientAsyncResult.WaitForResponse()  at System.Web.Services.Protocols.WebClientProtocol.EndSend(IAsyncResult asyncResult,Object& internalAsyncState, Stream& responseStream)  at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)  at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)  at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest,QueryList queryList, Service service, IAsyncResult asyncResult)  at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)  at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()  --- End of inner exception stack trace ---. Name of the server where exception originated: <Host name of Internet-facing site>.
请确保 活动目录(AD) 站点或目录林包含该用户的邮箱具有至少一个本地服务器运行 Exchange Server 还运行可用性服务。为可用性服务,打开日志记录,然后测试基本的网络连接。
原因
非-面向 Internet 站点中的 Exchange 服务器上没有安装用于使用 Exchange 联机创建联合身份验证的证书。
本地
面向 Internet 的 Exchange 服务器,从导出的联合身份验证的证书,然后将其导入到非面向 – Internet 的 Exchange 服务器。
详细信息
有关如何导出 Exchange Server 中的证书的详细信息,请参阅以下资源 ︰仍需要帮助?请转到 Office 365 社区 网站或 交换 TechNet 论坛.

属性

文章 ID:3057905 - 上次审阅时间:04/26/2016 14:34:00 - 修订版本: 3.0

Microsoft Exchange Online, Exchange Server 2016 Enterprise Edition, Exchange Server 2016 Standard Edition, Microsoft Exchange Server 2013 Enterprise, Microsoft Exchange Server 2013 Standard, Microsoft Exchange Server 2010 Enterprise, Microsoft Exchange Server 2010 Standard

  • o365e o365m o365022013 o365 o365a hybrid kbmt KB3057905 KbMtzh
反馈