Netflix no longer able to stream on Gateway internet
Best answer by Blava_Highlander
View original
Page 1 / 4
I have this problem as well. None of the images load in any of my devices. Whether it is in an app or in a web browser.
I also see the requests timing out to what appears to be a tmobiled owned subdomain of a netflix owned primary domain:
Resolving occ-0-7099-116.1.nflxso.net (occ-0-7099-116.1.nflxso.net)... 208.54.15.187, 208.54.15.189
Connecting to occ-0-7099-116.1.nflxso.net (occ-0-7099-116.1.nflxso.net)|208.54.15.187|:443... failed: Operation timed out.
Connecting to occ-0-7099-116.1.nflxso.net (occ-0-7099-116.1.nflxso.net)|208.54.15.189|:443... failed: Operation timed out.
| A | occ-0-7099-116.1.nflxso.net | 208.54.15.186 T-Mobile USA, Inc. (AS21928) | |
| A | occ-0-7099-116.1.nflxso.net | 208.54.15.187 T-Mobile USA, Inc. (AS21928) |
Userlevel 7
+8
They marked this community conversation with a best answer pointing to a conversation in a Reddit thread. There was no obvious answers there. It was discussion on the issue but did not explain why Netflix was not working. Looking at the actual traffic/packets and seeing is believing.
Good point. Yesterday I checked for updates on the Netflix app as well as the Vizio. They were both current. Just to be safe I deleted the Netflix app and reinstalled it. Also Netflix provided a link so that I could clear the cache. All to no avail.
I disconnected my Google wifi router from the Gateway and my Netflix issues have been resolved. Everything is working perfectly on my smart TV and 2 firesticks.
I stopped at a store today and confirmed that the wifi router that was previously used with my modem with Spectrum isn't necessary with the Gateway.
I needed a little assistance from customer support to get the internet connection set up again, but it's all good now!
Netflix stopped working a couple of days ago on my Roku and on my Vizio smart TV. The apps on both are up to date.
Userlevel 7
+8
Well, I am out of ideas and it is getting late. The HTTPS setup is my best guess. It works here for me on Safari. The FireStick had no issue nor did the app on the Xbox so… I got nothing.
Maybe tomorrow will bring a change in the wind.
https://www.reddit.com/r/tmobileisp/comments/zf0zla/netflix_still_not_working/
There seems to be some more detailed information on this reddit, if you wish to review it.
Userlevel 7
+8
The part I suspected yesterday and still do is the authentication with secure HTTP. When I see what you posted for, what I suspect to be working vs not working is the server responding on port 443. The failure takes place or seems to before the user can even get authenticated via the HTTPS connection to the Netflix server. Watch the front end of the session closely. I will have to run a capture later as I don’t have the time right now but I know it is working here so I can at least record the initial setup and know what to expect for the initial setup of the session with the server. Without hard data I am just speculating.
That is another factor I have had some suspicions about. Users that use additional routers vs those that do not. I have ONLY the Nokia gateway running. It works. Is the gateway hardware a factor OR additional router or mesh connected to the gateway part of the equation? I don’t know as there are not enough data points to draw additional conclusions or a theory that has some substance based upon data. It could still be in the T-Mobile IPv6 network vs at the edge.
Userlevel 7
+8
From that seeing the 443 time out tells me it appears to be excessive delay on the initial authentication setup. At least that is what I suspected.
Here are all the requests that I see in order:
android.prod.cloud.netflix.com = Successful connection
nrdp60-appboot.netflix.com = Successful connection
occ-0-7094-90.1.nflxso.net = Failed SYN packet, no response on T-Mobile IP
api-global.netflix.com = Successful connection
secure.netflix.com = Successful connection
occ-0-7094-90.1.nflxso.net = Failed SYN packet, no response on T-Mobile IP
ichnaea.netflix.com = Successful connection
Testing to occ-0-7094-90.1.nflxso.net from T-Mobile home gateway:
curl -v https://occ-0-7094-90.1.nflxso.net
* Trying 208.54.15.202:443...
* connect to 208.54.15.202 port 443 failed: Operation timed outTesting to occ-0-7094-90.1.nflxso.net from Comcast IP:
curl -v https://occ-0-7094-90.1.nflxso.net
* Trying 208.54.15.203:443...
* Connected to occ-0-7094-90.1.nflxso.net (208.54.15.203) port 443 (#0)
I hope T-Mobile can resolve this ASAP as it has been many days with no progress
Userlevel 7
+8
That specific information needs to get to the engineers so they can see for themselves. That makes it pretty obvious the HTTPS did not connect.
Userlevel 7
+8
Thanks so much for taking the packet captures from both sources. I am not sure what gateways were used for those two or if it has any bearing on the problem but clearly the HTTPS session does not complete authentication. I could have taken captures here but mine seems to be working but have the Nokia gateway. We could be in different regions for all I know and that may have a bearing on the problem as well. If it is due to firmware on the gateways then it might take some time for them to push the update out. Who knows how long that will take to complete given you can’t go get it.
Agreed, nothing better than seeing packets. I have the Arcadyan KVD21 gateway Firmware 1.00.16 on the East Coast.
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.
Userlevel 7
+8
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?
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 can 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?
Thanks!
In my case, this issue was caused by the fact that a rep signed me up for a business account…even though I didn’t need one and don’t own a business. The business accounts, by default, have a “productivity block” on them so employees can’t sit around watching tv all day. It took multiple calls, but the latest agent I talked to disabled the block. After a few reboots, of the tv and the Gateway, streaming services are all working now
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.
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.
Userlevel 7
+8
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 |   | 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 [S], 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.
Userlevel 7
+8
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.
Userlevel 7
+8
I gave the questions some thought and have a couple for you both to consider if you have not done so already.
Do you use the gateway with a third party router on your network or just the T-Mobile gateway?
Do you have dual stack enabled on the streaming devices you are attempting to use?
The reason I ask is that Netflix is among the largest domains using IPv6 for streaming content delivery and IPv6 does provide some benefits over IPv4 for content delivery. Using dual stack IPv4/IPv6 on the devices would probably be best. With IPv6 on the clients it would also circumvent the 464XLAT overhead due to not requiring the CLAT / PLAT translation between IPv4 & IPv6. I suggest to check the clients and make sure they do run dual stack. If there are any software/firmware updates available for the TV or Firestick also apply updates.
I use Netflix on multiple types of clients here including a Firestick and have not experienced issues but I also do not use an additional router on my network. I have kept it simple and direct. If you do run an additional router with your clients on a network other than the T-Mobile gateway segment it would be worth running the same client(s) on the T-Mobile gateway network to confirm operation as such.
Just a couple of thoughts as the problem might still be upstream and not a local network issue. If you have not investigated the DNS servers your clients are directed to then I would also suggest to experiment with the target DNS servers for the clients. When I have experienced some internet related communication issues here my alteration of the DNS source away from the gateway did help so I tend to still avoid allowing the 192.168.12.1 gateway to be used for DNS resolution.
Good luck with your endeavor.
I am having the same problem starting on Feb 9th. I cannot stream Netflix on any of my Roku TVs, Samsung Smart TV. Every other streaming service works fine. I have spent several hours with Netflix and T-Mobile, with no resolution. Even one call for over 90 minutes with both Netflix and T-Mobile on the same call. Netflix is taking the position that this is not their problem and would not even let me talk with their technical support team.
I saw the response from iTinkeralot, but I am not sure what to do based on his response.
It seems my only solution would be to cancel T-Mobile Internet, Netflix, or both. Netflix reps are condescending, claiming it is not their problem and I cannot talk with their technical supporting team.
I use a Google wifi router.
Are you saying that we don't need a router if we use the Gateway?
Appreciate your time!!
Page 1 / 4
Reply
New badge winners
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.