911guy

Q: MS Exchange mail account no longer connects after installing El Capitan

My MS exchange mail account worked perfectly all morning, last received message was 2 minutes before I downloaded and installed El Capitan.  As soon my mac booted up in El Capitan and mail opened the account showed a connection error and asked me to verify the settings.  Even though I assumed that the settings had not changed during the install process I did verify them and they were still correct.  I deleted the account and set it up again only to receive the same connection error.  Is anyone else experiencing this?  Does anyone know of a fix?

OS X Yosemite (10.10.5)

Posted on Sep 30, 2015 2:20 PM

Close

Q: MS Exchange mail account no longer connects after installing El Capitan

  • All replies
  • Helpful answers

Previous Page 2
  • by dwb,

    dwb dwb Oct 1, 2015 8:51 AM in response to 911guy
    Level 7 (24,221 points)
    Notebooks
    Oct 1, 2015 8:51 AM in response to 911guy

    I’d be surprised if the old Mail program works, let alone solves the problem. Apple’s programs tend to be tied into the OS at very low levels.

  • by Ein o Grön,

    Ein o Grön Ein o Grön Oct 1, 2015 11:15 AM in response to Ein o Grön
    Level 1 (0 points)
    Oct 1, 2015 11:15 AM in response to Ein o Grön

    the thing is that I don't think the problem is in apple Mail client " of corse its El Capitan that is creating the problem but "I think the mail app is working just fine, it's probably the mail servers that's needs to be updated for the mail client to work as Apple designed it to. il post as soon a I tried a few solutions,

  • by 911guy,Solvedanswer

    911guy 911guy Oct 1, 2015 12:50 PM in response to Ein o Grön
    Level 1 (1 points)
    Oct 1, 2015 12:50 PM in response to Ein o Grön

    Ok, the boys from IT just showed up.  After making fun of my mac for 10 minutes and telling me it had no place in the enterprise because of issues just like this, they changed one thin and now it works like a champ.  In preferences, under the exchange account, account information tab, they changed the external server name to webmail.(yourservername.here) and it worked immediately.  The auto-detect feature of EWS was giving a name that mail apparently didn't like.  I apologize for not knowing more in-depth information on this, but hopefully this may help someone out there having the same problem.

     

    Cheers!

  • by Paul Conaway,

    Paul Conaway Paul Conaway Oct 1, 2015 5:08 PM in response to 911guy
    Level 3 (935 points)
    iPod
    Oct 1, 2015 5:08 PM in response to 911guy

    Glad you got it worked out.

  • by Ein o Grön,

    Ein o Grön Ein o Grön Oct 1, 2015 9:08 PM in response to Ein o Grön
    Level 1 (0 points)
    Oct 1, 2015 9:08 PM in response to Ein o Grön

    The mail server problem i solved as well, we turned of ssl in the protocol settings for ip port 587.

     

    El capitan is really flying, when al the problems i solved and you start focusing on the OS X, but to be true i still have to get the index start working.

  • by SnowRider24,

    SnowRider24 SnowRider24 Oct 6, 2015 10:06 AM in response to 911guy
    Level 1 (0 points)
    Oct 6, 2015 10:06 AM in response to 911guy

    I managed to successfully add the account:

     

    After you try to add the account, it shows another screen where it asks for Internal URL and external URL. What I did is I used the recommended link with our internal exchange address:

     

    https://your.exchange.com/EWS/Exchange.asmx

     

    Both for internal and external URLs.

     

    The account was created right away and the incoming and outgoing were setup correctly using my exchange domain.

  • by ChemApple,

    ChemApple ChemApple Oct 7, 2015 12:20 PM in response to 911guy
    Level 1 (80 points)
    Oct 7, 2015 12:20 PM in response to 911guy

    Everyone else seems to be having problems with mail, but my problem is with Calendar and o365.  The calendar just doesn't seem to want to sync or connect with outlook.office365.com server, but the mail has worked flawlessly since upgrading. I've tried deleting and readding in calendar and in system preferences, but nothing seems to have an effect.  I can't believe that o365 doesn't have an up-to-date server protocol!

  • by Ein o Grön,

    Ein o Grön Ein o Grön Oct 7, 2015 11:12 PM in response to ChemApple
    Level 1 (0 points)
    Oct 7, 2015 11:12 PM in response to ChemApple

    Have you tried to reinstall office 365 feels like it could be something wrong  with the 365 installation after the upgrade to capitan

  • by Ein o Grön,

    Ein o Grön Ein o Grön Oct 8, 2015 9:58 PM in response to ChemApple
    Level 1 (0 points)
    Oct 8, 2015 9:58 PM in response to ChemApple

    Do a office update there should be a new update that solves the problem for outlook 2011,

    but it not for 2016.

  • by pythagos,

    pythagos pythagos Oct 23, 2015 3:10 AM in response to 911guy
    Level 1 (0 points)
    Oct 23, 2015 3:10 AM in response to 911guy

    Hi everyone,

    i am desperately in need of help; spent full day on fixing the exchange problem but no success + full of frustration.

     

    Upgraded to El Capitan, using exchange server with Mail. This morning i suddently started to get cannot connect to exchange server error. So I deleted the account, tried to re-add but had problem with it. re-added Certificate file to the key chain, but still cannot add/connect to exchange server.

     

    1) can you think of other solutions?

    2) if i install office 2016, can i use Mail and Outlook 2016 simultaneously (i don't want to mess-up my other accounts unless it works fine)?

    3) can i downgrade from El Capitan to Yosemite without Time machine; is so can you send me a link explaining how to do it

     

    thank you

    f

  • by timneva,

    timneva timneva Oct 27, 2015 5:38 PM in response to 911guy
    Level 1 (0 points)
    Oct 27, 2015 5:38 PM in response to 911guy

    Thanks man!

     

    just upgraded too and same issue with exchange. I run two accounts and my exchange account just kept failing with invalid login. As soon as I added "webmail" to the front of the external server I was back up and running. Weird!....... but it works - so I'll take it.

     

    Not sure if it'll work for everyone but my external server was "remote.server.name" and I changed it to "webmail.remote.server.name" and it worked

  • by cfvalera,

    cfvalera cfvalera Oct 31, 2015 10:25 AM in response to timneva
    Level 1 (0 points)
    Oct 31, 2015 10:25 AM in response to timneva

    I juste upgrade to El Capitan 10.11.1, problem with my Microsoft Exchange. I suppressed it an create at new, everything is ok now.

  • by AppleiOSNOI,

    AppleiOSNOI AppleiOSNOI Nov 11, 2015 3:00 PM in response to 911guy
    Level 1 (0 points)
    Nov 11, 2015 3:00 PM in response to 911guy

    I got it working Guys!!!!

     

    Use the same setting just like your iPhone.

     

    Don't follow the example that states on the example of the internal/external URL.  The greyed out example uses: https://webmail.exchangeserver.com

    just take out the "https://"

    Here are my settings:

    Email Address: Not@Telling.com

    Username: Telling\Not  = Domain\Username

    Password: 123456

    Internal URL: Leave this blank...

    External URL: webmail.Telling.com  = webmail.RegisteredDomainName.com  Notice that I left out the "https://"

  • by AppleUserSince84,

    AppleUserSince84 AppleUserSince84 Nov 19, 2015 8:29 PM in response to AppleiOSNOI
    Level 1 (0 points)
    Nov 19, 2015 8:29 PM in response to AppleiOSNOI

    I also got it working but a different way. And I've been able to repeat it. After locking myself out of my work  exchange account about 20 times... I found that if I use the OWA link that you can access your company e-mail using a web browser. But I accidentally found a trick.

     

    FIrst I had to delete my account and any other exchange accounts.I tried and tried but it wouldn't work until I did this and then recreated my account. Before recreating account, I was prompted to REBUILD my e-mails and I did that. ( I am not sure if that is necessary but I think it helped a lot) After rebuilding, I recreated my account. Then I input the fields...

     

     

    For e-mail address don't use:    Firstname.Lastname@xxx.com  instead use the alias if your company uses them....

     

    FLastname@xxx.com  (usine the first initial of your first name and your last name...no periods....seems to be a widely used standard)

    For internal link I put :       http://owa.xxx.xx.com\domain

    For external link I put:         owa.xxx.xx.com           (no http and no domain)

     

     

    and it worked for me... on 2 different machines...But make sure you aren't locked out of your exchange account. On one machine, I updated to El Capitan and left my house for hours... When I got home, I found my work account was locked out on my phone and other devices... THis was because after the upgrade, there were too many unsuccessful attempts on my account. SO if you are locked out, even if this method works, it won't work until you are reset from any lockouts.. (Both times, I just happened to be logged in using the OWA web browser connection but this should not have had a bearing on it working.)

     

    It can work... I tried everything for over a week and finally found this method to work.

  • by GILORTEGA89,

    GILORTEGA89 GILORTEGA89 Sep 13, 2016 3:36 PM in response to 911guy
    Level 1 (4 points)
    Mac OS X
    Sep 13, 2016 3:36 PM in response to 911guy

    ANY HELP?

Previous Page 2