Netflix streaming issue 2014-05-24

Forums › Online streaming services › Netflix streaming issue 2014-05-24

1 | ... | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | ... | 53

20 posts

Geek

#1057772 2-Jun-2014 07:53

I'm using a dynamic IP.

Curious how many users are now getting Netflix US to work on VF or other providers. I have no contract with VF but don't really want to go in to a new one by switching.

Falvation

26 posts

Geek

#1057781 2-Jun-2014 08:59

Hi Guys. My connection to Netflix was working awesome but now its just stopped working on my Apple TV. I am with Vodafone ADSL2 using Unblock-us. I went through that issue a few of us experience which was blocking me from using it, then it worked for a few days and now I can't load anything on my apple tv 2. Any ideas?

ir1141

74 posts

Master Geek
+1 received by user: 2

#1057822 2-Jun-2014 10:45

still working here on VF cable

getflix

11 posts

Geek
+1 received by user: 14

Trusted

Getflix

#1057859 2-Jun-2014 11:46

Falvation: Hi Guys. My connection to Netflix was working awesome but now its just stopped working on my Apple TV. I am with Vodafone ADSL2 using Unblock-us. I went through that issue a few of us experience which was blocking me from using it, then it worked for a few days and now I can't load anything on my apple tv 2. Any ideas?

Our affected customers on VF are on ADSL as well... no reports of any problems on VF cable

mynxnet

37 posts

Geek
+1 received by user: 4

mynxnet

#1057887 2-Jun-2014 12:23

I have been watching this space a lot for the last few months, and it seems there has been a big push by the major content providers against Netflix, hulu etc to crack down on these services. Nothing official out there but the major players all started making changes at the same time

freitasm

BDFL - Memuneh
80655 posts

Uber Geek
+1 received by user: 41052

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1057888 2-Jun-2014 12:25

mynxnet: I have been watching this space a lot for the last few months, and it seems there has been a big push by the major content providers against Netflix, hulu etc to crack down on these services. Nothing official out there but the major players all started making changes at the same time

Hanlon's Razor: "Never attribute to malice that which is adequately explained by stupidity."

If you mean the large New Zealand ISPs I think you will see that those same "big players" were just using default configurations. After adjusting those to respect headers and origins most of the problems went away.

If you mean SKY... Well, they were never friendly to any competitor really.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

Samsung

Shop now on Samsung phones, tablets, TVs and more (affiliate link).

mynxnet

37 posts

Geek
+1 received by user: 4

mynxnet

#1057897 2-Jun-2014 12:31

By big players I more mean the studios who create the content and distribute the rights to show it. Netflix, Hulu and Vudu have all made changes to their internal services and the applications they distribute. One app even changed to using hardcoded DNS servers.

eXDee

4033 posts

Uber Geek
+1 received by user: 1070

Trusted

#1057912 2-Jun-2014 13:00

Tomato overcomes hardcoded DNS servers nicely with a checkbox. Not sure if other firmwares support that, but a handy feature for thwarting the hard coded DNS.

Though unfortunately my my main modem/router is currently a fritzbox. So currently working on a bit of vlan and iptables trickery to force the roku's LAN port to have all its DNS intercepted.

Falvation

26 posts

Geek

#1057914 2-Jun-2014 13:06

My netflix appears to be back up and running again. Just makes me nervous everytime it stops working.

xena7051

44 posts

Geek

#1058149 2-Jun-2014 19:00

Hi

Have a family member who lives in Tauranga and is a Trust Power customer.....any one know of Trust Power, if you are a customer has it been resolved?....from what I know its not...we use Unblock-US as our DNS service provider and below is what they have responded with.

The error we are getting has a message number of N8210....although its seems intermittent if we can or can't open a movie and get this error straight away

Appreciate any feedback

Cheers
Peter

feedback from Unblock - US

Thanks for all your help now with this issue, we no longer need any further testing to be carried out and have concluded our investigations. 1. Netflix recently changed the format of URLs for US and Canadian CDN used for video streaming 2. The affected NZ providers are using transparent caching proxies for the Netflix CDN range of IP addresses. They are NOT using these for other IP ranges we tested. 3. The affected NZ providers are using transparent caching proxies that are set up incorrectly: - They cache content with "no cache" directive in HTTP header (Pragma: no-cache & Cache-Control: no-store) - They ignore query string part of the URL for caching The combination of 1, 2 and 3 has resulted in the Netflix streaming issue. Netflix has started using query string part of the URL to request the movie pieces. Since the content is cached incorrectly, the Netflix player tries to get a fragment of the movie but gets a completely different movie piece from the proxy and shows the error message. Affected ISPs have to reconfigure their proxies to: Take query string into account OR Respect "no cache" directive OR Turn them off for Netflix CDN IP range as caching Netflix streaming does not provide any benefit to the ISP. We encourage you to send the above to your ISP - as this is how they can fix the issue. If enough of you speak - then your ISP might do something about it.

NonprayingMantis

6434 posts

Uber Geek
+1 received by user: 1528

#1058157 2-Jun-2014 19:34

