Forum Discussion
Teams on Mac hangs on opening until "Could not connect to server xxx.xxx.x.x" message appears
Same here: MacBook Pro, all software up to date on Big Sur. Problem persisted since Catalina.
It waits for two (!) NAS shares to mount (one regular share and one Time machine share); works per se quite fast. But as mobile user, I am working in different places. And whenever I am outside my home network, I also have to wait for the process to time out.
This is very annoying when you have someone on the phone "...let me pull up teams real quick and have a look..."
All my data concerning work/TEAMs are on sharepoint, I access them via TEAMs or OneDrive. TEAMs has no business reading or writing on my NAS-shares and therefore should not have to wait until these are mounted.
Startup of Teams takes forever and tries to connect to internal file share, which doesn´t work in home office.
At one location the fils share isn´t even sharing files anymore, but they are all served through sharepoint.
I tried to replicate the behaviour through trying to share a file from the smb share, but I only receive an error message I can´t read fully because it is in preview mode and doesn´t show up anywhere else.
Did anyone of you contact MS support about this?
amd_andy I did. I scheduled a session with a tech and demonstrated the issue to him. I sent him console logs, and even provided a wireshark capture of the networking. He is currently sending me daily emails to let me know how things are going. So far basically none of the devs have had time to look at it, but at least he keeps giving me updates (making me think it won't get lost).
- LawsonCulver have there been any updates on this front from the Teams team?
- Kind of... They had me uninstall the entire Office suite, along with Teams and OneDrive. I also had to manually clean up some files. Installed ONLY Teams and it still mounted my drive on startup. I sent them system logs where Teams is requesting the drive be mounted, and I sent them Wireshark logs of the network traffic.
They kept saying they were looking into it, and then they tried to close the ticket without resolving it. I honestly think they still don’t know why their program keeps trying to mount my backup drive.
They asked me on Thursday to run a new tool and send them results, but I’m planning on doing it on Monday.
- That´s great news, thank you! Then I can only hope that it really won´t get lost 😉
