Outlook connectivity

Hi all,
Am working on a project in which i had to send mails to a list of email ids from a database. But the mail server is running a firewall and blocking any attempt to connect to it using port 25(exchange server), and am not able to connect using java mail api, it returns a -1 value when attempting to connect to port 25.
As i had configured the outlook to send mails to exchange, is there any way to create an outlook message object and send mails using outlook (in java). i can be able to find some code snippets using .net, but not in java.
can anybody provide me a link or a code snippet
Thanks in advance

I don't know if this is much help, but unfortunaly the Exchange server I had to deal with had most of the IMAP options disabled, so I had to port my request through an ActiveX control using JACOB. (http://users.rcn.com/danadler/jacob/)
Using this you could use outlook to send and recive. This is the most backwards way I possibly could do it but since I had time constraints and no real experience with the mail protocols, or the JAVAMail API, it was my first, last, and most desperate option. But since I couldn�t find anything when I searched the forum that didn�t involve using something that required money I thought why not post the code here. Big props to the JACOB team. If you still have those NET snipits you need to rewrite them but just follow the same code path. (they should use the same Outlook object model)
I suppose you could express my JAVA life with Microsoft as a J++ programmer try to go to Sun in this quote,
�Just when I thought I was out, they pull me back in.� - Michael in Godfather III
EX.)
import com.jacob.com.*;
import com.jacob.activeX.*;
class ��.
Method{
ActiveXComponent axOutlook = new ActiveXComponent("Outlook.Application");
Object oNameSpace = axOutlook.getProperty("Session").toDispatch();
// then from the NameSpace get the AddressLists, Messages, SyncObjects ect..
// Also you will have to add code to setup under the user you want to access the server with unless you preconfigure that in Outlook since you are just scripting it from outside (this may lead you to security issues, but i havent had any yet)
// I�d recommend Opening Outlook�s VB Editor and use the Object Explorer to get the right names of things since all these errors will be thrown at runtime if you mess up (Also I use the pull down menu to limit the Objects you see to Outlook)
The examples given with the JACOB package should help you figure out the JNI like calls (There is one that uses Outlook in the test folder)

Similar Messages

  • Outlook connection status window explained

    (this may be an already discussed topic, in that case feel free to answer with a hyperlink to another technet forum topic)
    Dear all,
    I am looking for a technet blog post, that explains all the tiny little details of the "Connection status" window, that is accessible if I CTRL+right click on the Outlook 2010 tray bar. I would like to receive some very professional and at
    least Level 300 explanation of all the possible information visible in this troubleshooting window. Unfortunately there are hundreds of hits for this search term, I find it nearly impossible to find that single article that is right for me.
    Richard
    PS: I think my question wasnt posted in the best topic, I would like to ask an admin to move it into the proper category under Exchange server

    Servername: pretty obvious :)
    Type:
    Directory => what is the server providding the answer to DSQUERY command / rpc proxy for authentification (therefore it is normal to see your exchange server when using outlook anywhere if you would use a direct mapi connection the "real"
    DC/GC name would show). This one is normally there twice , once for GC once for DC.
    Mail => you mailbox store server
    Public folder => if you still have a public folder store, that will identify what is the PF you are connected to.
    Interface: the local network interface used for the connection so either your wired connection or the wireless card
    Conn: HTTPS or MAPI, if you are using Exchange 2013 you will always see HTTPS. for older version, MAPI can only be on the local network.
    Status: current status of the connection type, you will see that changing if you start outlook /rpcdiag from at home.
    req/fail: number of current request/number of current request failed
    Avg Resp: delay of response (in ms) can be usefull to troubleshoot for long request (with exmon) or network bottleneck
    Authn: NTLM, KERBEROS, certificate etc...
    from the complet article about the change of outlook connectivity, here is also the explanation to the field that were not in previous outlook version (http://blogs.technet.com/b/exchange/archive/2014/05/09/outlook-connectivity-with-mapi-over-http.aspx):
    Field
    Value
    Protocol
    HTTP (v/s RPC/HTTP for Outlook Anywhere)
    Proxy Server
    Empty
    Server name
    Actual server name (v/s GUID for Outlook Anywhere connections)
    I hope that answer your question, however nowadays aside to check the current connection status of the client, you will get more usefull troubleshooting info from the exchange logs.
    Regards,
    Eric
    Please“Vote As Helpful”if you find my contribution useful or “MarkAs Answer” if it does answer your question.
    That will encourage me - and others - to take time out to help you.

  • Microsoft Test Agent appears to be blocking Outlook connectivity to Exchange

    Core Problem
    The problem I am having is that connectivity to Exchange from Outlook is blocked while executing an integration test through the Microsoft Test Agent (i.e. Outlook
    is in the disconnected state). The test is launched through Microsoft Test Manager.
    Below is the code for the integration test I am having problems with and I simplified the code as much as possible to rule out code within the integration test
    causing the problem. I also eliminated all other tests from running.
    [TestMethod]
    public void LaunchOutlook()
    Process.Start(new ProcessStartInfo(@"C:\Program Files (x86)\Microsoft Office\Office14\Outlook.exe"));
    Thread.Sleep(120000);
    I can change how long Outlook is blocked by changing the Thread.Sleep timeout. While the test is running, I can restart Outlook and Outlook is still blocked.
    After the test ends while Outlook is still running, connectivity to Exchange is restored. This happens for Outlook 2010 and Outlook 2013. If I run the integration test within a console app, Outlook connectivity is not blocked. If I run the test code manually
    through MSTest.exe, Outlook connectivity is not blocked.  The only way it’s blocked is if the integration test is executed by the Microsoft Test Agent which is the required approach for integration testing.
    More details on the problem
    Outlook is running on a machine that is part of a Hyper-V Lab with network isolation enabled. There are other machines within the same lab that have Outlook
    instances pointed against the same Exchange server. Executing the test on one machine causes Outlook connectivity issues with other machines within the same lab where the Outlook instances are pointed at the same Exchange server.
    I have small Hyper-V lab with network isolation enabled which is very similar to the lab mentioned above. The major difference is that it only has one machine
    with Outlook installed. This Outlook is able to connect to Exchange while executing the test above through Microsoft Test Manager. It is very clear that this is an environmental issue since it works in one lab and not the other. Both labs have the same Exchange
    server installed, and the same Microsoft Test Agent installed on all machines within the lab.
    I have ruled out the Outlook version as being the issue since the larger lab contains the same Outlook version as the Outlook version in the smaller lab.
    During test run
    Notice that Outlook is in the disconnected state.
    After test run.
    Notice that Outlook is not connected to Exchange.
    Environment Information
    Outlook 2010 Version: (14.0.7113.5000) SP2 (14.0.1740.5002) 64-bit or 32-bit Outlook 2013 Version: (15.0.4667.1000) MSO (15.0.4675.1002) 64-bit or 32-bit Windows
    7 Version: 6.1 (Build 7601: Service Pack 1)
    Exchange 2013 Version: 15.0 ‎(Build 847.32)‎ Windows Server 2008 R2 Version: 6.1 (Build 7601: Service Pack 1) Microsoft Test Manager 2013 Version: 12.0.31101.0
    TFS 2013 Update 4 Version: 12.0.31101.0 Microsoft Test Agent Version: 12.0.31101.0 Update 4
    Troubleshooting Steps
    I launched procmon and looked for failed TCP and UDP operations for indication of network failures and found none.
    I turned on enable troubleshooting logging in Outlook and nothing within the logs looks obvious.
    Pinging the Exchange server while the test is running still works.
    I ran the integration test through the command line using MSTest.exe and outlook connectivity is not blocked.
    Requesting Help
    Can you please help me troubleshoot this problem? I see two approaches to identifying the problem.
    Looking for differences between the two environments
    Obtaining logs or other information that would expose the core problem.
    I am open to suggestions or ideas especially if you have a different approach to solving the problem. Feel free to ask for other information related to the problem
    like logs, PowerShell commands, and registry values.
    If you are short on time, can you at least post some suggestions or ideas related to resolving this problem?
    Thanks, Keith

    After installing fiddler I figured out what the problem was. The Microsoft Test Agent was activating a proxy server which was blocking connectivity to exchange. The proxy server was activated due to having the ASP.Net Client Proxy for IntelliTrace and Test
    Impact turned on. 
    Below is a link to the article with the exact same problem.
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/ecc0b342-8e4d-436c-90c2-5f11bce1e9d8/proxy-server-settings-being-set-automatically-which-is-causing-me-not-to-be-able-to-run-manual-test?forum=vsmantest

  • Server and mailbox name check popup when opening Outlook connecting to Exchange 2010

    Everytime our users open Outlook 2007 or 2010
    this box pops up asking to verify the Microsoft Exchange server name and mailbox name. The user's information is automatically filled in and clicking ok makes the box go away but it will eventually pop up again or when outlook is closed and re-opened. 
    When "cached mode" is disabled the problem goes away (but "cached mode" is necessary for our users).
    The problem began when we deleted an old Exchange 2003 server (we are now using only Exchange Server 2010). 
    Outlook user's profile has been recreated : does not fix.  Users having that problem with Outlook 2010 dot not experience it with the OWA interface.
    How to fix that problem ?
    sti_cartem

    Hello,
    The issue seems related to the oab.
    I suggest you use EXRCA to test outlook connectivity.
    https://www.testexchangeconnectivity.com/ 
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Exchange msstd: setting in outlook connection for Outlook Anywhere

    I currently have the Exchange Provider for EXPR set to $null, however I still seem to get msstd:mail.mydomain.com set in my Outlook connection string setting on all machines. Where is this setting coming from? We do push the Outlook Anywhere settings
    via GPO and have the ProxyServer string defined set to mail.mydomain.com. The flags are set to ensure SSL is defined on the connection.
    We are in the process of moving from Exchange 2007 to Echange 2013. Will it be a problem moving from a UCC cert with a friendly name of mail.mydomain.com to a wild card SSL cert on the 2013 servers with *.mydomain.com set, if the
    "connect to proxy servers that have this principal name in their certificate is selected? I'm concerned that msstd:mail.mydomain.com  does not match msstd:*.mydomain.com?
    Thanks in advance

    Hi,
    We can run the following command to set with Ed’s suggestion:
    Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.mydomain.com
    Regards,
    Winnie Liang
    TechNet Community Support

  • Outlook connection question

    Currently we are running Outlook 2007 with Exchange 2010, I am about to install Exchange 2013 and we are not going to upgrade Office 2007 yet. So my question is can I still use a MAPI connection to exchange 2013 and NTLM? If so how would I go about that,
    Thanks.
    MSB

    Hi,
    From your description, I would like to clarify the following thing:
    RPC over HTTP Proxy component, which Outlook Anywhere clients use to connect, wraps remote procedure calls (RPCs) with an HTTP layer. In Exchange 2013, Outlook Anywhere is enabled by default, because all Outlook connectivity takes place via Outlook Anywhere.
    The only post-deployment task you need to perform to successfully use Outlook Anywhere is to install a valid SSL certificate on your Client Access server. Mailbox servers in your organization only require the default self-signed SSL certificate.
    For your reference:
    Outlook Anywhere
    https://technet.microsoft.com/en-us/library/bb123741(v=exchg.150).aspx
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2013 SP1 - Unable to test Mapi-over-HTTP Outlook Connectivity

    I've configured MAPI over HTTP in my testing environment. It is working fine. But i'm unable to test this configuration using the Powershell Test-OutlookConnectivity CMDlet.
    Outlook is working fine and is using MAPI over HTTP, so i'm pretty sure there are no configuration problems. But the CMD-let gives me the following output:
    [PS] C:\Windows\system32>Test-OutlookConnectivity -RunFromServerId <myserver> -ProbeIdentity OutlookMapiHttpSelfTestProbe
    WARNING: An unexpected error has occurred and a Watson dump is being generated: Failed to find the probe result for
    invoke now request id 1ad0cb55e6cc45c791194b34641fe3c2 and probe workdefinition id 241.
    Failed to find the probe result for invoke now request id 1ad0cb55e6cc45c791194b34641fe3c2 and probe workdefinition id
    241.
        + CategoryInfo          : NotSpecified: (:) [Test-OutlookConnectivity], InvalidOperationException
        + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Exchange.Management.Tasks.TestOutlookConnecti
       vity
        + PSComputerName        : <fqdn of my serer>
    Does anyone have a sollution for this?

    Hello @all,
    I got the same issue. The configuration is functional (Outlook connects over http). But the test-cmdlet raises this error. Is there any solution?
    Greetings from Germany

  • Outlook Connectivity Question

    Hello  All:
          In our client case they have Outlook installed in laptops, etc. But their exchange server is outside of the company. So they connect to it through some proxy using HTTP. Does it have any problem working with SBO outlook addon? My understand of it always is that outlook addon only look at outlooks, wether how outlooks connect to it's server or other servers is not a concern! Is that true? Thank You!
    Sincerely Yours

    Bo,
    You can start with this link ... https://websmp205.sap-ag.de/~sapidb/011000358700007392752004E.
    Once you are here, you will need to click on SAP Business One Products > Updates > SAP Business One 2005A > SAP Business One 2005A > Entry by Component, then either SAP B1 - SP00 Patches or SAP B1 - SP01 Patches, the appropriate B1 add-on.
    Sorry .. there is not a direct link to it and you will need your "S" number to log into the portal.
    HTH,
    Eddy

  • Outlook connection to exchange server problem

    We have a new domain and an existing exchange server. The problem is if i log in with a local computer account i can autodiscover and connect in cached mode to exchange no problem. If i then login with a domain user account the same computer (tried on other
    workstations) will fail to auto discover, fail to connect to exchange even with manual settings. I cant find anything obvious in Group policy.
    The server is setup with the latest 2013 Group policy templates with office 2013 templates
    Users not logged in with the new AD server can connect to exchange 
    Users not logged into the domain can access exchange server
    My feeling is its a local setting that is missing or needs to be changed in Group Policy but i am at a loss as to what it could be
    I have disabled roaming profiles too and it makes no difference.
    Any help would be greatly appreciated.
    Steve

    Hi,
    Sorry for my delay. According to your description, I summarize your issue to the following points:
    1. No problem when the user logs in Outlook with a local computer account in Cached mode.
    2. Can’t connect to Exchange from an cache mode enabled Outlook 2013 client when using a domain user account on the same computer automatically or manually.
    3. Can connect to Exchange from an online mode enabled Outlook 2013 client when using a domain user account on the same computer automatically or manually.
    It is right? If I misunderstand, please feel free to point it out. Additionally, I noticed that the server is setup with the latest 2013 Group policy templates with office 2013 templates. Please confirm
    if the Outlook cache mode is disabled by OTC or GPO. If there is following registry key applied on the machine:
    Software\Microsoft\Office\15.0\Outlook\Cached Mode
    Meanwhile, please try to install an Outlook 2013 with a fresh ISO file(Don’t use any template such as OCT template), see if the Cached mode Outlook can connect to Exchange server.
    Waiting for your updates.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Outlook Connection

    Hi,
    MS Outlook 2010 was working fine on my Windows Server 2012 with Exchange Server 2013 installed on a virtual machine up until a couple of weeks ago.  Each time I launch Outlook, I get the error "The connection to Microsoft Exchange is unavailable. 
    Outlook must be online or connected to complete this action."  I have the option of clicking "OK" and if I do, I get the Microsoft Exchange dialog box which shows boxes: 1) the "Microsoft Exchange
    Sever" with the following text inside of it "[email protected]" and 2) the "Mailbox" with the following text inside of the box "=SMTP:[email protected]
    I tried many things that are suggested online to fix the issue but to no avail.  Any step-by-step to fix the issue would be greatly appreciated.
    Thanks,

    Were any changes made recently in your environment either to Group Policy or the Exchange Server?  Also do you have a load balancer in place?  Can you try going directly to an Exchange Server?
    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

  • Exchange 2013 Office 365 Hybrid Cloud On-Premise Outlook Connection Problem

    Hi Everyone,
       We are required to migrate FROM the cloud TO an on-premise Exchange 2013 server.  We set up a trial of Office365 and linked our test domain to that account.  The test domain mimics our current domain, but ends in .net instead of .org.
     We set up a test Exchange 2013 server with a few database servers.  Internally, we can connect without issue (Outlook).  We mapped our test CAS to face the Internet, and can access what we need without issue.  We also set up the Hybrid
    configuration on both the Exchange 2013 and Office365 servers.  We have validated that DirSync works, and migration can occur up to the cloud and back down to the on-premise server.
    Now, here is the issue:
    We have our DNS records still pointing to Office365, so when we add an Office365 mailbox to Outlook (internal to the network or outside the network) we see absolutely no issues.  We migrated a mailbox today to our on-premise server, but upon doing so,
    can no longer connect to, or add, that mailbox to Outlook.  When we put this integration in to effect for production, we want to be able to migrate mailboxes on-premise from the cloud, and we want to make sure users can still access their mailboxes.  This
    also goes for distribution groups, conference rooms, etc.
    I see that most suggestions say to change your DNS record to point to the on-premise Exchange server, which is great, but after doing so Office365 accounts experience the same issue as above.  We NEED to make sure that when we batch migrate, the users
    DO NOT lose connectivity to their accounts.  We need both Office365 accounts and Exchange on-premise accounts are accessible internally and externally.  As an extra tid-bit, we HAVE configured Outlook Anywhere on Exchange 2013, but see no difference.
    Any thoughts on this?  Office365 and Exchange 2013 see eachother and recognize that the hybrid environment is set up good, but it appears we are missing some configurations.  Currently, we have a CNAME record points our autodiscover to autodiscover.outlook.com.
    Any help would be MUCH appreciated.  Thanks!
    Dan

    Hi,
    Here is an article on Move mailboxes between on-premises and Exchange Online organizations in 2013 hybrid deployments, for your reference:
    http://technet.microsoft.com/en-us/library/jj906432(v=exchg.150).aspx
    I want to make sure OWA works well with the moved mailbox.
    To use CNAME based autodiscover method, we need to have all domain names present in a SAN certificate.
    With Exchange 2013 CU1, we now have the option of adding multiple SMTP domains to Exchange Federation/Hybrid configuration and we can specify which of these domains should act the "autodiscover" domain.
    To configure an SMTP domain as the autodiscover domain, you can run following command:
    Set-HybridConfiguration -Domains "domain1.com, domain2.com, domain3.com", "autod:domain.com"
    More details, please refer following blogs:
    http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part11.html
    http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part12.html
    Disclaimer:
    Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
    that you completely understand the risk before retrieving any suggestions from the above links.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Outlook Connecter Install Problems

    Hi there,
    I have just set up a trial for the Calander Server and it is working a treat through the web interface but I am having problems with the Outlook Connector.
    The problem seems to spring from the fact that I am not using (and do not intend to use) the Sun Messaging Server for email. My setup is:
    Sun Calendar Server (machine 1)
    Sun Directory Server (machine 2)
    Exim Based IMAP / SMTP server (machine 3+ as it is scaled and redundant)
    When you use the connector deployment software it asks you for your incoming and outgoing mail servers and LDAP/Address/Calendar servers.
    So, I add the Exim mail platform in for the incoming and outgoing mail servers and the Dirctory or Calendar server to the others as appropriate.
    When I then try to install the connecter I get the error "Logon information for new mailboxes is invalid" .. even though they are the same as I have made the two users match exactly for testing. I can see the system trying to log on via IMAP and failing for no obvious reasons as the IMAP login works perfectly well.
    Any ideas? How can I get the outlook connector working without using the Sun Messaging Server? Will I need to install the messaging server and not use it to install the connector (seems like a lot of hassle).
    Thanks
    Josh

    Well, I think I've tried all of the above. Initially, I uninstalled the Office2013 preview and installed the released version. This is where it crashed. I have since performed a fresh install of Windows 8 Enterprise along with Office 2013. Now, when I create
    my IMAP account (to a personal self-managed email account on a Linux server) there are two fundamental problems:
    1. Even though I can see all of my IMAP folders when I use the IMAP folder tool in Outlook, no matter what I do, I can not get the folder listings in the Outlook sidebar to match my subscribed folders. I have an extensive list of folders I use to store my
    mail, and it flat-out is inaccessible to me. I get: inbox, drafts, sent, trash, drafts, Junk E-mail5(this computer only),
    October 2012, October 2012.lock, outbox,spam, Trash, Trash, Trash, Search Folders   (bold/italics are folders actually known to be on my server) Note that the drafts and trash folders show up multiple
    times. This is not what my subscribed folder list says I should see there.
    2. Outlook will not automatically sync my IMAP inbox. When I start Outlook, it syncs my Exchange Account and Outlook.com account just fine. Nada on the IMAP. I can even tell OUtlook to send/receive and it still does not update. If I click on the first trash
    folder I get a message telling me that Trash is syncing, and if I then switch to my IMAP inbox, it starts to sync and seems to work after that.
    I'm pretty clearly convinced that MS broke IMAP big time. It always had its quirks in the past, but this one is busted.

  • Microsoft outlook connection with 4.6C

    Dear All,
    Does anyone has a step by step procedure guide on " How to connect SAP 4.6C with Microsoft Outlook" for sending and receiving emails.
    I have done it with ECC6 but for 4.6C is very different.
    Regards
    Farooq

    Is not that different.. you actually have to install SAP Exchange connector.
    Follow this guide.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVCOMMSX/BCSRVCOMMSX.pdf
    Regards
    Juan

  • Outlook connectivity and mail flow issue on Exchange 2010 3 node DAG

    Hi,
    I have 3 node DAG, 2 (NODE A, NODE B) in Production site and 1(NODE C) in DR site. but just 1 AD Site.
    when I have the active databases on NODE B, everything works fine. no issues to report.
    but when I move the databases on NODE A, outlook gets connected with trying to update folders. Furhter, emails will be in outbox and no new emails will be delivered to the users. After an hour or so emails get delivered from outbox.
    Even after supplying the credentials OWA doesnt login. just tries to load.
    No issues when I move the servcies on NODE C.
    ANy idea what could be the issue?
    Thanks,
    Vinod

    Hi Vinod,
    According to your description, there is one-hour delay in the process of sending and receiving emails.
    To check if it’s caused by Autodiscover service, we can use the tool Test Email AutoConfiguration:
    1. Hold CTRL and Click the outlook Icon in the system tray and select “Test Email Auto Configuration”.
    2. Deselect the “Use Guessmart” and “Secure Guessmart Authentication” and click Test.
    3. Check SCP value returned
    For more information, please refer to the following article:
    http://blogs.technet.com/b/exchdxb/archive/2012/05/10/troublshooting-autodiscover-exchange-2007-2010.aspx
    http://support.microsoft.com/kb/2663435
    http://support.microsoft.com/kb/262052
    If connectivity is well, the issue is mostly likely caused by the Exchange mail submission service.
    We can check if the service work properly. And the issue may be not related to the Hardware Load Balancer. Because the emails are stuck in the client side.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange Server 2013 Service Pack Upgrade - Outlook connectivity issue

    Hi,
    After upgrading to Exchange Server 2013 service pack 1, we are unable to connect via Outlook 2010 or Outlook 2013. Outlook Web Access is working fine though. We have followed all the instructions, and have applied Outlook upgrades, but the issue remain the
    same. Outlook was working fine before the upgrade.
    Have we missed out something. I would highly appreciate if someone can help out? I'm not sure if this is the known issue as I can't seem to find anything on the internet.
    Already applied the transport fix.
    Thanks in advance!

    Hi,
    According to your description, your Outlook 2010 and Outlook 2013 come across the connectivity issue.
    To narrow down the issue, I’d like to recommend the following troubleshooting:
    1. Check if the issue happens on all Outlook users
    2. Check the Outlook Anywhere connectivity by using ExRCA:
    https://testconnectivity.microsoft.com/
    Additionally, MAPI over HTTP is only supported when you use Outlook 2013 sp1 and Exchange 2013 sp1 at the same time. Since the issue also happens on Outlook 2010 client, we can firstly try the above troubleshooting.
    If you have any question , please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Outlook Connectivity / Exchange 2010 Coexistence Scenarios

    Hello,
    I recently migrated to Exchange 2013, autodiscover.domain.com and mail.domain.com are pointing to CAS 2013 for external and internal access. For EX013 users, Outlook establishes connection with both CAS 2010 and CAS 2013 which is fine. For EX2010 users,
    Outlook establishes the connection only with CAS 2010 for both internal and external access. My understanding is that CAS 2013 should proxy the connection to CAS 2010, but it doesn't and also after the migration I have to remove and add the profile again for
    the changes to take effect for the migrated users. I haven't changed the namespaces, its the same. Any suggestions would be much appreciated.

    Hi,
    Your understadning is correct. Since only Exchange 2013 is Internet-facing, CAS2013 would proxy all requests for Exchange 2010 external user accessing.
    Please make sure the External URL in Exchange 2010 services are all set to $Null and Outlook Anywhere is enabled with the external host name pointed to mail.domain.com. Then the external Exchange 2010 user would connect the Autodiscover service
    with autodiscover.domain.com successfully. The other services such as EWS, OOF and OAB request would be send to Exchange 2013 then proxy to Exchange 2010.
    For more infromation about the connectivity in Exchange 2013 coexistence environment, please refer to:
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Regards,
    Winnie Liang
    TechNet Community Support

Maybe you are looking for