Network - Wireless & Wired Connections

[charlesdebatz]

"atc98092" wrote:
Nope, I have CenturyLink as my ISP, and have no issues with any of my Rokus. So it's something with the CL router that is messed up. Not saying it isn't something that CL can control, but I'd log into the router/modem and see if there's any settings that might be blocking Roku access. 

I have taken down and reworked about every aspect of the local network that I can.  As I stated in my prior post, there are not any local connectivity or filter/firewall issues.  Also, I do not think Centurylink is blocking access to the Roku servers.  As I said, I can trigger a security message from the Roku API address using a browser.  If you look carefully at what I posted, you will also see that I do not have a Centurylink router.  At the location in question I have carefully pored over the configurations, I have swapped with different routers, different router firmwares, reset the dynamic IPv4 address to a new one multiple times, etc.  As far as I can tell, the Roku servers have blacklisted the range of Centurylink IP addresses in my area.

The only things I can think of that I have not yet tried are temporarily switching out the DSL modem with a different make and model or setting up a virtual IP address with a VPN.  I may swap out the modem next, but I seriously doubt that will reveal anything new.  As for using a VPN, one is not otherwise needed at the location in question and it adds cost and complexity, so I would rather not do that if I do not have to.

I see you are in the Auburn, WA area.  What modem and router are you using and does Centurylink provide native support for IPv6 where you are?  (I am in the Albuquerque, NM area.  I tried switching to an IPv6 address, but it appears Centurylink does not natively support that where I am, so no help there).

Thanks.

[atc98092]

I missed that you aren't using a CL router/modem. I have the Actiontec C1000A, but I think all of their modems are garbage. I have to keep a fan blowing on mine year round or it ends up locking up eventually. Yes, they do support IPv6 here. It's been a while since I had it disabled, so I can't say for sure if that makes any difference. My Rokus all worked fine when I had IPv6 disabled, but as I said it's been a while since I ran it that way. 

[charlesdebatz]

Resolved!

I swapped the Netgear DM200 DSL modem with an old ZyXEL PK5000Z.  The PK5000Z was set as a DSL modem only with WAN: Transparent Bridging, DHCP: Disabled, Firewall: Medium, WIFI: Disabled.  I literally inserted the PK5000Z in place of the DM200.  No other changes were made, and suddenly Roku servers could be accessed by the Roku set top box.  To be certain this was not a fluke, I re-installed the DM200.  The Roku box was again denied access to Roku servers.

The Netgear DM200 was set in modem mode, firmware v1.0.0.58.  Aside from DSL flavor, there are almost no options that can be set on the DM200 when in modem mode.  There is no firewall available, etc.  The DM200 in question has been in service for years and as far as I know there have not ever been any problems accessing any other internet content.

PRESUMABLY DUE TO SOME OBSCURE BUG, ROKU'S SERVERS AND THE NETGEAR DM200 DSL MODEM RUNNING OVER CENTURYLINK ARE NOT COMPATIBLE.  I am extremely surprised.

[atc98092]

Well, that's interesting. I certainly would have expected the Netgear to have better configuration options than a CL modem. My Actiontec C1000A (very similar to your ZyXEL) has a fair number of things I can change, but nothing like I've seen on a quality router from a major manufacturer. Netgear might be interested in hearing about your issue. I suggest providing them a detailed report, and how the ZyXEL worked as expected. Perhaps it's something they can address with a firmware update, assuming that hardware is still supported. [/font]

[charlesdebatz]

The Netgear DM200 is a budget DSL modem.  Configuring it for "modem" mode bridges the modem directly to the LAN port and disables the router features.  The setting is intended to be used with an external router.

This modem is officially not supported by Centurylink (although it typically will work correctly if a user has enough networking skills to set it up).  I think it was discontinued some time ago.  I expect Netgear lists it as a legacy product.

[nrw276]

I have Centurylink and have had nothing but problems. The roku just will not work with the world's worst internet service. I'm stuck because they just don't care. I have no answers so I'm stuck with two roku devices that I can't use.

[drcristoff]

