Windows 10: I can't connect to a particular network

This has been driving me mad for days, I cannot connect to one particular network in Win10 as it always shows "no internet access" and diagnose tells me that "one or more network protocols is missing" and other times it tells me there was a problem with the access point and it was fixed and restarted, but in reality nothing is fixed, it's still showing no internet access. My trick is to connect to the wifi on my tab and connect it to my Win10 laptop through usb tethering, but this is really cumbersome.

Wifi works flawlessly on ubuntu (dual boot).

UPDATE 1: I also can't connect to the default gateway, when I try to access the router page firefox said the connection has timed out, ditto for chrome, pinging the default gateway also returns "request timed out".

UPDATE 2: I've updated the wireless driver from atheros and restarted but it's still not working

UPDATE 3: flushed dns and resetted winsock, restarted, error still won't budge, does anyone know what steps can I take to troubleshoot if I can't ping even the default gateway?

UPDATE 4: For whatever reason I still can't connect to the wifi broadcasted by the router itself but got a repeater and everything works fine so that saves me from headaches for now.

:)

 

Cannot connect to a particular Wifi Network

Did you find out what the problem was?

 

Cannot connect to a particular Wifi Network

Hello,

I cannot connect to this particular wifi network. Other networks work fine. So it doesn't seem to be a hardware problem.

The network asks my user name and password, Windows shows me a warning and then I have to click connect.

Almost immediately windows asks for my user name and password again. I don't get any message as what went wrong. I then click cancel.

I tried the following:

- updated the wifi driver: was up to date

- stopped anti-virus etc : didn't help.

- placed to computer in a clean boot: didn't help.

- I created a profile and tried to connect through the command line. Weirdly the command line gives the message "Connection request was completed successfully" yet no connection is established. (When I try another wifi network, I get the same message but
this time the message is correct as windows says 'connected' for this network and I can surf the web).

I ran some wlan reports:

1/ For a manual connection (no profile) - I deleted some parts because I could not fully evaluate if posting that information is safe.

Interface:Intel(R) Centrino(R) Wireless-N 2230

Connection Mode:Connection to a secure network without a profile

Profile:TelenetWiFree

SSID:TelenetWiFree

BSS Type:Infrastructure

Session Duration: 0 hours 0 minutes 13 seconds

Disconnect Reason:The operation was cancelled.

8000
2016-08-14T18:13:21
[+]WLAN AutoConfig service started a connection to a wireless network.

Connection Mode: Connection to a secure network without a profile

Profile Name: TelenetWiFree

SSID: TelenetWiFree

BSS Type: Infrastructure

11000
2016-08-14T18:13:21
[+]Wireless network association started.

Authentication: WPA2-Enterprise

Encryption: AES

802.1X Enabled: Yes

11001
2016-08-14T18:13:22
[+]Wireless network association succeeded.

Management Frame Protection Enabled: 0x2500000000

11010
2016-08-14T18:13:22
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T18:13:22
[+]Wireless 802.1x authentication started.

Eap Information: Type 0, Vendor ID 0, Vendor Type 0, Author ID 0

2087
2016-08-14T18:13:22
[+]User Entered Credentials.

107
2016-08-14T18:13:28
[+]Server Certificate Thumbprint: FC F0 BE 34 8A 3D EF CD F2 43 F4 CA F9 80 A3 1E E2 CC 52 DD.
Server Certificate Fully Qualified Domain Name: authentic.telenet.be.

107
2016-08-14T18:13:29
[+]Sending creds to server for Username: [ I deleted this] Domain:

11004
2016-08-14T18:13:29
[+]Wireless security stopped.

Security Hint: The operation was successful.

11010
2016-08-14T18:13:30
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

2/ For the connection from the command line (with profile) - I deleted some parts because I could not fully evaluate if posting that information is safe.

Interface:Intel(R) Centrino(R) Wireless-N 2230

Connection Mode:Manual connection with a profile

Profile:TelenetWiFree

SSID:TelenetWiFree

BSS Type:Infrastructure

Session Duration: 0 hours 0 minutes 9 seconds

Disconnect Reason:Unknown

8000
2016-08-14T19:37:40
[+]WLAN AutoConfig service started a connection to a wireless network.

Connection Mode: Manual connection with a profile

Profile Name: TelenetWiFree

SSID: TelenetWiFree

BSS Type: Infrastructure

11000
2016-08-14T19:37:40
[+]Wireless network association started.

Authentication: WPA2-Enterprise

Encryption: AES

802.1X Enabled: Yes

11001
2016-08-14T19:37:41
[+]Wireless network association succeeded.

Management Frame Protection Enabled: 0x2900000000

