Netflix no longer streaming

I have the KDV21 but using an Asus mesh with DHCP (double NAT) and Cloudfare DNS. No issues with Netflix on Apple TV 4K, iPhones, iPads, and MacBooks. I also have a Android 10 DAP that works fine too.

It is an odd issue and hard to nail down. I have the Nokia as I stated and it works for me here and I do have  Cloud Flare set on my MacBook Pro for DNS. Yes, no issue here for me. I don't run an additional router or any extenders. I have been trying to see if there are some hard clues. The packet captures where the HTTPS fails authentication for two different users seemed like a good start. Still I think there are more common datapoints that are not recorded. Almost need a laundry list of variables to look for common elements to pull it all apart. I still can't seem to ignore the two users that have the packet captures showing the issue with HTTPS. If the session authentication fails then of course the mission fails. Why, what is the trigger? 

iTinkeralot wrote:

It is an odd issue and hard to nail down. I have the Nokia as I stated and it works for me here and I do have  Cloud Flare set on my MacBook Pro for DNS. Yes, no issue here for me. I don't run an additional router or any extenders. I have been trying to see if there are some hard clues. The packet captures where the HTTPS fails authentication for two different users seemed like a good start. Still I think there are more common datapoints that are not recorded. Almost need a laundry list of variables to look for common elements to pull it all apart. I still can't seem to ignore the two users that have the packet captures showing the issue with HTTPS. If the session authentication fails then of course the mission fails. Why, what is the trigger? 

Personally, I think it's a caused by using TMO router's default DNS. When I first used the TMO router as a stand alone, I had random connectivity issues (not all websites and not all devices). That all went away when I changed to Cloud Flare DNS on my Asus mesh.

Unfortunately the TMO Routers cannot change DNS servers so you can only change DNS at the device level if your device allows it.

The issue or problem with the DNS resolution has to be related to the 464XLAT delivery. I have seen that issue as well. I just changed my clients to use Cloud Flare and it was a quick fix. The refresh time to the gateways or the gateway firmware just probably does not refresh properly so the entries get stale. If you reboot the gateway to fix that issue sure it forces the DNS refresh. That is just an extreme way to resolve the problem. They just need to look at the protocol stack used in the code and fix it. 

The Netflix streaming issue seems a bit different and the packet capture suggest a problem with delivery of the packets via port 443. The domain info is correct so the handling of the layer 4 information is mucked up. With the packet information it really looks like that. I have not seen the full capture information for a failed session initiation as it works here. I have the Nokia and the Arcadyan gateway does not seem to be impacted by this. Maybe it is with the Sagemcon firmware. Still not enough data to know and no way to debug it with these dumbed down gateways other than packet captures and that only points at the fault not the root cause. I often wish T-Mobile would just be a bit more transparent about the problems and be up front about the genuine effort being applied. Just a little respect would be nice. 

I no longer have the issue, Netflix is working for me now. They
have change the IP for occ-0-7094-90.1.nflxso.net from a T-Mobile owned IP to
a Netflix owned IP 198.38.108.x. So the traffic is no longer going to the
T-Mobile data centers and instead is sent direct to the Netflix data centers.

AS2906

198.38.108.0/24

Netflix Streaming Services Inc.

curl -v https://occ-0-7094-90.1.nflxso.net
*   Trying 198.38.108.76:443...
* Connected to occ-0-7094-90.1.nflxso.net (198.38.108.242) port 443 (#0)

11:37:26.467868 IP 192.168.x.x.61346 > 198.38.108.242.443: Flags , seq 2992268027, win 65535

11:37:26.513020 IP 198.38.108.242.443 > 192.168.x.x.61346: Flags [S.], seq 1595082536, ack 2992268028, win 65535

11:37:26.515457 IP 192.168.x.x.61346 > 198.38.108.242.443: Flags [.], ack 1, win 2054

11:37:26.522641 IP 192.168.x.x.61346 > 198.38.108.242.443: Flags [P.], seq 1:337, ack 1, win 2054

I suspect that was a workaround while they figure out the root cause on the
T-Mobile hosted Netflix streaming.

When I had the issue I changed my DNS resolver to Google, CloudFlare, OpenDNS etc, but as long as occ-0-7094-90.1.nflxso.net resolved to a T-Mobile IP here in the east coast, the issue was there.

So another DNS resolution problem. More reason to set DNS to something other than the gateway IP relying upon the default they have established. The delivery of proper DNS resolution from the gateway IP has had some issues so it should not be a surprise actually. It is interesting that it was primarily only for Netflix in this case. I was using quad9 for DNS so that explains why it was working here.

I am still unable to stream from any of my apple devices ( iPad, iPhone, appleTv )… however, I can now stream from safari on my laptop.  I have also tried updating the DNS server settings to google in my router… and also directly on my appleTV.  This also did not work for me.

Does the laptop connect through the gateway and which gateway do you have? You state from Safari on your laptop works. What is your laptop and can you see a difference in the IP addressing of the laptop that works and the other devices? So, also you state you tried updating the DNS server settings to google on your router. Do you have a router connected to the T-Mobile gateway? 

What network does the laptop connect to? Is it also connecting via wireless or with an Ethernet cable and is that to wireless via the T-Mobile gateway direct on its wireless or via a connected router? 

The suggestion to change the DNS on a client was to see if it would help but was only based upon the possibility that it might if the DNS from the 192.168.12.1 gateway address was not working. I have seen a recent period when DNS here was failing and I changed my MacBook DNS to quad9s and it resolved the issue for me. I still have my MacBook Pro with 9.9.9.9 for DNS and Netflix and Amazon Prime both work for me. I have the Nokia gateway so I also have not seen any postings to know if the issue has some bearing on any specific gateway. From the Reddit conversation is sounded more like the engineers were working on some solution but it was not clear what. I wish T-Mobile would actually post some reference to issues like this which impacted many users. If I see more on this I will let you know.

I know that this thread is a couple of months old now, but I just started having this problem. I can no longer successfully load Netflix on any of my Smart TVs or STBs (various Fire devices). I get error tvq-st-106 when I try. I poder load the app on my iPhone and PC, and I can stream content. But, no thumbnails appear.

This just started happening on 2/9/2023. I have spent considerable time with both Netflix and T-Mobile support, but have not made any progress toward resolving the issue.

Does anyone have any ideas on what I can try? Is anyone else seeing this issue again?

¡Gracias!

I have the same Netflix issue that also started on 2/9. I have a smart TV with a firestick and another TV with just a firestick. 

This is getting to be so frustrating that I'm considering getting rid of the gateway! Why can't they fix this, since there's enough people having the problem.