For what it’s worth it has been some time since I originally posted this thread and the devices have been largely working fine. I have made no further adjustments in my home network and I haven’t experienced the issues that I had originally. At least in my particular case I do believe the issue originated in century link somewhere. Whatever the cause may have been it was not visible to me as the end user.  My best suggestion would be if you are experiencing issues, start with the basics and try to get your Roku device onto a different connection.  If you have a cell phone hotspot give that a shot, if you have to take it to someone else’s house to test give that a try. This will at least help you narrow down whether it is your Roku device or is it something to do with your home network. 

Secondly, as unsatisfying as it may be the problem I had ended up resolving itself with time. If your issue is a transient one it may be that somebody down the road is fiddling with the box that connects you to the internet. 

[ErnestNM]

Drcristoff, I think your initial suspicion about the problem being with the Roku Servers was correct. That is the conclusion I came to the past few days as I worked to try and get 2 Roku Ultras working with a wired connection. My story follows. 1) Bought a Roku Ultra that finally ‘quickly’ connected (wired) after experiencing many of the issues mentioned here and on another thread. And it seemed to stream OK but I didn’t monitor it for long because I realized that the model I was sold was not the 4670R that was advertised. It was a 4660X2 in a box labeled 4661R. I returned it. 2) Bought a 4670R that was in a box labeled 4670R that would not connect (wired) until the next day (today). But it is operating very slow and intermittent. It connected wireless yesterday immediately and worked fine. 3) For both Rokus, after wired connection failures, I connected an old Dell Inspiron 1545 laptop to the same line and it connected immediately both times and a speed test each time gave 15+ Mbps down and 2+ Mbps up speed. I have Comcast Xfinity service with a Motorola MB8600 modem and a Pepwave SURF SOHO MK3 router that allows me to have isolated virtual LANs on all wired and wireless ports. All of our new and old computers, cell phones, and Internet Of Things (IOT) devices have worked flawlessly for several years on this network. 4) Bottom line -> It is likely a problem on Roku’s end and it is just not worth my time, effort, hassle, and frustration to try and solve the problem with a $100 IOT device. Why can my old Sony BDP-BX350 connect immediately and work flawlessly (but doesn’t support HULU anymore; the reason for this purchase) and this state-of-the-art Roku cannot? Answer -> Roku doesn’t make enough money off of box sales to break even and has likely cut technical staff and validation efforts to the bone to improve the bottom line. And, there are several other income generating ventures they are involved with to improve the bottom line that could also be affecting this ‘common issue without a specified solution’. 5) If the problem doesn’t ‘self-correct’ big time within a few days this unit is going back and I will spend the extra $75-$100 to buy an Apple TV 4K streamer and see if it can connect with no problems.

[ErnestNM]

Update:

Well, late yesterday the Roku Ultra started making connections without problem and speed tests were 16 and 17 Mbps which is at or above what our other IOT devices ever measure.   Two possible reasons follow.

1) Roku fixed the problem on OR from their end.

2) I changed the LAN “Port Speed” on my Pepwave SURF SOHO MK3 from “Auto-negotiation” to “100Mbps/Full Duplex”.   I think this did the trick because auto-negotiation seems to be a common problem with other devices as seen on the internet and this is the recommended fix to try first.

So, Roku Ultra it is for now!

[drcristoff]

Well I’m back reading my own thread because guess what... exact same problem again. I’m resisting the urge to do the factory reset trap because I know that will lead me down the frustrating path of trying to activate the device and having the page error on me unless I time it just right. Here is a clue - exact same hardware but what happened is that the line somewhere down the block went bad with century link. They had to switch me to a different “port” on their big switching station. Same exact scenario, all other internet working fine but Roku all messed up. As usual century link no idea what I am talking about.  But here’s the trick, because I’m using the DM200 I have to call tech support to “allow” my device to connect. I think perhaps it may come with some limitations when first activated or something on the network adapts to this different device and then the traffic becomes unblocked. So I would not be surprised if most folks with self supplied modems end up with the same issues on century link. I’ve just got my fingers crossed that it magically resolves itself again like it did last time around.