Forum Discussion
Teams error "We ran into a problem. Reconnecting..."
PeterRising We've had our network team vet the network side of things. We currently have a ticket open with MS and waiting for approval for internal escalation to the MS product support engineers.
At this point we're pretty convinced it's a token-related issue. People are reporting that if they sign out of Teams and sign back in they have no issues the rest of the day, but the issue returns the next day.
Would be interesting to know the result.
So we have this problem occasionally, specially if a user sends a laptop to sleep at home (Via VPN) and opens from dock at work.
Also coming from Dock to Company wifi (requires VPN for server access)..
I understand that it maybe a token issue, especially where we come from an MFA enrolled company, I believe jumping from a non trusted to trusted / even jumping from different sites, will confuse the heck out of Teams. I understand why it would, but, surely Teams is clever enough to sort itself out rather than sit there an wait for our intervention...
- Justin-GOVJun 01, 2021Brass ContributorOur company believes the split tunneling Teams with required MFA is causing this issue for us as well.
- Josiah_HJun 01, 2021Brass Contributor
that's interesting because I believe MS recommends spilt tunneling for Teams to work optimally, right? Justin-GOV
- Justin-GOVJun 01, 2021Brass ContributorYes. Split-tunneling does improve Teams connectivity. But, since some Teams traffic is split and seen as off VPN, when the MFA token expires the rest of our Office services are on VPN. We conditionally allow lengthier VPN traffic without re-authorizing MFA so Teams thinks it needs MFA but Office says they already have it and the two services argue while the user is stuck.