@Anonymous wrote: Hi @SteveB   Let us raise this to one of our Senior Technicians to conduct assessment and investigation. Could you shoot us a PM with your best contact time.   Regards,   I can connect to Teams if I use my phone's hotspot, it's only going through the ISP/router combination the issue happens.   As for Microsoft, they probably don't go beyond proving their stuff is all OK.   Our support remoted in and did Fiddler logs, again going to be sent to Microsoft, no answer yet.   It's likely a recent security protocol enforcement by something in the chain. As I said, our organisation is paranoid security wise and likely use very recent features that old, obsolete routers etc don't get unless they are updated or replaced. There has never been a firmware upgrade to my router since going FTTP because there isn't one. We don't live in a world where that is acceptable any more.   I may have to get a new router and see if it fixes the issue. One colleague on iiNet was fine but they had a high end gaming router so I suspect that the default router is the likely problem.   Regards   Steve Update on this issue: Microsoft have so far been unable to determine what is being broken in the security VPN chain but that investigation is ongoing. (there are several of us with this issue)   I borrowed a TP-Link AX6000 router and it works fine! This means that the old Archer C1200 (V1) router as supplied by TPG is the issue, something new security wise is not able to be transmitted via my work VPN client (Cisco AnyConnect). There is no later firmware for the old router so it's way obsolete.   TPG need to have a router update/obselecense policy as it is essential to support all modern security protocols given the wild west internet bandits these days.   I don't know what TPG plan to do about their old routers, the situation can only get worse as more software utilises the latest security protocols.   Regards   Steve ... View more

Chrome does its own thing as does Teams client, if Teams was going to use any browser component it would be Edge. This is NOT an issue with teams.microsoft.com being blocked in the ISP/router, Edge can get there OK.   It's an issue with some new security aspect of the response not being acceptable to Teams or Chrome while Edge is OK with it (for the moment).  The info (F12) in the Chrome response header indicates something is sub-par but then Chrome is a mental thing about security.   Given that the internet traffic is all via a high grade VPN client going directly to a local agency hosted VPN server you would think that the internal traffic would be independent of the ISP infrastructure.   My suspicion is that the VPN internal response traffic is inheriting some security aspects from the VPN container's header and that for some reason there is a new feature or header attribute that the ISP/router cannot process or pass through. My guess is it's a CORS or security attribute that is relatively new.   I'm 90% convinced it's likely to be a router limitation, those old Archer C1200 routers are way obolete and out of support. My likely only solution is to get a modern router instead of the TPG supplied one but there is still the risk that the limitation actually exists in the TPG infrastructure.   Happy to hear other suggestions or things to try though.   Regards   Steve ... View more

I can connect to Teams if I use my phone's hotspot, it's only going through the ISP/router combination the issue happens.   As for Microsoft, they probably don't go beyond proving their stuff is all OK.   Our support remoted in and did Fiddler logs, again going to be sent to Microsoft, no answer yet.   It's likely a recent security protocol enforcement by something in the chain. As I said, our organisation is paranoid security wise and likely use very recent features that old, obsolete routers etc don't get unless they are updated or replaced. There has never been a firmware upgrade to my router since going FTTP because there isn't one. We don't live in a world where that is acceptable any more.   I may have to get a new router and see if it fixes the issue. One colleague on iiNet was fine but they had a high end gaming router so I suspect that the default router is the likely problem.   Regards   Steve ... View more

While the VPN is started manually the whole desktop is very locked down so you can only work locally without it. ie No Internet unless through VPN and even then it's border managed.   Also every security setting is managed, I can do nothing with those settings or using non white listed tools etc.   Our support area are also perplexed as the whole network is fine according to Microsoft who were assisting with this issue (I'm talking thousands of workstations on our network, some working from home having issues if on TPG or iiNet)    Regards   Steve ... View more

Basically Teams client can't connect at all. When in Chrome anything going to "teams.microsoft.com" is blocked for some vauge security reason. "Upgrade-Insecure-Requests: 1" whatever that means (from the response header)   Teams client also uses this URI and dies but for some reason Edge is not blocking the vauge security issue outright. ... View more

I have to reply to this post because the TPG Community page won't let me start a post! There is no "New Post" button. Why?   I am on NBN50 and have FTTP. The complimentary speed boost only went to ~100mbs. If I run a large download at this speed the router crashes out after a few minutes and needs to be restarted (Archer C1200). I assume this is why the max speed is not reached?   Not sure what can be done about the router but it is very unstable when the network is faster than it can handle. Do you use better routers for faster connections? ... View more