Quantcast
Channel: Exchange Server 2013 - Mobility and ActiveSync forum
Viewing all articles
Browse latest Browse all 1206

ActiveSync for Linked Mailboxes - not syncing

$
0
0

Hello Everyone,

Our Customer organization consists of mixed Exchange 2013/2007 Environment and they are in the process of moving rest of mailboxes to the new environment.
Unfortunately after moving some linked mailboxes to the Exchange 2013 Env. they discovered that those migrated users cannot connect by their smartphones.

ExRca for the each linked mailbox  generate following Error (bellow OPTIONS section)

 The underlying connection was closed: An unexpected error occurred on a receive.  
 System.Net.WebException  at System.Net.HttpWebRequest.GetResponse() at Microsoft.Exchange.Tools.ExRca.Extensions.RcaHttpRequest.GetResponse() 
 Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. 
 Type: System.IO.IOException  at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) 
 at System.Net.Security._SslStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security._SslStream.StartReading(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) 
 at System.Net.Security._SslStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.TlsStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead) Message An existing connection was forcibly closed by the remote host Type: System.Net.Sockets.SocketException  at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) 

The connections for the Ex2007 users are established through the another (separated) reverse proxy and sync for the regural and linked mailboxes works well.
They published ActiveSync for the Exchange 2013 users by preparing the new DNS name and  the new public IP address (for the separation of the Exchange 2007 mailboxes connection).

So all connections for the regular Exchange 2013 mailboxes going well , unfortunately except Exchange 2013 linked mailboxes (regardless of witch linked mailbox smtp domain we choose)


ActiveSync Web Directory settings for each exchange 2013 server are as follows:

Server                                  : SERVERNAME
ExtendedProtectionTokenChecking         : None
ExtendedProtectionFlags                 : {}
ExtendedProtectionSPNList               : {}
ExternalUrl                             : https://mail.domain.com/Microsoft-Server-ActiveSync
ExternalAuthenticationMethods           : {}
RemoteDocumentsInternalDomainSuffixList : {}
InternalUrl                             : https://mail.domain.com/Microsoft-Server-ActiveSync
InternalAuthenticationMethods           : {}
MobileClientCertificateAuthorityURL     : 
BasicAuthEnabled                        : True
WindowsAuthEnabled                      : True
ClientCertAuth                          : Ignore
InternalAuthenticationMethods           : {}
ExternalAuthenticationMethods           : {}
WebSiteSSLEnabled                       : True

Certificate is signed by the Inside organization PKI and contains the new DNS name (in SAN section)

Thanks in advance for any help.

Regards,

HM




Viewing all articles
Browse latest Browse all 1206

Trending Articles