Thanks mpryor!

Updating the client to 3.5.2 helped. No more error prompts and much better connectivity experience for the end users. In case I missed it, was a direct root cause to this error ever found/documented?