Is anyone else having trouble accessing Netflix with their Hub 3 or is it just me?
13-10-201813:46 - edited 13-10-201813:48
The problem started when I swapped out the SH2 for the H3 yesterday afternoon. It appears something is blocking my connection from accessing Netflix as you see from the screenshots underneath. Everything else is fine; I get good speeds and surf the web normally.
Running a traceroute to one of VM's Netflix servers produced these results one from Windows and the other from the Hub...
Tracing route to manc-netflix-cdn-02.network.virginmedia.net [18.104.22.168]
over a maximum of 30 hops:
1 6 ms 3 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 36 ms 12 ms hari-core-2a-xe-820-0.network.virginmedia.net [22.214.171.124]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 32 ms 22 ms 21 ms manc-ic-2-ae0-0.network.virginmedia.net [126.96.36.199]
8 25 ms 21 ms 20 ms manc-netflix-cdn-02.network.virginmedia.net [188.8.131.52]
Put the hub 3.0 into modem mode and see if it connects. If it does, your hub 3.0's router side is IP banned on Nteflix's side. In which case contact Netflix to ask them to lift the ban.
Thanks for your assistance Shelke. Carrying out your suggestion of putting the Hub 3 into modem mode does indeed connect. After spending 2 hours on the phone with a very knowledgeable chap from the Netflix technical research team, he could see there was no unintentional IP ban. Under router mode, I am able to sign into Netflix, but I am not able to connect to the rest of Netflix. That would suggest there may be either a fault with my Hub 3.0 or there is a potential issue with the Hub 3.0's firmware that Virgin Media may not be aware of.
It's probably best to wait for one of the members of the VM team to look into it further.
Re: Is anyone else having trouble accessing Netflix with their Hub 3 or is it just me?
28-10-201800:36 - edited 28-10-201800:51
Just a quick update for anyone else who may have the same issue. I requested a new Hub 3 and sure enough, Netflix is back online. My issue was caused by a faulty Hub and not an IP block as previously thought. I would like to thank @Shelke for his/her help here and a special shout out to Jack from the Netflix Technical Research Team for his assistance in diagnosing my issue and the VM technical support for sending out a replacement Hub