Mac can't connect to exchange server

Hello everyone,
I'm having an issue with our mail environment.
Windows users and phone users (iOS and Android) are working
But when I try to configure a Exchange mailbox it doesn't work.
It says: Username and password is incorrect.
Even with Domain in front of it and a password reset, it still doens't work.
We tried mail for mac, outlook for mac 2011 and some other clients.
any fixes/idea's ??

I tested it with my Windows Computer at home, which configures it after I manually set Outlook Anywhere and put it the information. So Autodiscover is working half I guess?
My colleague also tested it at home, with a MacBook but sadly enough it doesn't work.
Last week it kept asking for username and password, but that is somehow fixed.
It now just accepts the username and password, and tries too accept. Normally you'll have a green dot if it is succesful but it stays orange and can't connect even though it seems to verify the username and password.
I think we are close, but can't find anything in the logs so far.
PS: I opened an other topic, but I don't know if it's related to this problem. 
Outlook Anywhere Autodiscover
SOLUTION: Since we were brainstorming yesterday, we found out the server were not in such a good shape as we thought. All HUB/CAS Server had a restart pending, tons op updates, so we fixed that first.
After that we found out, 1 of the HUB/CAS server didn't have Windows Auth enabled in EWS.
We enabled the Windows Auth, and the Mac OSX clients were connecting after like 10 minutes.

