Exchange under Mountain Lion

The different levels of success people are having with some of these solutions suggest that Exchange server settings are one of the factors. Some configurations appear to be sending set-up data to ML that is resulting in problems. See the post by justinhamlin on 27th July - MS and Apple need to work together to fix it

Grrr

I use outlook for mac 2012 and have experiences the same problem.

Mail was working fine until upgrade to ML and then got an exchange password error and was locked out of my work account.

I use an AIRPORT station.

I troubleshot and found that when I connect directly to modem without a router I can use outlook fine and connect to my exchange server.

When I use airport base station eveb with a hardwire I cant connect.

Hard to tell if the problem is with ML or with a default setting ML changed on my AIRPORT.

Anyone else using AIRPORt and having this problem?

I am also using an Airport router.

I added an external server address and checked the box for SSL in each of the preferences for Mail, Calendar, and Contacts. Seems to be working so far. Tests with syncs between each of these three programs between my Macbook Air and my iPad and iPhone appear to work.

I just found something else they may be another part of the problem. When I attempted to log on to a secure web site, I had a problem and a warning suggesting that my Network Proxy settings were off. I went into System Prefs, Network, Advanced, Proxy. Then checked auto (odd that nothing was checked), and passive at bottom. It worked. That affects communication with Local Area Networks, "Exchange," and may also have affected the abaility to correctly find server names as well as Proxy settings.

Maybe, Maybe not

I did just that joshuaiz. I agree that everyone with this problem should be sure to send that feedback to Apple to make sure they see this impacts a large number of users.

Joe

I am using a Time Capsule as my wireless router. My cable modem is plugged directly into that and my iMac connects to it.

Mine is a time capsule also, Joseph if you plug your imac directly into your modem does your exchange work fine?

Please don't let this thread get side tracked. This has nothing to do with your router or networking equipment. This happens no matter how you are conencted. We have tested this both on the same network as the exchange server, or remotely from outside the network and the issue still happens. It also doesn't matter if you are wireless or hard wired.This is related to changes made in the way Mail 6.0 works. It is now changing the internal server setting no atter how your connection is made.

Checking the "Use SSL" box for the external port did not fix the problem for me.

Ticking the SSL box is one step of several. From an earlier post:

The External Server setting on the Account Info tab also needed to be manually corrected. I also deleted the exchange record from my Keychains.

I agree with you about everyone contacting Apple about this to let them know it is a bigger issue than they think it is. I called them and to make a long story short they said I needed to contact my Exchange server IT person and have him update the server to be compatible with ML. I don't follow that logic since mail worked fine using Outlook for Mac but not with Mail. Sounds likes a Mail application issue not a problem at the OS level.😕

Like I stated in a earlier post mine was a simple issue of checking SSL and letting it go ahead and change the server addresses to what it wanted (since it is gonna do it anyway) and it has been working ever since.

I have similar problems! I have only tried to sync Exchange at home, not at my office. I have an Airport Extreme.

On my iPhone/iPad both mail and iCal work.

On my PowerBook Pro connected with wifi both mail and iCal work.

On my Mac Pro, connected with wire direct to the Extreme, mail works but in the beginning iCal refused to work. Nothing happended. I tried all of the tips above but nothing happened. Then I opened the Airport app and changed a parameter and then iCal started to work with Exchange!

Klick at the bottom "Internetalternativ... (sorry, from Sweden...)

I changed to Automatic and rebooted the Airport. Then it started to work. I got all of my calendar tasks from Exchange. But, there is a but. When I started my Mac Pro today iCal had all the information from Exchange but when I tried to write a new iCal meeting on my iPhone the Mac Pro didn't sync. I had to reboot my Extreme and then iCal started to sync.

My iCloud account works like a charm.

/Pär

I agree wi. points about not getting side tracked on this thread but will try Issac's solution at some point as well to see if I can get temporary relief for this.

Regardless, I have faith the Apple is going to get to the bottom of this. The company has always prided itself on its ability to be compatible with other platforms. It went truly out of its way to have cross connectability with Windows (Intel chip switch, etc.). Telling Mac home users that if Microsoft doesn't adapt to something caused by an Apple software update then they cannot access their work Exchange content in ML is going to result in thousands of people, like us, writing negative reviews of ML and getting back to the days of the not so distant past where people would say, "If you are using the computer for work at all, you gotta have a PC." I know Apple doesn't want that.

A few weeks ago Apple produced an update of iMovie. When I imported video from a Canon camera, the video was there, the audio wasn't. In a few weeks time, Apple came out with a software update for iMovie that resolved the problem. They didn't say (as that silly Tech. Support person did), that I needed to contact Canon to resolve it. I don't think they will ultimately do that here. But, there is strength in numbers. Let's continue to let our voices be heard and keep in mind that OSX is still the greatest operating system ever created. Peace!

Joe

This answer by APPLE tech.support leads me to think that my "theory" that Apple's engineers have silently "improved" the behavior of their mail client against Microsoft Exchange may be correct - even in that case, though, I expect Apple to soon publish some documentation describing their modifications (so that administrators of Microsoft systems can take care accordingly...).