Forum Discussion

Troglodyte23's avatar
Troglodyte23
Tuning in
3 months ago

Laptop can no longer see Hub 5

Our Lenovo laptop was working with Hub5 fine yesterday. Today it can't see the hub. It can see various other networks, and will hotspot from my phone. But not our hub. All my other devices - two other laptops, Xbox and phones can all connect to the hub.

I have: Run all Windoze updates, restarted laptop. Restarted hub, checked drivers up to date on network adapter, reset network settings to factory.

No change. Any ideas?

 

 

 

 

  • Client62's avatar
    Client62
    Alessandro Volta

    Has some kind soul used the Connect app and paused the wrong device i.e. your laptop ?

  • It is very strange that Virgin do not post the answer to this issue on the community.
    This is a known issue with the new hubs and there seems to be no solution.???
    - just attracting random uninformed random comments that are of no help.

  • Adduxi's avatar
    Adduxi
    Very Insightful Person

    What is this known issue?  The usual answer is given by Client62  i.e. Mac filtering by the app.

  • Steve1077's avatar
    Steve1077
    On our wavelength

    I had this on the 5g signal, when I set the channel manually to 44 it worked

  • Client62's avatar
    Client62
    Alessandro Volta

    On 5GHz channels 36 or 44 are a good place to start as the 5GHz Wi-Fi service
    begins without delay.

    Selecting a DFS channel 52 to 144 will result in minutes of delay before the start of the 5GHz Wi-Fi service,
    if you don't expect this it is very easy to conclude the 5GHz Wi-Fi has failed.

    • Adduxi's avatar
      Adduxi
      Very Insightful Person

      Over the years I’ve use ASUS routers and now using Omada AP’s and they never picked any DFS channels that I can remember. 

  • Fixed it. 

    I'd changed channels, frequencies, done a complete IP reset etc etc and nothing worked. 

    I got a wired connection using ethernet ( and an ethernet to USB C adapter).

    Windows insisted that the WiFi adapter driver was up to date. I downloaded a driver direct from the Intel website. I used the Intel tool to select and install a driver, and then restarted.

    It works.