Similar Messages

  • Hello.....after updating to Yosemite, i can't get my exchange mail to work.  It keeps saying can't connect to exchange server and asks for my password.  My mail is still working fine on android phone and ipad2.  Can someone help?

    Hello....after updating to Yosemite my mail isn't working .  Keeps saying can't connect to exchange server and asking for password

    I am having this exact same problem with my gmail account. Hopefully someone will have a remedy.

  • Mac mini wont connect to exchange server

    i cannot connect my mac mini to my office exchange server. i was able to connect my ipad and iphone, but cannot figure out how to connect the mac mini using the same techniques. i unchecked autodiscover and still no luck

    Hmm, the fact that that link didn't work may be thekey, here's that page anyway...
    By Erik Eckel
    October 25, 2011, 6:00 AM PDT
    Takeaway: Erik Eckel addresses a common problem — trying to get Lion Mail connected to Exchange servers. Here are some tips for how to do it.
    Many technology professionals become frustrated when connecting Macs to Exchange servers. The frustration typically results from a misunderstanding of Microsoft Exchange technologies. Here’s what Lion users and administrators should know.
    Exchange Web Services is the key
    When connecting a Mac OS X Lion system, the email server should be running Exchange 2007 or 2010. Microsoft Exchange 2003 does not leverage the newer Exchange Web Services (EWS) introduced with the 2007 platform. iPhones and iPads leverage ActiveSync technology, which is one of the reasons those mobile devices typically work with Exchange 2003 servers.
    While there are workarounds for connecting Lion systems to Exchange 2003 servers, including leveraging POP3, IMAP or browser-based OWA technologies, those solutions are less secure and support fewer capabilities. Anyone considering such options should remember that Microsoftsuspended mainstream support for Microsoft Exchange 2003 in April 2009. Organizations still dependent upon Exchange 2003 infrastructure should already be planning if not implementing their Exchange 2010 migrations.
    Connecting Lion Mail
    Assuming an SSL certificate is installed, DNS A and MX records are properly configured, and the organization’s firewall passes the appropriate traffic, you can follow these steps to connect Mac OS X Lion’s Mail application to an Exchange 2007/2010 server:
    Open Mail.
    Click File and select Add Account.
    Specify the user’s name in the Full Name field. Enter the email address and type the password associated with the user’s Windows/Exchange user account, then click the Continue button. Mail will search for the associated email server; users may have to click Connect if Mail reports it cannot verify the identity of the email server.
    When the Incoming Mail Server screen appears, select Exchange from the Account Type drop down menu.
    Within the Incoming Mail Server field, specify the email server, providing again the user name and password.
    Check the Contacts and Calendars boxes if you wish also to synchronize those items, then click Continue.
    If SSL is to be used, check the Use Secure Sockets Layer (SSL) box on the Incoming Mail Security screen and then click Continue.
    An Account Summary will appear. Review the information entered to ensure accuracy, then click Create.
    Connecting Outlook 2011
    Microsoft Outlook 2011 users can configure the application to connect to properly configured Exchange servers by following these steps:
    Open Outlook 2011.
    Click Tools and select Accounts. If an account already exists, click the + icon and select Exchange. Otherwise, click Exchange Account from the Add an Account screen.
    Enter the email address within the E-mail address field, then specify the authentication method. The most common method is likely the default user name and password configuration. Once you supply the requisite information, click the Add Account button (note Outlook selects the Configure automatically box by default).
    If Outlook is unable to automatically configure the account, you will need to specify the server address, then click Add Account.
    The Accounts screen will then appear. If additional settings must be configured, click the Advanced button. From the Server tab, you can override and update ports and change the server address, among other options. The Delegates and Security tabs, meanwhile, enable configuring delegate users, digital signing, and encryption certificates.

  • Can't connect to exchange server after 1/4/2011 am update - anyone else?

    Woke up this am and phone is unable to connect to exchange server for email. Last email received was @4:35am. I've reentered my password to confirm and exchange is working fine on Desktop. Any suggestions?

    I'm pretty sure that the combination is right. On my macs everything works fine. Is there another reason why the exchange server could reject the iPhone? Similar to the 3.1 problems with the hardware encryption?

  • Can't connect to Exchange Server 2007

    Hi,
    I have problems to set everything up, probably someone has a solution for this problem? After entering my account data the autodiscovery fails (see log below, the password is not wrong :)) I have to enter the server settings manually. Apple Mail was able to use autodiscovery to set everything up.
    So I entered the correct server settings, but the iPhone can't establish a connection to the server.
    As already said, I'm using Exchange 2007, and an iPhone 3G 3.0.1. Anyone had this problem before?
    Sat Oct 3 01:25:00 unknown Preferences[224] <Warning>: EAS|EAS Protocol Manager set to ASProtocolUnknown
    Sat Oct 3 01:25:05 unknown Preferences[224] <Warning>: EAS|Root node is expected to be an Autodiscover element
    Sat Oct 3 01:25:05 unknown Preferences[224] <Warning>: EAS|Autodiscovery task encountered an error: Error Domain=DAErrorDomain Code=1 "Operation could not be completed. (DAErrorDomain error 1.)"
    Sat Oct 3 01:25:05 unknown Preferences[224] <Warning>: EAS|Autodiscover task failed with status 59 and error Error Domain=DAErrorDomain Code=1 "Operation could not be completed. (DAErrorDomain error 1.)"
    Sat Oct 3 01:25:05 unknown Preferences[224] <Warning>: EAS|Bad password error received.
    Sat Oct 3 01:25:05 unknown Preferences[224] <Warning>: EAS|Received bad password response. Optimistically trying one more time
    Sat Oct 3 01:25:05 unknown Preferences[224] <Warning>: EAS|Autodiscovery task encountered an error: Error Domain=ASHTTPConnectionErrorDomain Code=401 "Operation could not be completed. (ASHTTPConnectionErrorDomain error 401.)"
    Sat Oct 3 01:25:05 unknown Preferences[224] <Warning>: EAS|Autodiscover task failed with status 6 and error Error Domain=ASHTTPConnectionErrorDomain Code=401 "Operation could not be completed. (ASHTTPConnectionErrorDomain error 401.)"

    I'm pretty sure that the combination is right. On my macs everything works fine. Is there another reason why the exchange server could reject the iPhone? Similar to the 3.1 problems with the hardware encryption?

  • Outlook 2013 can't connect to Exchange server

    Trying to set up Outlook 2013 on my new work laptop. I have the correct Exchange server name  and emaill address, but get the error message "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this
    action." In fact, I'm online and connected to the internet. When I open up a "CMD" window, I can ping the server, so I know my computer can see the server, only Outlook can't. My laptop is running Windows 7, 64-bit. The Office/Outlook 2013 is
    64-bit as well.  I've tried with my firewall both on or off, and it doesn't seem to make any difference.
    btw - I have essentially the same configuration set up on my iPhone, and can send and receive emails with no issue.
    Does anyone have any suggestions on how to resolve this issue.

    Hi
    As per the information and details provided by you, to connect the Outlook 2013 from Exchange server please follow these steps: -
    1. Open Outlook 2010 or Outlook 2013. If the Outlook startup wizard appears, on the first page of the wizard, click Next. Then, on the Email Accounts page, click Next to set up an email account.
    If Outlook startup wizard does not appear, on the Outlook toolbar, click the File tab. Then, just above the Account Settings button, Click Add Account.
    2. On the Auto Account Setup page, Outlook may automatically fill in the Your Name and Emil Address settings based on how you are logged on to your computer. If the setting is filled in and they are correct, click Next to
    have Outlook finish setting up your account. If the settings on the Auto Account Setup page are not filled in or are not correct, do the following steps: -
    • If the settings on the Auto Account Setup page doesn't fill in, type the correct settings based on the information that was provided to you by the person who manages your email account.
    • If the name in the Your Name box is not correct, you may need to reset the options on the Auto Account Setup page before you can edit your name. To reset the options, click the option button next to manually configure
    server settings or additional server types, and then click the option button next to Email Account. 
    3. After you click Next on the Auto Account Setup page, Outlook will search online to find your email server settings. You will be prompted to enter your user name, password during this search. Make sure that you enter your
    full email address as your user name.
    If Outlook is able to set up your account, you will see the following text: Conguratulations, Your email account is successfully configured and ready to use. Click Finish.
    I hope this information will be helpful for you.
    Thanks and regards
    Shweta@G 

  • Can't connect to Exchange server.

    I am having trouble connecting my Outlook 2013 to my work Exchange server. I am fairly certain the problem is that the certificate from my work account is the issue and that Outlook 2013 doesn't trust it. I have turned off Windows Firewall, so that shouldn't
    be interfering anymore. I'm having the same trouble getting my Samsung Galaxy S4 to connect as well. I think the real trouble may lie in the expiration date of the certificate. Is there any way to create an exception or override Outlook so that I can
    connect to my work server? 

    Hello,
    Based on your description if Exchange certificate has expired you should buy new certificate or deploy your own CA and issue certificate for your server.
    Hope it helps,
    Adam
    CodeTwo: Software solutions for Exchange and Office 365
    If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

  • Outlook Can't connect to Exchange Server

    Dear All;
    I install the exchange server 2013 in our Environment with basic configurations, it was work correctly in out look and OWA.
     In this period I install  outlook Clint  and connect to exchange correctly , Then I log in to Exchange Administrations Center , then make some changes , after that i can't connect  outlook Clint  to exchange server  while I
    can connect to OWA but with error message related to Certificate.(Kindly check the screen shoot of error )
    Kindly help me to solve this issue I beginner  with Exchange.

    Here are the default permissions for the Exchange virtual directories:
    http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
    I found that the print in the screenshots was not clear - maybe it's me or my browser.
    What names do you have on the certificate?
    exchange.abc.local
    Is that it?
    Is this a self-signed certificate? Or did you get it from Digicert, VeriSign, GoDaddy or some other 3rd party authority?
    Regardless, the URLs for the virtual directories, OWA in particular, have to match what is on the cert.
    So OWA might be:
    https://mail.exchange.abc.local/owa
    Other possibility:
    https://webmail.exchange.abc.local/owa
    Since exchange.abc.local is what you have on the cert, the URL has to configured as shown above. You can use "mail", "webmail" or whatever just before (once again, as shown above) but you have to make sure that is what the users enter
    when they attempt to access email.
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Can't connect to Exchange Server - Upgraded Policies

    My company just upgraded their policies and said that with an iPhone it will auto encrypt but they had no idea about a Windows phone.  I get an error code 86000C2B saying certain policy's need to be enforced but no solution is given?  Help

        vanhoogy, I saw your distress call in this post. I can assist you with this corporate e-mail issue. Did your employer provide you with the new port settings information? These port settings should be provided by the service provider or administrator. Please be advised that you must insert the correct username/password to verify that a you are authorized to send and recieve messages using that particular server. If the provider uses a username / password combination to authenticate senders, the combination must be valid for both the incoming and outgoing servers. Otherwise, attempts to add your work e-mail address will fail.
    Are you attempting to sync to an Exchange 2010 mail system, Outlook Web App, Outlook Anywhere or ActiveSync/EAS with a Windows device?
    LasinaH_VZW
    Follow us on Twitter @VZWSupport

  • Outlook Mac Loses Connection to Exchange Server

    Hi All,
    I've had this problem pretty since deployment a couple of weeks ago, so I'm hoping some one can point me in the right direction.  I'm running Exchange 2013 on a Server 2012 Standard box with the DC running on a different box, every thing up to date.
    Mac clients running Outlook 2011 (14.4.2).
    Periodically throughout the day, Outlook loses connection to Exchange server.  After several minutes, it will connect back up, and seems to operate normally.  During the down time, I am able to connect to OWA, and ActiveSync seems to work as well.
    If I run the Remote Connectivity Analyzer while Outlook is responding, I get no errors and the "Connectivity Test Successful" message.  However, if I run it while Outlook is NOT responding, I get the following:
    Exchange Web Services synchronization, notification, availability, and Automatic Replies.
    Not all tests of Exchange Web Services tasks completed.
    Creating a temporary folder to perform synchronization tests.
    Failed to create temporary folder for performing tests.
    Exception details:
    Message: The request failed. The operation has timed out
    Type: Microsoft.Exchange.WebServices.Data.ServiceRequestException
    Stack trace:
    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
    at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
    at Microsoft.Exchange.WebServices.Data.ExchangeService.BindToFolder[TFolder](FolderId folderId, PropertySet propertySet)
    at Microsoft.Exchange.Tools.ExRca.Tests.GetOrCreateSyncFolderTest.PerformTestReally()
    Exception details:
    Message: The operation has timed out
    Type: System.Net.WebException
    Stack trace:
    at System.Net.HttpWebRequest.GetResponse()
    at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
    at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
    Elapsed Time: 100141 ms.
    Nothing I've attempted to do so far as had any meaningful impact, and I am fairly new to Exchange.
    Following the adice I've seen online so far, I've:
    I've made sure the auto discover in DNS points to the Exchange server.
    I've disable auto-discover on the client, manually adding accounts, tried using their FQDN, local IP, LAN IP.
    I've made exceptions to the proxie on the client.
    Just not sure where to look next?  Appreciate any advice out there.
    Thanks,
    Michael

    Hi,
    Before we go further, I'd like to confirm if your Outlook clients can work well when your Outlook MAC clients come across the issue.
    If the issue only happens on your Outlook MAC clients, we can check the IIS log and confirm if there is any error releted to EWS. And you can recreate your EWS virtual directory to have a test.
    Thanks, 
    Angela Shi
    TechNet Community Support

  • Why can't I connect to Exchange Server 2003? I'm using OS Lion. My iphone connects, what am I doing wrong?

    Why can't I connect to Exchange Server 2003? I'm using OS Lion. My iphone connects, what am I doing wrong?

    the iPhone uses active sync. Desktop clients do not. Desktop clients use another exchange protocol (which i can't remember as i'm not a microsofty).
    Just because you can access via active sync doesn't mean you can access it by other methods, and vice versa.

  • Database error #2002 can not connect local mysql server to socket through '/var/run/mysqld/mysqld.sock'(2) on mac os x 10.9.2

    Dear Fellas:
    I received "database error #2002 can not connect local mysql server to socket through '/var/run/mysqld/mysqld.sock'(2)" on mac os x 10.9.2.
    mysql info:
    ps -ef | grep mysql
        0    66     1   0 11:06AM ??         0:00.04 /bin/sh /usr/local/mysql/bin/mysqld_safe --user=mysql
       74   225    66   0 11:06AM ??         0:02.50 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysql/lib/plugin --user=mysql --log-error=/usr/local/mysql/data/Chuans-MacBook-Pro-2.local.err --pid-file=/usr/local/mysql/data/Chuans-MacBook-Pro-2.local.pid --socket=/var/run/mysqld/mysqld.sock
      501   952   947   0  3:52PM ttys000    0:00.00 grep mysql
    Please help!!

    Fascinated and guessing:
    Something related to sock(2) because that's not part of your copied info. I'm thinking you've doubled up on sockets and the second socket doesn't exist, meaning you should be connecting to the first socket "mysqld.sock" whether automatic or not.
    I've only used GUI tools on purpose, so does this mean you've already got MySQL running and you tried to launch it again manually? Perhaps you already have one instance of a db and you're trying to launch a second instance, and the two can't coexist with a single user local db?
    Assuming this is all local, I'd shut down the db service and restart it, out of hand. I've seen similar messages when I set the db to start up on boot, and it didn't finish shutting down when I tried to restart it manually. Usually the GUI won't let me turn it on because it reports it's already running, but in that case it hadn't finished performing what the GUI was reporting.
    Just speculating.

  • What is required to Exchange integration work - (Can't connect to Exchange Web Server)?

    Hi guys,
    We have just 'beaten' our Lync installation until it decided to work with mobility, however the clients (IOS) complain that it "Can't connect to Exchange Web Server". Entirely possible its our own fault!
    My question is:
    What exactly do I need to configure to make this work?
    DNS records,
    Firewall rules,
    etc. 
    We are running:
    Exchange 2010 on-premise
    TMG 2010
    Cheers
    Dave
    Dave

    Hi Dave,
    The Lync 2010 mobile client for iPhone and iPad has a Meeting tab that lists meetings for the day from the Exchange calendar.
    The client uses simple Exchange Autodiscover processes to determine the location of the Exchange server of the user who is signed in. The SIP Uniform Resource Identifier (URI) of the user is used in the attempt to discover the Exchange Web Services (EWS) endpoint.
    However, if the user’s SIP URI and email address are different, the Autodiscover process will fail, the Meeting tab will be blank, and Exchange Unified Messaging (UM) voicemail in the Phone tab will not sync.
    For disjointed email and SIP URIs, the Lync 2010 mobile client for iPhone and iPad lets the user specify a different set of credentials for Exchange integration. For the Exchange Autodiscover process to work correctly, the necessary DNS records must be available.
    To confirm that Autodiscover is working, use Microsoft Remote Connectivity Analzyer at http://www.testexchangeconnectivity.com (http://www.testexchangeconnectivity.com/)
    In addition, please also refer to this document
    Lync 2010 Integration. Hope helps.
    Noya Liu
    TechNet Community Support

  • Outlook 2013 Can't connect to Exchange or ping Exchange server.....Very Weird!!!!

    The CEO of one of our clients has 2 workstations we'll call them Old and New Dells.
    He'd RDP into his new Dell and Outlook will not connect to Exchange and eventually stops responding. His old Dell work just fine.
    We restarted the new Dell and the problem persists. I tried pinging the Exchange server and don't get a response. I ping the other servers in the network and I get responses from all of them. On the new Dell I tried going OWA and the website failed to load.
    The old Dell has no such issues. Not sure what's going on and could use some guidance. I tried disabling the firewall and that didn't work. It looks like it's only affecting his new Dell, I have not heard of any other users reporting problems. Any ideas?

    Hi,
    Since you can't ping the Exchange server, it's more likely a server side issue. This forum is for general questions and feedback related to Office client side issues, it's better to post your question to the Exchange server forum to get further assistance:
    https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
    Steve Fan
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Lync 2010 iPhone - Can't connect to Exchange web server. you can try again later

    Hi there,
    I installed Lync 2010 mobility, and works fine, but iPhone users have a :
    Can't connect to Exchange web server.
    you can try again later
    Now does this have anything to do with it? And how do i fix it? I searched but nothing relevant

    Total server discovery time: 0.3 seconds
    Starting Lync server autodiscovery
    Please wait; this test may take several minutes to complete...
    Starting automatic discovery for secure (HTTPS) internal channel
    Server discovery has completed for https://lyncdiscoverinternal.contoso.com/.
    Automatic discovery results for https://lyncdiscoverinternal.contoso.com/
    Access Location                          : Internal
    SIP Server Internal Access               : server.contoso.com
    SIP Server External Access               : sip.contoso.com
    SIP Client Internal Access               : server.contoso.com
    SIP Client External Access               : sip.contoso.com
    Internal Auth broker service             : https://server.contoso.com/Reach/sip.svc
    External Auth broker service             : https://lync.contoso.com/Reach/sip.svc
    Internal Auto discover service           : https://server.contoso.com/Autodiscover/AutodiscoverService.svc/root
    External Auto discover service           : https://lync.contoso.com/Autodiscover/AutodiscoverService.svc/root
    Internal MCX service                     : https://lync.contoso.com/Mcx/McxService.svc
    External MCX service                     : https://lync.contoso.com/Mcx/McxService.svc
    Internal UCWA service                    : service URL is empty in the discovery response
    External UCWA service                    : service URL is empty in the discovery response
    Internal Webscheduler service            : service URL is empty in the discovery response
    External Webscheduler service            : service URL is empty in the discovery response
    Server discovery succeeded for secure (HTTPS) internal channel against URL https://lyncdiscoverinternal.contoso.com/
    Starting automatic discovery for unsecure (HTTP) internal channel
    Couldn't connect to URL http://lyncdiscoverinternal.contoso.com/[email protected] (HTTP status code Forbidden)
    Server discovery failed for unsecured internal channel against http://lyncdiscoverinternal.contoso.com/
    Starting automatic discovery for secure (HTTPS) external channel

Maybe you are looking for