11010
2016-08-14T19:37:41
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T19:37:41
[+]Wireless 802.1x authentication started.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

2088
2016-08-14T19:37:41
[+]User Uses Saved Credentials.

107
2016-08-14T19:37:41
[+]Sending creds to server for Username: [I deleted this]. Domain:

11004
2016-08-14T19:37:41
[+]Wireless security stopped.

Security Hint: The operation was successful.

11010
2016-08-14T19:37:41
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T19:37:41
[+]Wireless 802.1x authentication started.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

12014
2016-08-14T19:37:41
[+]Wireless 802.1x authentication was restarted.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

Restart Reason: Msm Initiated

100
2016-08-14T19:37:41
[+]Authentication succeeded for EAP method type 25.

2088
2016-08-14T19:37:41
[+]User Uses Saved Credentials.

107
2016-08-14T19:37:41
[+]Sending creds to server for Username: [I deleted this]. Domain:

11004
2016-08-14T19:37:41
[+]Wireless security stopped.

Security Hint: The operation was successful.

11010
2016-08-14T19:37:42
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T19:37:42
[+]Wireless 802.1x authentication started.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

12014
2016-08-14T19:37:42
[+]Wireless 802.1x authentication was restarted.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

Restart Reason: Msm Initiated

100
2016-08-14T19:37:42
[+]Authentication succeeded for EAP method type 25.

2088
2016-08-14T19:37:42
[+]User Uses Saved Credentials.

107
2016-08-14T19:37:42
[+]Sending creds to server for Username: [I deleted this]. Domain:

11004
2016-08-14T19:37:42
[+]Wireless security stopped.

Security Hint: The operation was successful.

11010
2016-08-14T19:37:42
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T19:37:42
[+]Wireless 802.1x authentication started.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

12014
2016-08-14T19:37:42
[+]Wireless 802.1x authentication was restarted.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

Restart Reason: Msm Initiated

100
2016-08-14T19:37:42
[+]Authentication succeeded for EAP method type 25.

2088
2016-08-14T19:37:42
[+]User Uses Saved Credentials.

107
2016-08-14T19:37:42
[+]Sending creds to server for Username: [I deleted this]. Domain:

11004
2016-08-14T19:37:43
[+]Wireless security stopped.

Security Hint: The operation was successful.

11010
2016-08-14T19:37:43
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T19:37:43
[+]Wireless 802.1x authentication started.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

12014
2016-08-14T19:37:43
[+]Wireless 802.1x authentication was restarted.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

Restart Reason: Msm Initiated

100
2016-08-14T19:37:43
[+]Authentication succeeded for EAP method type 25.

2088
2016-08-14T19:37:43
[+]User Uses Saved Credentials.

107
2016-08-14T19:37:43
[+]Sending creds to server for Username:[I deleted this]. Domain:

11004
2016-08-14T19:37:43
[+]Wireless security stopped.

Security Hint: The operation was successful.

11010
2016-08-14T19:37:43
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T19:37:43
[+]Wireless 802.1x authentication started.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

12014
2016-08-14T19:37:43
[+]Wireless 802.1x authentication was restarted.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

Restart Reason: Msm Initiated

100
2016-08-14T19:37:43
[+]Authentication succeeded for EAP method type 25.

2088
2016-08-14T19:37:43
[+]User Uses Saved Credentials.

107
2016-08-14T19:37:43
[+]Sending creds to server for Username: [I deleted this]. Domain:

11004
2016-08-14T19:37:44
[+]Wireless security stopped.

Security Hint: The operation was successful.

11010
2016-08-14T19:37:44
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T19:37:44
[+]Wireless 802.1x authentication started.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

12014
2016-08-14T19:37:44
[+]Wireless 802.1x authentication was restarted.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

Restart Reason: Msm Initiated

100
2016-08-14T19:37:44
[+]Authentication succeeded for EAP method type 25.

2088
2016-08-14T19:37:44
[+]User Uses Saved Credentials.

107
2016-08-14T19:37:44
[+]Sending creds to server for Username: [I deleted this]. Domain:

11004
2016-08-14T19:37:44
[+]Wireless security stopped.

Security Hint: The operation was successful.

11010
2016-08-14T19:37:44
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T19:37:44
[+]Wireless 802.1x authentication started.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

12014
2016-08-14T19:37:44
[+]Wireless 802.1x authentication was restarted.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

Restart Reason: Msm Initiated

100
2016-08-14T19:37:44
[+]Authentication succeeded for EAP method type 25.

2088
2016-08-14T19:37:44
[+]User Uses Saved Credentials.

