chaonan georgianna natthanielle

0 views

Skip to first unread message

Eugene Hill

unread,

Aug 2, 2024, 1:01:12 AM8/2/24

to xiufenfwake

Hi guys. The Microsoft Edge is my favorite browser of all times, really, but not when I try to watch netflix or other video streaming services, it always breaks, I have no ideia what to do anymore. Always when I try to play something there's an error and then I need to reload over and over again, sometimes even when I just play the video it stop working when I try to play again. Help me to keep using this best browser that I've ever seen.

I've ever tried to disable hardware acceleration, enable DRM content, install Microsoft Silverlight and a lot of other things, but I didn't get to watch so far without an error I keep receiving these error codes: D7356-7701 and others related. Is there's still something that can be done to really fix theses erros or I just have to be patient and wait for news versions of the browser?

Nothing can be more frustrating than when you are trying to watch a movie on Netflix and you get disrupted by an error message. One such annoying error code is the Netflix Error NW-2-5. You can get this error code on a smart TV, game console, or Blu-ray player, but what actually causes it, and how can you fix it?

While the content of the error code differs based on the streaming device, the Netflix code NW-2-5 means that your device is not connected to the internet or something like a firewall, parental controls, or proxy is blocking your connection to Netflix. On some streaming devices, the error code might pop up as NW-3-6.

Likewise, where your internet comes from might also affect your experience on Netflix. If your internet service provider (ISP) is having some issues, or you have a faulty router or modem, you might also get an error message.

You can also see the NW-2-5 error code if your streaming device has problems that affect its performance or compatibility with Netflix, such as an outdated app or software, corrupted cache or data, or insufficient memory.

It might be that your Netflix app has crashed, and switching your streaming device off and on should get things going again. It might also help to disconnect your device from a power source before switching it on again.

Switch to a faster network or contact your internet service provider if your internet bandwidth is slower than it should be for streaming. Also, ensure that you are not out of data bandwidth or that your ISP is not throttling your network by running an internet speed test or using a VPN that supports Netflix streaming.

Alternatively, turn off your router, and wait a few seconds before turning and reconnecting it to your device. Then, bring your router closer to the streaming device if they are too far apart or there are obstructions.

For instance, you may need to check and verify your domain name service (DNS) settings and ensure they are set to default or automatic if you stream on game consoles like PlayStation and Xbox. Better still, you can consider switching to a public DNS server like Google DNS.

In most cases, you can fix most Netflix error codes by switching your device on and off or checking your network connection to see if your device is connected. You can also try restarting your home network.

Netflix doesn't work - error "NW-2-5" (network issues) - started about four or five days ago.
When the TV's DNS is manually set to 8.8.8.8 Netflix works, set back to 192.168.20.254 (pihole) it stops.
BUT Netflix works on ALL other devices that go through the Pihole...?? PC, phones, Xbox... they all work, except the TV.

OK here's something weird. To try and narrow down the issue a little I went to the blocklists page in the console and unchecked ALL the lists, planning to enable them one-by-one to see which one is doing it.

I am having the same exact issue but not only with Netflix but Disney Plus and Hulu. Main difference is every Netflix app on my network will not launch unless pointed to a outside DNS server. 4 Rokus, PS4, TVs and Bluray players. Doesn't matter if Pihole is enabled or not. I have also disabled all block lists just like you but still won't launch. Only way around it for me so far is with Cascading Routers. Have the pihole on the forward facing router and all devices on the back router. Set the back router DNS server to the IP of the forward router.

I have the same error code as you and just like you I have disabled pihole, and removed all blocklists. Netflix still wont launch but like I said the main difference is all of my devices are having issues.

Hm, interesting. I have an Asus RT-86U with Merlin, there was a Merlin update recently too. The Asus provides ethernet/wifi to the house, and gets its WAN from the router that was supplied by my telco.

But somehow, Netflix doesn't like talking to a DNS server that is not public, with the router being the only exception (as demonstrated by @JonnyB's router cascade). This is probably due to Netflix seeming to be excruciatingly rigorous at shutting out access via VPN or through a proxy.

