I have a multi-tennant Exchange environment and am working on a migration from Exchange 2007 to 2013. I am having trouble with ActiveSync for mailboxes on 2007, through my 2013 CAS. Here is what my environment looks like:
Internet-facing Exchange 2007 CAS 2007cas1/10.1.1.2/204.228.1.2 (name/internal IP/external IP)
Non-Internet-facing Exchange 2007 CAS 2007cas2/10.1.1.3 (name/internal IP)
Internet-facing Exchange 2013 CAS/MBX 2013casmbx1/10.1.1.4/204.228.1.4 (name/internal IP/external IP)
2007 URL: webmail.hosteddomain.com
2013 URL: testmail.hosteddomain.com
Certificate: Third-party CA wildcard cert
I have verified that OWA out OutlookAnywhere work. When I try to connect to my Exchange 2007 mailbox (and only 2007) through ActiveSync, my phone says "Can't connect to server" and I see the following entries in my IIS logs (2013casmbx1):
Front-end:
2015-06-15 16:28:32 10.147.0.34 OPTIONS /Microsoft-Server-ActiveSync/default.eas &CorrelationID=;&ClientId=PYSJZZTTUA9DOEHLZDW&cafeReqId=3b8bbbeb-f258-4f82-8ae2-85ddb58433f7; 443 mtest2#customerdomain.com 10.2.1.2 Android/5.1.1-EAS-2.0 - 500 0 0 124
2015-06-15 16:47:44 10.147.0.34 GET /Microsoft-Server-ActiveSync/default.eas &CorrelationID=;&ClientId=YGEGSFJYKEWUKETSAGG&cafeReqId=96b81a28-90ab-45cf-9d7d-c117c7cba7d9; 443 domain\mtest2_customerdomain 10.2.1.2 Mozilla/5.0+(Windows+NT+6.3;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/43.0.2357.124+Safari/537.36 - 500 0 0 21612
Back-end:
2015-06-15 16:28:32 fe80::24f5:677f:e642:1b83%12 OPTIONS /Microsoft-Server-ActiveSync/Proxy/default.eas &Log=PrxTo:2007cas2.domain.local_PrxFrom:fe80%3a%3a24f5%3a677f%3ae642%3a1b83%2512_V0_HH:testmail.hosteddomain.com_SmtpAdrs:mtest2%40customerdomain.com_Error:SendFailure_Mbx:2007mbx1.domain.local_Dc:dc01.domain.local_SBkOffD:L%2f-470_TmRcv16:28:32.7702994_ActivityContextData:ActivityID%3d3b8bbbeb-f258-4f82-8ae2-85ddb58433f7%3bI32%3aADR.C%5bDC01%5d%3d1%3bF%3aADR.AL%5bDC01%5d%3d1.1509%3bI32%3aADS.C%5bDC01%5d%3d3%3bF%3aADS.AL%5bDC01%5d%3d2.216033%3bI32%3aADS.C%5bdc01%5d%3d1%3bF%3aADS.AL%5bdc01%5d%3d1.7718%3bI32%3aATE.C%5bdc01.domain.local%5d%3d1%3bF%3aATE.AL%5bdc01.domain.local%5d%3d0%3bI32%3aATE.C%5bDC01.domain.local%5d%3d3%3bF%3aATE.AL%5bDC01.domain.local%5d%3d5%3bS%3aWLM.Bal%3d480000%3bS%3aWLM.BT%3dEas_Budget:(D)Owner%3aSid%7eDOMAIN%5cMTest2%5Fcustomerdomain%7eEas%7efalse%2cConn%3a0%2
I verified that the AS virtual directories on our 2007 CAS server look like this:
InternalURL: webmail.hosteddomain.com
ExternalURL: $null
BasicAuthEnabled: True
WindowsAuthEnabled: False
Finally, I verified that my test user as inheritance enabled.
Since all the other mail clients work and ActiveSync works when I'm not trying to proxy through Exchange 2013, I'm not sure what else to check. Thoughts? Thanks.
Looks like enabling NTLM on the 2007 ActiveSync virtual directory fixed the problem.
Related
we have a Dynamics 365 Version 8.2 on premise in our company and our email service is based on Microsoft Exchange 2016 on premise. I Want To Install Email Router in my crm server and Then Connect it to exchange server to send and receive email from crm but my problem is there is no any option about exchange 2016 and i have been search whole the internet and there is no any good solution. when i set incoming profile to pop3 and outgoing to smtp when i click on Test Access button it show me an error at incoming but outgoing show me a success message. please help me to handle this error.
the error is:
"Incoming Status: Failure - An error occurred while executing POP3 command "". The server response was: "220 mail.modernisc.com Microsoft ESMTP MAIL Service ready at Wed, 3 Oct 2018 12:26:29 +0330".
"
I think you should use server side synchronisation:
Connect Dynamics 365 (on-premises) to Exchange Server (on-premises)
The scenario is as follow:
Connection from Windows Server 2003 to SQL Server 2005 works smoothly. Now a new Windows 2012 server which hosts the same .net web application unable to connect to the same SQL Server database, it fails with the following error:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider,error: 0 - An existing connection was forcibly closed by the remote host.)]
As it is working fine from Windows 2003, I guess the issue could be one of these:
Backward compatibility issue, as the new box is Windows 2012 instead of Windows 2003.
Network connectivity issue. However I can confirm the network path is fine as I can telnet port 1433 from the web server to the database server and also part of the error message is
A connection was successfully established with the server
Any help would be appreciated.
You need to install this hotfix for Windows Server 2003. It adds TLS_RSA_WITH_AES_128_CBC_SHA AES128-SHA and TLS_RSA_WITH_AES_256_CBC_SHA AES256-SHA cipher suites to Windows Server 2003.
Without these 2 cipher suites added to Windows Server 2003, anything from Windows Server 2008 R2 and above, will not be able to create an SSL connection to Windows Server 2003. This includes SQL Server connections, and any other connections that rely on SSL.
Why? Because Windows Server 2008 R2 and above, have no ciphers that match with what Windows Server 2003 has (the old ciphers have all been removed from new OS's for security reasons); therefore Windows Server 2003 drops the connection because there's no matching cipher available.
Microsoft Hotfix for Windows Server 2003: https://support.microsoft.com/en-us/help/948963
You need to check your SSL and TLS settings(the server only allows 1.2 and your client only supports 1.0.)
Check the following kb page for more inforamtion
TLS 1.2 support for Microsoft SQL Server
I had a very similar error message:
Microsoft ODBC Driver {Version number here} for SQL Server : SSL Provider: An existing
connection was forcibly closed by the remote host.
I found this guide and this post to be very helpful on this issue. One suggestion was to "upgrade your ODBC driver", tried that and it didn't work, most of the other discussion is around "Checking you SSL settings" in some shape or form.
What I did to resolve my issue was enable TLS 1.0, 1.1 and 1.2 on my SQL Server (in my case 2019) and then on my client systems enable ONLY TLS 1.0 and 1.1 (explicitly disabling TLS 1.2) using the toolset linked here. This seems to have resolved my issue.
What is a RDOSession.LogonExchangeMailbox server name for outlook.com ?
'Logon' with local outlook is working.
I was try redemption with my outlook.com account with RDOSession.LogonExchangeMailbox('user#outlook.com', server_name ), and got MAPI_E_NETWORK_ERROR.
Internet is on. Firewall is off.
server_name I've got from outlook account settings - may be it's wrong?
How to get the actual exchange name for outlook.com ?
UPD
MS Outlook 2010 SP1 и 2013 (both same result)
Redemption v5.12
LogonExchangeMailbox creates a temporary profile that uses plain RPC connection. Exchange 2013 and 2016 do not support RPC connections anymore, only RPC-over-HTTP or MAPI-over-HTTP. You need to use LogonHostedExchangeMailbox for that.
[I installed exchange server 2013 on server 2012r2 .... after login Exchange Administrative center got this error "500 Unexpected Error" ] Then what will i do?
After login Exchange Administrative center got this error
You may find with 2013 and exchange 2016 that if your using chrome or firefox that often now you'll get hit with a 500 error because out of the box exchange is supporting encryption cyphers that are no longer supported. It would be nice for MS to identify such things up front but the do not.
A recommendation is to download IISCrypto 2 tool which identifies crpto levels on your machine. Run the best practices template and then reboot your machine.
Often another possibility is the ssl certificate assigned in IIS to both the front and backend systems. By Default it should assign a exchange self signed cert but sometimes it may get left blank and needs to be assigned.
Those are two common 500 errors.
I am trying to configure two accounts in Microsoft outlook 2007 connected to the same exchange server/same domain. First account is configured associated with the user but when I try to configure the second account it is giving an error :
unable to connect to IMAP server.
Can anyone assist me to how to configure the same or it is supported by Microsoft outlook 2007.
IMAP accounts are supported in Outlook 2007. The error message indicates a connection problem with the server, or incorrect configuration values. You must also ensure that IMAP connections are supported on your Exchange server.