Forum Discussion
I work at a dorm school, all staff live here also. over the weekend we have had 4 Roku devices all stop connecting to Wifi. 1 device was a 75" TV used for display in a common location, that was less then 2 years old.
I called support for the TV brand they gave me Roku support, I called Roku support.
What fixed this TV, (haven't tested this everywhere), we had the "Bandwidth Saver" setting turned on. she told me to turn it off. (The only step I hadn't tried myself), the next time I attempted the wifi it connected!
She also had me connect to my phone as a hotspot, and at the moment the wifi connected I was already on the hotspot when I tried connecting to the wifi again. not sure if any of this was part of the fix or not. I had also did a system shutdown and restart and clearing of the network settings prior to the tech support conversation.
I hope to help our other staff reconnect their personal Roku's as well using this same fix. We urge people to use Bandwidth Saver because we all share the same bandwidth here at our school.
The lady did say that sometimes having the Bandwidth saver turned on, while trying to reconnect causes connection to fail, this is first I've heard of that, so hope this helps everyone else.
I'll try to comment again or add to this if it works in on other devices.
- RaymondKn3 years agoChannel Surfer
Update after a few days of trial and error.
Part of my problem here at the school looks like a failover dhcp server vm. I have no idea why only Roku devices decide to not connect to wifi when it is on but only Roku devices failed.
The only thing I did recently with that server was move the VM from old hardware to new hardware, it still has all the same settings and the failover was still intact and working between the 2 dhcp servers.
I looked at time clocks and made sure they were in sync as well as many other settings, I tried again today to turn on the failover server and the Roku TV couldn't connect to wifi.
This might be related to others issues, but might not, since I can't prove at this time the server isn't at fault. I disabled the failover server and will be building another, because I need failover.
I will have to readdress this if the issue returns.
Since absolutely no other device seemed to have issues, and all the people here having trouble, I still believe something needs fixed, but at this time, I need to rebuild.
Hope someone who knows more might put this with something else and figure it out if they are related.
Thanks