Now, I don't have a Netflix account, an Asus Router or an LG TV, so the following paragraphs are kind of a blind shot attempt to apply a mildly related solution to a different problem. You have to decide whether it's worth a try.

When trying to fence my TV from leaving my home network in ways I didn't approve of, I ultimately resorted to putting it into a separate WLAN raised by a separate Zero W where all DNS traffic was forced to Pi-hole, regardless which DNS server my TV was using. To that end, I had to alter the Zero's prerouting table.

As far as I am aware of, Asus routers allow ssh login, so you could give that approach a try by extending your router's iptables. I won't post them, as there is an easier way in your case: You happen to run your router with Merlin, so you can set up DNS Filters.
From the UI, find LAN DNS Filter, switch "Enable DNS-based Filtering" to ON, and select "Router" from Global Filter Mode. Assuming you have defined Pi-hole as local DNS server via the DHCP settings, leave the custom entries blank.
(I am assuming Merlin's documentation as well as a corresponding screenshot are up to date)

Both approaches - iptables via ssh or DNS filters via UI - should produce the same result:
They force any(*) DNS traffic on your network to reroute through Pi-hole.
So when your TV requests to resolve api-global.netflix.com through Google's 8.8.8.8, your router will show that request friendly but firmly to your Pi-hole instead, while your TV thinks it is still talking to Google.

So you just got back home from a long day at school or work and you want to play some games on your Xbox. You fire up the Xbox console to load your favorite game and then you get hit with the "Xbox Game took too long to start" error. What happens now?

This article will go through all the problems that might be happening to your game and console associated with the Xbox games taking too long to start error and the solutions to fix them.

Most common problems with the Xbox consoles can be filtered down to a few root causes. A few of those reasons could be a faulty console, damage to game disc or file, unstable internet connection, and the list goes on. It is important to note that the root of the problem might be too hard to identify, but given the situation, it is important to try to solve the issue first. The corresponding solution might give an insight into what the root of the cause might have been.

Here is a list of 10 possible solutions that you can follow to try and solve your Xbox one games taking too long to start problem. Please read each solution carefully and follow it to the best of your abilities for the best results.

A very simple way of dealing with the error in the game is to delete the saved data and restart your app or game. This is mainly due to the fact that the files and saved data could become corrupted which causes the error code 0x8027025a to occur in the first place.

One of the most core problems that can lead to your console issue "Xbox game took too long to start" error is having a problem with your cache. Xbox consoles store all your temporary files in your cache to help games load faster (similar to how cache works on your browser). However, some of these cache files can get corrupted from time to time and cause the error to occur.

Sometimes changing your region can solve a lot of things (Like watching region-exclusive Netflix shows). In this case, changing your region to the United States should solve the "Took too long to start" error on the Xbox console. This is applicable to all Xbox consoles.

Sometimes, it is not your console's fault and just simply something wrong with the game. If you have tried the above methods and still haven't seen any success, then try to uninstall and reinstall the game that is showing the error. To uninstall the game:

Persistent storage refers to the data storage device that still retains data even after the console has been shut down. Sometimes, this can be the root cause of the error with files becoming corrupted, thus causing the games taking too long to start. To fix it:

In energy save mode, it disables a lot of features in order to conserve more power. Instant On mode on the other hand simply refers to the low-powered state that your Xbox goes into. Switching between these two modes could potentially disable features that are hindering the game or app files from running properly and fix the problem. It is a low-risk solution.

Network configuration can be daunting, especially if you aren't sure what to do. However, it is a fairly straightforward process. Sometimes you just need to adjust the network settings to clear up some of the issues.

Navigate to Settings > Network > Advanced Settings.

If you are experiencing the error because you are running your games from an external hard drive, then try this solution. Sometimes, using an external hard drive is good for saving space but it could cause some problems. To solve this, simply install your applications and games from your external drive to your internal drive. Restart your console after the files are installed and it should work.