Recently Google chat was depreciated by Hangouts. One of our employees is experiencing a strange issue with Hangouts after this change — She can't connect and can't receive messages. Hangouts works fine for the rest of the team on the same Gsuite @domain so we figured over the weekend this issue would resolve itself. It did not.
We tried turning chat on and off. Cleared everything. Tried on fresh PC's with no history of her account. Logged out everywhere. Monitored connects through Fiddler. Etc etc. She does not use Hangout app. There are no plugins installed. We didn't change domains or touch DNS. All the stuff is code 200 on the client end. It seems to be Google "server" side.
All forum threads I have seen are supremely unhelpful. "Did you try clear-cache/restart/different-browser?" kind of replies with the sound of crickets further down the threads. Yes we did all that. Google help says it's prob network based (which is false considering the rest of the team accounts work).
Has anyone experienced this? How do we solve these errors and connect?
Best Answer
After much trial and error across devices, OS's, networks, and facilities, we have finally solved "Errors: 212, 213, 214" in Hangouts.
In our case, the users Gsuite Organization Unit (we will call it a "group") was corrupted. The only way the user was able to use hangouts was when they were moved to a different or fresh group. The Google engineers didn't have a solution as to why this specific "Support" group became corrupted.
So, deleting the old group, recreating it, and re-assigning the user(s) to that fresh group seemed to work. Hangouts is now alive and kicking again. Thanks for all the good suggestions everyone.