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...
I have the same problem.
I have a NAS share that my MacBook is set to reconnect at start. If I'm at home (where the NAS is accessible) Teams starts imediatelly with no problems or messages. If I'm anywhere else, and the network drive is not available, when starting Teams it takes few minutes to get in, and it forces Finder to spit out 3 consecutive messages, that the specific network share is not available, and only then the application shows a window. I have never ever attached a file from that network drive ( I have attached files from local drive only). Then on quit command it does the same thing, this time the quitting process is a bit faster (only takes 30-40 seconds) and spits only one Finder message for the unavailable network share.
My issue went away when Teams updated itself to 1.3.00.11161 on June 21st. I also removed the network drive from my startup options.
- I'm using 1.4.00.11161 and the problem is still there. Yes, I understand I can remove the drive from the start-up items, and it might solve Teams' issue, but I don't want to! I'm using that drive all the time and I like the fact I don't have to reconnect manually every time. It would be an inconvenience that shouldn't have to be the actual solution to an obvious bug. Why is Teams forcing Finder to attempt connecting to it?!?