cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Connected to router not internet PC Win10 Qualcomm AR9485

ash_mistry
Investigator
Investigator

Hi

I have upgraded to the new EE hub and now Windows 10 PC can't connected to the internet (WiFi connection) 

Other devices are ok.

Is something not backwards compatible?

Ash

1 SOLUTION

Accepted Solutions
ash_mistry
Investigator
Investigator

Thank you all.

I have found the solution. 

Somewhere in the past I had manually put in a  DNS  on my network card, and once I set it back to automatic everything worked

 

View solution in original post

4 REPLIES 4
ash_mistry
Investigator
Investigator

Sorry forgot to add when I use network diagnostics or says "devices or resource (DNS) is not responding"

JimM11
Brilliant Contributor
Brilliant Contributor

@ash_mistry If you login to the EE Router, what is the current wireless security type value set at? Details can be found on your router, as you only say upgraded to the new EE hub. Would try lowering the spec on that first. 

Edit It is also an old wireless N adapter, does support 5ghz but you may have to go back to wi-fi 5 compatible, and disable 5ghz band until you get it connected.

XRaySpeX
EE Community Star
EE Community Star

 

I believe that's an old PC & probably has a lesser WiFi then the router.

I think you'll find the router is set to WiFi-6 and/or WPA3 by default. Your device mayn't cope with that. Change the router settings down to WiFi-5 and WPA2. 

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Mobile Phone & Mobile Broadband or Option 2 for Home Broadband & Home Phone

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP
ash_mistry
Investigator
Investigator

Thank you all.

I have found the solution. 

Somewhere in the past I had manually put in a  DNS  on my network card, and once I set it back to automatic everything worked