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 this.
Basically, when she opens MS Teams, she gets the "spinning wheel" for about a minute. At the end of the minute, we get the OSX "Cannot connect to Server xxx.xxx.x.x", where x's are our local server that we currently do not have access to (working from home). I have ALSO tried disabling the NIC for this device.
We cannot locate ANYTHING in Teams that may be looking for this IP address, even shortcuts in chats.
I have the log file and can't see anything clearly out of order.
Any ideas??
Matthew
This is still an issue for me in Jan 2022 (almost 2 years later). Linking a related thread with the same workaround mentioned by others above if you're willing to delete the auto-mount from your startup items:
This is definitely not a solution to the issue though, so I'm still hopeful that someone at MS will see this and work on a proper fix.
I started experiencing the same problem while traveling -- Teams cannot connect to my home file server and hangs up. My Teams version is 1.4.00.35562 (last updated on 1/20/2022), so this is definitely not a solved problem yet. I temporarily removed the file server from my Login Items so that I won't go crazy during this business trip. Sigh ... another half-baked mess from Microsoft which we're forced to use per corporate policy.
- 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. - 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,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...)
- I had the connection to the share folders in the login items. I solved it removing them.
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?!?
- Mine is hanging again on an entirely NEW server that has no connection whatsoever to Teams. Teams is trying now 5 TIMES -- 3 to the OLD server I dont have and 2 to the NEW one -- to connect before it loads. It now also pulls the same crap on exit. This is ridiculous. It's not a NAS, it's not OneDrive, it's not ANYTHING other than an elastic storage server containing unrelated scientific data. And the fact that it tries co connect to old servers (whose info is purged from the Finder server list and any/all keychain passwords) makes me extra suspicious as to the flaw in teams. This seems like something rife for exploiting and that worries me.
we have the same issue, when users aren't in the same office as the server the Mac is attempting to connect to, removing the server connection from the users "startup items" resolved the issue for us. Presumably Teams thinks the connection is live, but cannot tell that it is offline if it remains the users "startup items"
kingjim1977 LawsonCulver I had to start using teams again. Teams starts immediately once I remove the server from my login items. Not ideal, but at least a workaround that does not have me staring at the screen waiting for apps to launch like it is 1995!
- I'm having the same issue on a few of my users.
MattPetersen i have the same issue. Teams keeps on looking for a volume that doesn't exist anymore. Tried to reinstall teams entirely - no effect. A few months ago it tried to mount it once, now I have to wait until THREE timeouts before I can use Teams - very frustrating
Ronald_Lange: the 1->3 transition is something I experienced too: when I installed teams, I had no remote drives mounted, all was fine. Once I mounted a remote drive, I started getting this timeout once while launching (I don't remember if it would wait while quitting too). Now, I have to wait for three timeouts before teams launches. I have not tried uninstall / reinstall, an "annoying but limping along" installation of teams currently holds more value than not having teams at all.
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.
- Same problem here: All together we have three different users - all on Catalina - on two different locations.
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).
MattPetersen Some issue here. I thought I was alone.
What's worse is I added a new Team -- and now I have to wait for it to try to connect to the server TWICE. Frustrating.
DrN8PhD I have the exact same issue. Teams has decided that whenever I open or close it, it cannot comply until it mounts a specific network share that I have. It's a NAS device with a folder called "backup".
With Teams closed, I unmount Backup. Open Teams, and Teams causes the volume to be mounted before opening.With teams open, I unmount Backup. Quit Teams, and Teams causes the volume to be mounted before closing.
When I am on my work VPN they block access to my Backup volume. This means that I have to wait for Teams to time out attempting to mount it whenever I open or close it.
