Home

Unable to oh no... we can't connect to the internet. Check your connection.

%3CLINGO-SUB%20id%3D%22lingo-sub-364232%22%20slang%3D%22en-US%22%3EUnable%20to%20oh%20no...%20we%20can't%20connect%20to%20the%20internet.%20Check%20your%20connection.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364232%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHoping%20someone%20can%20advise%20on%20an%20issue%20we%20are%20seeing%20in%20our%20organisation%20in%20relation%20to%20Microsoft%20Teams%20app.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20some%20reason%20some%20users%20are%20unable%20to%20access%20Microsoft%20teams%20desktop%20app.%20The%20web%20version%20works%20fine.%20We%20have%20confirmed%20that%20the%20latest%20version%20is%20running%20(1.2.00.4664)%20on%20a%20working%20and%20none%20working%20machine.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20some%20reason%20the%20teams%20app%20will%20work%20when%20first%20installed%20however%20after%20rebooting%20the%20machine%20we%20receive%20an%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3Edesktop-9e33ba8c-7964-4ecb-bd53-9c711fcda039%3C%2FDIV%3E%3CDIV%3EError%20code%20-%20Invalid%20FederationProvider%20response%20json%20cannot%20be%20parsed%3C%2FDIV%3E%3CDIV%3EFailed%20to%20connect%20to%20settings%20endpoint%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3ENow%20all%20of%20our%20web%20traffic%20goes%20through%20a%20trend%20micro%20cloud%20web%20security%20service%2C%20this%20is%20enabled%20on%20all%20machines.%20We%20have%20recently%20done%20a%20piece%20of%20work%20to%20allow%20all%20office%20365%20URLs%20and%20IPs%20on%20our%20corporate%20firewall%20and%20web%20security%20solution%20so%20effectively%20all%20365%20traffic%20is%20trusted.%20We%20have%20also%20added%20the%20sites%20into%20the%20trusted%20zones%20in%20the%20browser%20but%20for%20some%20reason%20I%20am%20getting%20this%20same%20issue%20on%20few%20select%20clients%20and%20unable%20to%20determine%20where%20the%20issue%20lies.%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EHas%20anyone%20else%20seen%20this%20issue%3F%20or%20did%20see%20any%20connectivity%20issues%20when%20adding%20in%20the%20URLs%20and%20IP%20address%20as%20per%20MS%20article%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Furls-and-ip-address-ranges%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Furls-and-ip-address-ranges%3C%2FA%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EI%20attach%20the%20log%20files%20from%20a%20working%20machine%20and%20non%20working%20machine.%20One%20thing%20to%20note%20is%20I%20seem%20to%20be%20getting%20a%20different%20welcome%20screen%20on%20the%20non%20working%20machine%20which%20I%20attach%20also.%20Has%20anyone%20seen%20this%20behaviour%3F%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EAny%20advice%20on%20this%20would%20be%20most%20appreciated%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EThanks%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-364232%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364252%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20oh%20no...%20we%20can't%20connect%20to%20the%20internet.%20Check%20your%20connection.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364252%22%20slang%3D%22en-US%22%3EUsually%20different%20login%20screen%20is%20related%20to%20using%20Modern%20Authentication%20vs.%20Non%20Modern%20Auth.%20It%20might%20be%20related%20around%20that.%20When%20someone%20not%20working%20tries%20to%20launch%20Teams.%20Dont'%20try%20logging%20in%20with%20the%20first%20login%20box%2C%20hit%20cancel%2C%20this%20will%20force%20the%20non%20modern%20Auth%20to%20come%20up%2C%20see%20if%20they%20can%20login%20then.%20If%20so%2C%20then%20I%20would%20focus%20around%20modern%20auth.%20Teams%20will%20be%20defaulting%20to%20this%20soon%20as%20well%20if%20it%20hasn't%20already%20thou%2C%20so%20I'm%20curious%20if%20this%20is%20a%20new%20issue%20or%20you%20guys%20just%20started%20to%20rollout%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-364243%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20oh%20no...%20we%20can't%20connect%20to%20the%20internet.%20Check%20your%20connection.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-364243%22%20slang%3D%22en-US%22%3ESome%20questions%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAlways%20the%20same%20machines%3F%20They%20can%20login%20to%20web%20with%20that%20same%20user%3F%3CBR%20%2F%3ESame%20network%20location%20as%20working%20computers%3F%3CBR%20%2F%3ETry%20disable%20OS%20firewall%3F%3CBR%20%2F%3ETried%20the%20same%20computer%20on%20other%20network%3F%3CBR%20%2F%3ERemoved%20the%20teams%20cache%20folders%3F%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E
Ranjeet Singh Bassi
Occasional Contributor

Hi All

 

Hoping someone can advise on an issue we are seeing in our organisation in relation to Microsoft Teams app. 

 

For some reason some users are unable to access Microsoft teams desktop app. The web version works fine. We have confirmed that the latest version is running (1.2.00.4664) on a working and none working machine. 

 

For some reason the teams app will work when first installed however after rebooting the machine we receive an error:

 

desktop-9e33ba8c-7964-4ecb-bd53-9c711fcda039
Error code - Invalid FederationProvider response json cannot be parsed
Failed to connect to settings endpoint
 
Now all of our web traffic goes through a trend micro cloud web security service, this is enabled on all machines. We have recently done a piece of work to allow all office 365 URLs and IPs on our corporate firewall and web security solution so effectively all 365 traffic is trusted. We have also added the sites into the trusted zones in the browser but for some reason I am getting this same issue on few select clients and unable to determine where the issue lies. 
 
Has anyone else seen this issue? or did see any connectivity issues when adding in the URLs and IP address as per MS article https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges
 
I attach the log files from a working machine and non working machine. One thing to note is I seem to be getting a different welcome screen on the non working machine which I attach also. Has anyone seen this behaviour?
 
Any advice on this would be most appreciated
 
Thanks

 

2 Replies
Highlighted
Some questions :)

Always the same machines? They can login to web with that same user?
Same network location as working computers?
Try disable OS firewall?
Tried the same computer on other network?
Removed the teams cache folders?

Adam
Highlighted
Usually different login screen is related to using Modern Authentication vs. Non Modern Auth. It might be related around that. When someone not working tries to launch Teams. Dont' try logging in with the first login box, hit cancel, this will force the non modern Auth to come up, see if they can login then. If so, then I would focus around modern auth. Teams will be defaulting to this soon as well if it hasn't already thou, so I'm curious if this is a new issue or you guys just started to rollout?