feedback from Unblock - US

Thanks for all your help now with this issue, we no longer need any further testing to be carried out and have concluded our investigations. 1. Netflix recently changed the format of URLs for US and Canadian CDN used for video streaming 2. The affected NZ providers are using transparent caching proxies for the Netflix CDN range of IP addresses. They are NOT using these for other IP ranges we tested. 3. The affected NZ providers are using transparent caching proxies that are set up incorrectly: - They cache content with "no cache" directive in HTTP header (Pragma: no-cache & Cache-Control: no-store) - They ignore query string part of the URL for caching The combination of 1, 2 and 3 has resulted in the Netflix streaming issue. Netflix has started using query string part of the URL to request the movie pieces. Since the content is cached incorrectly, the Netflix player tries to get a fragment of the movie but gets a completely different movie piece from the proxy and shows the error message. Affected ISPs have to reconfigure their proxies to: Take query string into account OR Respect "no cache" directive OR Turn them off for Netflix CDN IP range as caching Netflix streaming does not provide any benefit to the ISP. We encourage you to send the above to your ISP - as this is how they can fix the issue. If enough of you speak - then your ISP might do something about it.

Im interested in what that means from a 'non-geek' point of view.

Does it mean:

ISPs caches are setup to try and cache stuff that is video, but Netflix's content 'breaks' the cache somehow? presumably because of DRM?

Geekzone

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).

robjg63

4161 posts

Uber Geek
+1 received by user: 1427

Subscriber

#1058167 2-Jun-2014 19:48

NonprayingMantis:

feedback from Unblock - US

Thanks for all your help now with this issue, we no longer need any further testing to be carried out and have concluded our investigations. 1. Netflix recently changed the format of URLs for US and Canadian CDN used for video streaming 2. The affected NZ providers are using transparent caching proxies for the Netflix CDN range of IP addresses. They are NOT using these for other IP ranges we tested. 3. The affected NZ providers are using transparent caching proxies that are set up incorrectly: - They cache content with "no cache" directive in HTTP header (Pragma: no-cache & Cache-Control: no-store) - They ignore query string part of the URL for caching The combination of 1, 2 and 3 has resulted in the Netflix streaming issue. Netflix has started using query string part of the URL to request the movie pieces. Since the content is cached incorrectly, the Netflix player tries to get a fragment of the movie but gets a completely different movie piece from the proxy and shows the error message. Affected ISPs have to reconfigure their proxies to: Take query string into account OR Respect "no cache" directive OR Turn them off for Netflix CDN IP range as caching Netflix streaming does not provide any benefit to the ISP. We encourage you to send the above to your ISP - as this is how they can fix the issue. If enough of you speak - then your ISP might do something about it.

Im interested in what that means from a 'non-geek' point of view.

Does it mean:

ISPs caches are setup to try and cache stuff that is video, but Netflix's content 'breaks' the cache somehow? presumably because of DRM?

I have assumed it means roughly the chunks of video are coming through from Netflix with a flag that says dont cache me and they are being cached by the ISPs proxy server anyway.
This means that you start streaming something - (if you can get it started) and there is a request sent for the next chunk of video file - the proxy has some of chunk of video file that it has mistakenly cached from some other streaming requests and it tries to stream this down to you. The software knows this is not the one you should be getting and it fails. Wouldnt totally swear to the accuracy of this but I think its close enough.

Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler

Lurch

1061 posts

Uber Geek
+1 received by user: 71

#1058189 2-Jun-2014 20:06

dejadeadnz:
Just curious, what video bitrate do you view things at? I am using Unotelly and the performance isn't too flash on either their DNS service or the VPN. I used to be able to do 4300 with minimal rebufferings apart from the initial buffer but lately have had to drop things down to 3850 and there are still one or two rebuffers

Not sure haven't checked, just let it pick what it deems correct for the stream and the HD looks spot on. Netflix has adaptive streaming so takes care of the stream, usually gives me the best results.

I can try tomorrow forcing it to another rate?

freitasm

BDFL - Memuneh
80655 posts

Uber Geek
+1 received by user: 41052

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1058193 2-Jun-2014 20:10

Dlownz: What should the DNS settings be on the xbox

Seeing your problem IS NOT related to this thread you should create a new topic just for your configuration.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

dejadeadnz

2394 posts

Uber Geek
+1 received by user: 2287
Inactive user

#1058241 2-Jun-2014 21:12

Lurch:
dejadeadnz:
Just curious, what video bitrate do you view things at? I am using Unotelly and the performance isn't too flash on either their DNS service or the VPN. I used to be able to do 4300 with minimal rebufferings apart from the initial buffer but lately have had to drop things down to 3850 and there are still one or two rebuffers

Not sure haven't checked, just let it pick what it deems correct for the stream and the HD looks spot on. Netflix has adaptive streaming so takes care of the stream, usually gives me the best results.

I can try tomorrow forcing it to another rate?

If you can that would be great. Can you try forcing to 3850 or 4300 (ctrl+shift+alt+s together on a PC) and see what your performance is like?

Thanks!

1 | ... | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | ... | 53