- Sync pending for this folder outlook 2011 mac exchange password#
- Sync pending for this folder outlook 2011 mac exchange windows#
Sync pending for this folder outlook 2011 mac exchange password#
It sends username and password in clear text across the network, which is, of course, horrible unsafe by default. Basic Authentication is pretty much what it sounds like, pretty basic. But a tenth of our company can now not work from home, which is a big problem for some.Īny help or advice would be greatly appreciated. However, I can’t get the IT department to enable Basic Authentication because they think it can’t be related (because the VPN is working so it must Authenticate fine), and because it might pose a security risk.ĭo you have any insights, words of advice, or things to try for this situation? When it was just me an Office 2011 struggling, it wasn’t so much of an issue. My recent hunch is that perhaps it has something to do with the issue you discovered above, though that seems far-fetched. We’ve verified that the names of the machines are correct, but none of us can get in. “Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.” Now, when we try to log in we get the alert: However, it’s Remote Desktop Connection that no longer lets us access our machines. We all connect via VPN (Cisco client), and we can all still connect to the VPN fine. This seems unrelated, but it’s a clear correlation, so that’s our only obvious connection now.
Sync pending for this folder outlook 2011 mac exchange windows#
Since the change to Exchange Server 2010, none of us can get to our Windows machines at work. Exchange is the last major bugaboo.Ģ) They hate dealing with Macs, so they leave me pretty much unsupported to deal with any and all issues by myself.ģ) There might be security issues in enabling the Basic Authentication (or so they claim), which I doubt, but might be the case – do you know?īut the big issue is that, while I am the only Mac user on-site, around 10% of the company uses Macs at home. This is for a variety of reasons:ġ) I am the only Mac guy in-house, and a guinea pig to see if we can convert our design department to Mac. Now, the IT department here hasn’t tried implementing your fix yet.
I thought that your discoveries above provided a solution for the problem I’ve been having here at work, which is exactly as you described above.
Thank you for this potentially very illuminating posting. If you want to make sure it’s updated fast, do a iisreset from a command line. We enabled Basic Authentication and it started working immediately on the Mac. Obviously you need to authenticate to pull anything useful out of this service, and, for perhaps pretty obvious reasons, the Mac wasn’t using Windows Authentication. It was set to allow Anonymous Authentication (this is required by the Exchange server) and Windows Authentication. Then we checked the authentication allowed for EWS in IIS. When we tried to browse via a browser on the Mac, it wouldn’t prompt for any credentials, just show a blank page, where a Windows computer would actually show something useful. Outlook 2011 doesn’t use MAPI, it relies solely on EWS (Exchange Web Services). The solution? Keep reading! The solution When we finally found the solution, it was a fairly basic one. Anyways, we struggled a long time as we kept getting no feedback on the process from the Mac. Let me be honest and say that at my company, we’re not exactly good when it comes to Macs, we’re actually quite horrible. It would just sit at an empty mailbox, no connection errors, no authentication errors, nothing. When he put in the information for the Exchange server, nothing happened. This customer also has a few Macs running Office 2011, where Outlook unfortunately refused to do anything (literally). Everything was set up like it should be, Outlook 2007 and Outlook 2010 clients worked like a charm. A colleague of mine was setting up a customer for Exchange 2010.
0 kommentar(er)
