Forum Discussion

joecaldwell's avatar
joecaldwell
Channel Surfer
3 years ago
Solved

Roku TCL TV can't connect to my Verizon 8800L MIFI hotspot

My Roku TV has stopped connecting to my Verizon 8800L hotspot.  It has worked well until a couple of days ago.  Error code is  14.40.  I have tried the recommendations I have seen of restarting both ...
tv & player wifi
  • AvsGunnar's avatar
    AvsGunnar
    3 years ago

    joecaldwell 

    I think the next step is to look at MAC address Filtering and Guest Network access.

    First thing to do is to verify that MAC address Filtering is not Enabled. (When enabled, will only allow approved MAC addresses to access the main network).  If you find it enabled, disable it and then restart the hotspot and the Roku devices.  If still no-go, then I would enable it and add the RokuTV MAC address to the list in order to test if I could now connect.  https://www.verizon.com/support/knowledge-base-220974/

    Next thing I would try is to enable the Guest network.  Since the Guest network is unaffected by many settings of the main network, allows you to test whether the RokuTV can can at least connect to the hotspot.  If so, then lets us know it is a Setting somewhere on the main network preventing connection. https://www.verizon.com/support/knowledge-base-220986/.  Try leaving the password empty first (or at least very simple if an empty password/open network for the Guest Network is not allowed).

    If the Guest Network works for you, then I would go back into the main network and try creating an open network. (open network=no password).  If the RokuTV connects, then try assigning a simple password with no special characters).  If connects again, then getting closer to narrowing it to a password issue.

    ----

    Start at the top of this list and work through in that order as allows us to rule out different contributing factors.

joecaldwell's avatar
joecaldwell
Channel Surfer
3 years ago

Thanks.  We do have a MAC address and the TV sees the MIFI hotspot as well as other available networks.  Just can't connect to the MIFI.  I reset the network connection.  I turned off the 5 Ghz part of the MIFI but connection still fails.  Have no idea what to try next.

 

Joe

AvsGunnar's avatar
AvsGunnar
Community Streaming Expert
3 years ago

joecaldwell 

I think the next step is to look at MAC address Filtering and Guest Network access.

First thing to do is to verify that MAC address Filtering is not Enabled. (When enabled, will only allow approved MAC addresses to access the main network).  If you find it enabled, disable it and then restart the hotspot and the Roku devices.  If still no-go, then I would enable it and add the RokuTV MAC address to the list in order to test if I could now connect.  https://www.verizon.com/support/knowledge-base-220974/

Next thing I would try is to enable the Guest network.  Since the Guest network is unaffected by many settings of the main network, allows you to test whether the RokuTV can can at least connect to the hotspot.  If so, then lets us know it is a Setting somewhere on the main network preventing connection. https://www.verizon.com/support/knowledge-base-220986/.  Try leaving the password empty first (or at least very simple if an empty password/open network for the Guest Network is not allowed).

If the Guest Network works for you, then I would go back into the main network and try creating an open network. (open network=no password).  If the RokuTV connects, then try assigning a simple password with no special characters).  If connects again, then getting closer to narrowing it to a password issue.

----

Start at the top of this list and work through in that order as allows us to rule out different contributing factors.

  • joecaldwell's avatar
    joecaldwell
    Channel Surfer
    3 years ago

    Thanks for your great help.  When I got to the MAC filtering list, it showed the Roku TV as "Blocked" for some unknown reason.  We went into the MIFI and unblocked the Roku TV and it then connected to the MIFI hotspot just like normal.  Have no idea how it got changed but I think this may have fixed the problem.  Thanks again.

     

    Joe