Hi, I have some trouble connecting the Outlook to our Exchange Server. On that same Mac I configure the Mac Mail to connect to Exchange and went OK. I configure the Outlook using the exchange connection and cannot connect, user account (username password) is correct but still cant connect history: few days back it was connected but recently for unknown reason its just stop synchronizing.
How to Setup Outlook for GoDaddy e-mail accounts. Outgoing mail server (SMTP) smtpout.secureserver.net IMAP Incoming mail server imap.secureserver.net. May 3, 2017 - Requirement for Microsoft Outlook 2011 for Mac configuration. To connect your atmail 7 cloud account to Microsoft Outlook 2011 for Mac you will need. Note: Connection via Secure Server Settings is highly recommended.
![Conver Conver](/uploads/1/2/5/6/125616065/990546440.png)
I tried comparing the outlook configuration on the working MAC it was the same but still can't connect. We tried reinstalling the Office, do some Office Update but still same.
Any idea shared is highly appreciated. Regards, mobdoc. Ahh,.local rears its ugly head again.local is not a valid TLD, and Mac OS X handles it differently than Windows. Here are Microsoft's articles recommending against the use of.local 'Using single label names or unregistered suffixes, such as.local, is not recommended' The dsachetuil command should be as shown below, so I apologize for that typo on my part (I've fixed it above in my prior replies). Dsacheutil -q host -a name fqdn.ofyourserver.com or in your case dsacheutil -q host -a name server.domain.local. Hi Oliver - What version of Exchange are you using and what OS X version?
Microsoft has some useful recommendations for troubleshooting which might apply to you: Outlook 2011 also had issues with corrupted identities and databases which would require using the DB Utility to clean up or a completely new install and setup removing all previous preferences files. Some of the issues you reported were fixed in an update for Mavericks and Yosemite a while back. You can use this free utility as an Administrator to test Exchange connections.
As an FYI - If you're an Office 365 user, you can get access to Outlook 2016 for Mac which my team reports is performing well. The standalone version of this will be available to the public in September. Hope this information helps you out!
Please let me know if I can be of further assistance.. Hi Megan, Thanks for your reply, yes its Yosemite 10.10.2 and were using Exchange 2007 SP3, we have a couple of Mac users using Outlook 2011 and they are working fine connecting to our exchange server except this one. We tried reinstalling a couple of times, update the Office, uninstall the office and install back again, and once we tried adding account in outlook using exchange connection we got yellow icon and account is not successfully added to outlook. Note: it is same configuration we did to other Mac Users who is using Outlook, users credentials are correct because we can login using that account through OWA. Regards, Oliver.
There is a lot of information being tossed about but much of it is simply not on point, sorry. For an Exchange account with Outlook for Mac never ever ever do a database rebuild.
I'm speaking from many years of experience with this. A rebuilt Outlook for Mac database will fail again within days to a couple weeks, it will. Because Exchange email is all housed on the server, one should completely replace the existing Identity & newly configure Outlook for Mac & let the email sync from the server. Outlook 2016 requires Exchange 2010 or later so it's not an option for Oliver.
Alphnix: Your suggestion is only valid for a mail client that uses ActiveSync. As I have already noted above Outlook for Mac does.not. use ActiveSync, it uses Microsoft's EWS. Oliver, please revisit & respond to my reply above. Ahh,.local rears its ugly head again.local is not a valid TLD, and Mac OS X handles it differently than Windows.
Here are Microsoft's articles recommending against the use of.local 'Using single label names or unregistered suffixes, such as.local, is not recommended' The dsachetuil command should be as shown below, so I apologize for that typo on my part (I've fixed it above in my prior replies). Dsacheutil -q host -a name fqdn.ofyourserver.com or in your case dsacheutil -q host -a name server.domain.local. Thank you for the additional information on the versions of Outlook and OS, mobdoc.
Some more information for you from my team. Have you tried to see if Apple Mail will connect via the “Exchange” active sync setup? Also you can add a test user account on this particular Mac and attempt an Outlook setup to see if there are any changes.
I believe, that despite uninstalling the software on previous attempts some remnants of the Microsoft DB or preferences were left behind. By setting up a test user OS X account and trying the Outlook setup again we can eliminate some possibilities. The Apple Mail setup could also shed some light..
URL: This article is intended to assist users in solving database corruption cases in Outlook 2011/Outlook 2016 for Mac when connected to an Exchange mailbox. Sometimes Mac users report that Outlook 2011 /Outlook 2016 for Mac is not syncing properly (or syncing quite slowly, freezing frequently) with Exchange. The problem usually is not a connectivity issue between the mail client and the mail server, but rather a local Outlook database corruption. Keep your mail sorted into folders In many cases, Outlook does work properly with folders as large as 10.000 items and more, but decreasing the folder size can improve the performance drastically, and generally this is the first troubleshooting step to be done in a case of slow/freezing Outlook client. You can move the items using client.
Read the following Microsoft Office articles for more information:. Keep the number of subfolders in Inbox and Sent Items to minimum Instead, it is preferable to create new folders on top level.
The same level as Inbox and Sent Items are for better performance. Move folders and multiple items in OWA Moving big folders or a lot of items at once in desktop Outlook client takes significant time to synchronize with the server. Moving a lot of items can often cause disruption in the mailbox if the connection fails for a moment, for example, due to high network usage or your computer’s CPU load. On the other hand, changes made in occur directly on the server and thus happen instantaneously. Clear affected folder's cache in case of content mismatch If you see that Outlook 2011/Outlook 2016 for Mac and folders don't match, you may want to reload the cache to fix the issue. Read the Knowledge Base for more information. Re-create the Microsoft Office Identity If the Outlook 2011 client becomes slow and unresponsive, or stops syncing completely, while Outlook Web App and/or other clients work fine, it is most likely an indicator of corrupted Outlook database. In this case, it is recommended to rebuild, or remove, and re-create the Microsoft Office identity or Outlook Profile on Outlook 2016 for Mac. If you do not have any other mailboxes in your Outlook profile, we recommend removing and re-creating the identity.
Please read the following articles and for more information.