dmciver wrote:Yet another frustrating round with (non)tech support at Roku. Finally a supervisor agreed the problem must be on my router, so they're replacing my Roku 3 -- yeah, that makes sense.
So I decided to do drop in a spare Apple Airport Express BEHIND my Juniper (so they're in line with each other, double NAT on the Apple) -- guess what works like a champ?
Very puzzling, right - my Airport Express router is handing out the same DNS info (that it's getting from the Juniper) -- so I'm still determined it's something incompatible or how the Roku is querying for multicast when it initializes the network.
Should someone else run into a very frustrating round of network connectivity errors with their Roku, I suggest installing a cheap SOHO grade firewall on your network and putting the Roku behind it. Regardless of how many other devices you have working flawlessly on your network (e.g. Apple TV, Dish w/ sling adapter, VoIP phones, etc, etc)
dmciver wrote:Yes - juniper is pingable on the LAN. As someone else mentioned, if the roku can't get an IP address or ping the LAN you get other errors. I'm fairly certain this has to do with multicast announcements.
Port 80 / 443 (http and https) are both wide open and unfiltered from the LAN to the internet.
Users browsing this forum: tkfan75 and 40 guests