W
Waterboi
Hi, I'm having wifi issues on Windows 10. I've just moved into a new office and cannot connect.
I can still connect to my phone's hotspot but obviously that's not a long term solution. Also, other devices like my gigabyte laptop and my boss's iMac computer can connect to the same network just fine.
So here's what happens:
When I select the network and enter the correct password, it comes up with "unable to connect to this network" (refer img below)
When I troubleshoot the issue, it says i need to use an ethernet cable, but that seems silly as I've never needed one to use the wifi. Plus, the other devices did not need one to connect.
I get a similar message when troubleshooting is completed:
So I've run ipconfig/all on the command prompt and received the following:
Microsoft Windows [Version 10.0.18362.959]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Jaws
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I219-V
Physical Address. . . . . . . . . : 10-7B-44-15-1D-73
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter WiFi:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Qualcomm Atheros AR938x Wireless Network Adapter
Physical Address. . . . . . . . . : C0-25-E9-1F-6C-FA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 12-25-E9-1F-6C-FA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 22-25-E9-1F-6C-FA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
C:\WINDOWS\system32>
------------------------
SO! Seeing that I have media disconnect issues, I reset WINSOCK and IP Stack with the following commands:
netsh winsock reset
netsh int ip reset
I then restart my computer... and it did not work
I've updated Windows to the latest version and all my drivers are up to date
Does anyone know what the issue is? Is the ethernet issue message connected to media disconnect? I've never encountered this issue before and I've moved offices a few times so I know my system is able to connect to different networks.. just not this one I guess...
Appreciate any ideas anyone may have
Continue reading...
I can still connect to my phone's hotspot but obviously that's not a long term solution. Also, other devices like my gigabyte laptop and my boss's iMac computer can connect to the same network just fine.
So here's what happens:
When I select the network and enter the correct password, it comes up with "unable to connect to this network" (refer img below)
When I troubleshoot the issue, it says i need to use an ethernet cable, but that seems silly as I've never needed one to use the wifi. Plus, the other devices did not need one to connect.
I get a similar message when troubleshooting is completed:
So I've run ipconfig/all on the command prompt and received the following:
Microsoft Windows [Version 10.0.18362.959]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Jaws
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I219-V
Physical Address. . . . . . . . . : 10-7B-44-15-1D-73
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter WiFi:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Qualcomm Atheros AR938x Wireless Network Adapter
Physical Address. . . . . . . . . : C0-25-E9-1F-6C-FA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 12-25-E9-1F-6C-FA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 11:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 22-25-E9-1F-6C-FA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
C:\WINDOWS\system32>
------------------------
SO! Seeing that I have media disconnect issues, I reset WINSOCK and IP Stack with the following commands:
netsh winsock reset
netsh int ip reset
I then restart my computer... and it did not work
I've updated Windows to the latest version and all my drivers are up to date
Does anyone know what the issue is? Is the ethernet issue message connected to media disconnect? I've never encountered this issue before and I've moved offices a few times so I know my system is able to connect to different networks.. just not this one I guess...
Appreciate any ideas anyone may have
Continue reading...