Menu
Reply
  • 8
  • 0
  • 0
cooltone
Joining in
194 Views
Message 1 of 4
Flag for a moderator

Does Hub 3.0 have security vulnerability on Windows 10?

I just received this notice from my OS:

"WiFI network not secure in Windows 10" and was pointed to this link:

https://support.microsoft.com/en-gb/help/4501036/windows-10-wi-fi-network-not-secure

The webpage certificates are valid, so unlikely to be a scam.

Does the Hub 3.0 have a security vulnerability on Windows 10?

Advice welcome.

0 Kudos
Reply
  • 1.01K
  • 144
  • 217
DJ_Shadow1966
Knows their stuff
184 Views
Message 2 of 4
Flag for a moderator

Re: Does Hub 3.0 have security vulnerability on Windows 10?

Hello

Not aware of any issues with the security of wireless on a Hub 3.0 and Windows are you connected to the hubs wireless or are you connected to an unsecure network ?

You can check the setting on the wireless by going to http://192.168.0.1 logging in with the details on a sticker on the bottom of the hub, once in goto Advanced Settings - Wireless - Security, the most secure is WPA / WPA2.

Regards Mike

I dont work for VirginMedia all opinions are my own.
39 years in IT.
0 Kudos
Reply
  • 3.67K
  • 396
  • 1.29K
Very Insightful Person
Very Insightful Person
164 Views
Message 3 of 4
Flag for a moderator

Re: Does Hub 3.0 have security vulnerability on Windows 10?

Both insecure standards mentioned in the Microsoft article cannot be selected on the Hub so it is likely Advanced settings > Wireless > Security is set to Disable; as DJ_Shadow1966's post mentioned. Should you find this is the case then be aware that Disable is not the default / factory setting.

 

As a Very Insightful Person, I'm here to share my knowledge. I don't work for Virgin Media.

Click to learn more about VIP

 Use Kudos to say thanks

 Mark as Helpful Answer if I've helped

0 Kudos
Reply
  • 8
  • 0
  • 0
cooltone
Joining in
74 Views
Message 4 of 4
Flag for a moderator

Re: Does Hub 3.0 have security vulnerability on Windows 10?

In the end the Hub was well configured.  I found it was client-side, my PC was configured to WPA2-Personal (OK) and TKIP (Not OK). So I updated the encryption to AES, hopefully that solves it.

Many thanks for the support Gentlemen, much appreciated.

Cooltone.

0 Kudos
Reply