Windows 10: "Unable to Connect" to my home WiFi on brand new Surface

Another ghostly Windows issue for one of my clients.


They recently got a brand new Surface. The computer seems to work on every single Wi-Fi network known to man except the one in their home.


The network is made up of a series of Araknis Wi-Fi access points. Every single device in the home, mobile device and any Apple computer seems to work fine. She however has a Surface.


If we completely remove the network from the device tree and restart the computer, we can connect to it. But as soon as the computer is removed from the network or powers down, the next time you try to connect, the message "Cannot connect to network" is what is displayed when you try to force the connection.


For testing purposes, to made sure the network isn't flagging the computer for some reason, we've connected a brand new access point to the system with a different SSID and have no trouble_ so we are 99% certain the issue lies between the computer and the Access points in use here... but it seems illogical to me that I should tell them they need to replace their whole wi-fi network in order to get this one computer working correctly.


So... words of wisdom oh smarter-than-I-at-Windows-Gurus?

:)

 

wifi issue brand new Surface pro 3

I just swapped a brand new SP3 with Windows 10. However, the WiFi stops periodically. Trouble shooting will not identify any problem. I reinstalled the driver as Barke suggested, still does not work. Every time when I turn on the system, WiFi will be connect.
But it will not get on to the internet. I have to turn WiFi off and on. My old SP3 did not have this problem after I install Windows 10 preview and even after clean installation. It is a very annoying issue. Can anyone help? Please do not ask me whether I
update it. It is all updated. Brand new SP3 OME windows 10!

Thanks,

Jason

 

Cannot connect to wifi


Hello, I'm running a Surface Pro 3. I use it for work and my personal life. At work, we have three different wifi connections. My preferred one is the "guest" wifi. I've been using it since I got my Surface almost 2 years ago. I've never had an issue. Two days ago, I noticed I wasn't connected to the web. I disconnected and reconnected to the guest wifi. It showed "No Internet, secured". Chrome shows that the DNS address could not be found. I am able to connect to the other two wifi options and access the web (I prefer the guest access because it doesn't limit what I do on the web). I took the surface home with me and again, no issues connecting to the wifi at home, or some public wifi I tired. Everyone I've talked to is able to connect to the guest wifi at work without issue. My network administrator (who is technically not allowed to work on my surface because it is not a company device) says nothing has changed on his end.
I followed some of the trouble shooting steps on other posts. I did run the system file checker and determined that opencl.dll (I think that is the file name) was damaged. I was unable to repair it.
I am hoping someone could possibly run me through troubleshooting this issue? It's an annoyance more than anything and I would like to see if I can fix it. Thanks in advance.

 

Is it possible to set up a new manual wifi connection from the command line?

I'm trying to work out a solution to set up ad-hock wifi connections in Windows 8.1 based on the suggestions in a post on Micsrosoft's answers site. Is there any way to do the first few steps:

• go to "Network and Sharing Center"
  
• click "Set up a new connection or network"
  
• double click "Manually connect to a wireless network"
  
• enter the SSID of the ad-hoc network (as shown by "netsh wlan show networks") into the "Network name" field
  
• configure security settings accordingly
  
• uncheck "Start this connection automatically" (important)
  

...without using the windows dialogs?