Forum Discussion
MattPetersen
Apr 14, 2020Copper Contributor
Teams on Mac hangs on opening until "Could not connect to server xxx.xxx.x.x" message appears
A member of my team is having an issue opening the MS Teams (Mac) app on her iMac (identical to mine). We deleted the cache files, then associated files, and re-installed Teams before posting thi...
nathanoicts
Sep 24, 2021Copper Contributor
Teams shouldn't be trying to mount drives present in Login items at all.
I'm running MacOS Big Sure and I have my Synology at home mounted via an automatic SMB share. This share is of course in my Login items to make sure that when I'm at home a Backup is made using Time Machine.
That's ALL I'm using it for. Why would Teams ever need to be a part of this process? It shouldn't.
To make matters worse. When utilizing Power Nap (Sleep mode) when putting the laptop in my bag between work, customer or home this MS Teams issue crashes my laptop. Consistenly, everytime.
Only solution? Disabling my login item, breaking my backup solution. Thanks Microsoft, you've now made it possible to even break stuff that's an integral part of MacOS,
I'm running MacOS Big Sure and I have my Synology at home mounted via an automatic SMB share. This share is of course in my Login items to make sure that when I'm at home a Backup is made using Time Machine.
That's ALL I'm using it for. Why would Teams ever need to be a part of this process? It shouldn't.
To make matters worse. When utilizing Power Nap (Sleep mode) when putting the laptop in my bag between work, customer or home this MS Teams issue crashes my laptop. Consistenly, everytime.
Only solution? Disabling my login item, breaking my backup solution. Thanks Microsoft, you've now made it possible to even break stuff that's an integral part of MacOS,
bvanrent
Oct 26, 2021Copper Contributor
Don't have the answer yet, but just stating that I have the same problem. As I have multiple Office365 accounts (and I must constantly switch between them), and I have the issue only with one account, my assumption is that this is somewhat linked to an account config/setup. Hopes this helps to pinpoint the issue... but please Microsoft, do something about it soon, as this issues is really becoming unbearable to me (losing 5-10 minutes with account switching...)