Forum Discussion
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...
Just continuing to bump this in the hopes of finally finding an answer.
I've spent weeks with multiple MS tech support people going after this....I've given every log, every file, shown them in real time what happens...and they keep coming back to some issue with a DNS log that they blame on my employer. Except -- this happens everywhere with both personal and business accounts, so it doesnt appear to be a caching issue as they keep thinking. I kinda lost my stuff on them last week (sorry IT dude, but there's only so much I can take of being told it's my fault), and I think that's the end of the road for MS helping out. I told them to grab a Mac, map a NAS and include it in startup connections, then disconnect the NAS and try to open teams. We'll see if they actually try to keep this going.
My concern is the security implications here: if the handshaking between Finder and Teams is such that Teams can prioritize its choices for connections without my permission, then I see a big security hole someone can exploit. I dont know if anyone noticed, but Teams will also re-connect your server for you if you've disconnected it of your own volition whilst still on the same network. SO, it's not just the hang when it cant find the server...it's the entire way Teams for Mac interacts with shared/networked drives.
I've spent weeks with multiple MS tech support people going after this....I've given every log, every file, shown them in real time what happens...and they keep coming back to some issue with a DNS log that they blame on my employer. Except -- this happens everywhere with both personal and business accounts, so it doesnt appear to be a caching issue as they keep thinking. I kinda lost my stuff on them last week (sorry IT dude, but there's only so much I can take of being told it's my fault), and I think that's the end of the road for MS helping out. I told them to grab a Mac, map a NAS and include it in startup connections, then disconnect the NAS and try to open teams. We'll see if they actually try to keep this going.
My concern is the security implications here: if the handshaking between Finder and Teams is such that Teams can prioritize its choices for connections without my permission, then I see a big security hole someone can exploit. I dont know if anyone noticed, but Teams will also re-connect your server for you if you've disconnected it of your own volition whilst still on the same network. SO, it's not just the hang when it cant find the server...it's the entire way Teams for Mac interacts with shared/networked drives.