It can be annoying when the WLAN Auto Configuration service does not turn on. Please follow the steps provided below that may fix the issue:
1. Click Start -> All Program -> Accessories. 2. Right click on “Command Prompt”, select "Run as Administrator" to open a command prompt. 3. In the command prompt window that opens, type the following commands one by one:
netsh winsock reset catalog
netsh int ipv4 reset reset.log
netsh int ipv6 reset reset.log
4. Reboot the computer and check if the wireless works.
I had very similar symptoms on an XPS. I ran the commands as described above. I still have a red x over the wifi connections icon. The mouse over error still states, "not connected - no connections available." Network diagnostics tries to start the windows wireless service but times out. It asks for an Ethernet connection. Network diagnostics then recommends plugging in an ethernet cable. I did that and it seemed to update some info but did not fix the issue.
DELL-Rajath N
4 Operator
•
1.8K Posts
0
March 21st, 2013 04:00
Hi ADAM2393,
It can be annoying when the WLAN Auto Configuration service does not turn on. Please follow the steps provided below that may fix the issue:
1. Click Start -> All Program -> Accessories.
2. Right click on “Command Prompt”, select "Run as Administrator" to open a command prompt.
3. In the command prompt window that opens, type the following commands one by one:
netsh winsock reset catalog
netsh int ipv4 reset reset.log
netsh int ipv6 reset reset.log
4. Reboot the computer and check if the wireless works.
Please let me know about the status.
gsanmartin
2 Posts
0
October 4th, 2014 14:00
I had very similar symptoms on an XPS. I ran the commands as described above. I still have a red x over the wifi connections icon. The mouse over error still states, "not connected - no connections available." Network diagnostics tries to start the windows wireless service but times out. It asks for an Ethernet connection. Network diagnostics then recommends plugging in an ethernet cable. I did that and it seemed to update some info but did not fix the issue.