107
2016-08-14T19:37:45
[+]Sending creds to server for Username: [I deleted this]. Domain:

11004
2016-08-14T19:37:45
[+]Wireless security stopped.

Security Hint: The operation was successful.

11010
2016-08-14T19:37:45
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T19:37:45
[+]Wireless 802.1x authentication started.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

12014
2016-08-14T19:37:45
[+]Wireless 802.1x authentication was restarted.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

Restart Reason: Msm Initiated

100
2016-08-14T19:37:45
[+]Authentication succeeded for EAP method type 25.

2088
2016-08-14T19:37:45
[+]User Uses Saved Credentials.

107
2016-08-14T19:37:45
[+]Sending creds to server for Username: [I deleted this]. Domain:

11004
2016-08-14T19:37:45
[+]Wireless security stopped.

Security Hint: The operation was successful.

11010
2016-08-14T19:37:45
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T19:37:45
[+]Wireless 802.1x authentication started.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

12014
2016-08-14T19:37:45
[+]Wireless 802.1x authentication was restarted.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

Restart Reason: Msm Initiated

100
2016-08-14T19:37:45
[+]Authentication succeeded for EAP method type 25.

2088
2016-08-14T19:37:45
[+]User Uses Saved Credentials.

107
2016-08-14T19:37:46
[+]Sending creds to server for Username: [I deleted this]. Domain:

11004
2016-08-14T19:37:46
[+]Wireless security stopped.

Security Hint: The operation was successful.

11010
2016-08-14T19:37:46
[+]Wireless security started.

Authentication: WPA2-Enterprise

Encryption: AES

FIPS Mode: Disabled

802.1x Enabled: Yes

12011
2016-08-14T19:37:46
[+]Wireless 802.1x authentication started.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

12014
2016-08-14T19:37:46
[+]Wireless 802.1x authentication was restarted.

Eap Information: Type 25, Vendor ID 0, Vendor Type 0, Author ID 0

Restart Reason: Msm Initiated

100
2016-08-14T19:37:46
[+]Authentication succeeded for EAP method type 25.

2088
2016-08-14T19:37:46
[+]User Uses Saved Credentials.

107
2016-08-14T19:37:46
[+]Sending creds to server for Username: [I deleted this]. Domain:

2089
2016-08-14T19:37:46
[+]EAP session is completing during the authentication phase.

105
2016-08-14T19:37:46
[+]Deleting cached credentials as authentication failed for EAP method type 25.

101
2016-08-14T19:37:46
[+]Authentication failed for EAP method type 25. The error was 0x2B3.

2086
2016-08-14T19:37:46
[+]EapHostPeerGetResult returned a failure.

Eap Method Friendly Name: Microsoft: Protected EAP (PEAP)

Reason code: 691

Root Cause String: Network authentication failed\nThe credentials provided might not be correct.

Repair String: Contact your network administrator\nYour administrator can verify your user name and password.

12013
2016-08-14T19:37:46
[+]Wireless 802.1x authentication failed.

Identity: [I deleted this]

User:

Domain:

Reason: Explicit Eap failure received

Error: 0x2B3

EAP Reason: 0x2B3

EAP Root cause String: Network authentication failed\nThe credentials provided might not be correct.

EAP Error: 0x80420112

11006
2016-08-14T19:37:46
[+]Wireless security failed.



Thank you

 

These symptoms suggest that you have a not-perfect Microsoft driver for your Wi-Fi installed. You can use a utility such as Aida64 to identify your Wi-Fi card and then find official drivers which should work better.

The simplest method is to visit your notebook manufacturer's support site and download the latest Wi-Fi driver. If there is no Windows 10 driver, try that for Windows 8 or 7. Once you download it, right-click and Run as Administrator. It should install OK and your Wi-Fi should work as expected.

There is a chance that Windows Update finds a "newer" driver and replaces your official working driver with the "newer" not-working Microsoft driver. To prevent it, use the show/hide tool to find and hide (disable) the respective update as described in this tutorial.

In the unlikely case that the driver from manufacturer's site doesn't work as epxected, you must use Aida64 to identify the hardware of your Wi-Fi card and then google it to find drivers.

 

Not connecting on one particular network means that there is an issue with that network. Have you asked others if they are having the same problem?

The Missing Protocol is caused by Microsoft removing Guest access and locking down the OS to protect it from Malware.

 

Thanks for the suggestion I'll try this later

As I said, no one else is experiencing issues on the network, nor my other devices and OS, so I'm 100% sure somewhere in my OS something isn't configured right I just haven't figured out what it is.

 

Try flushing the Winsock and Dns. Farbar's Minitoolbox comes in handy for this.