codengine / AdhocManager

Managing application to create and configure a hosted / AdHoc Network
MIT License
7 stars 2 forks source link

windows 10 Home/Pro x64 gives error when start selected. #5

Open swgmike opened 10 months ago

swgmike commented 10 months ago

I'm trying to use this program so that I can transfer files between two laptops point to point wirelessly without them needing to be connected to the router and outside world. Both are Dell laptops of the same model, 1) Win 10 Home with Dell 1708 2g wireless card, 2) Win 10 Pro with Intel 9260 AC that is 2G/5G.

1) Hence I'll need to connect on 2G between the wireless card, but the software doesn't have a selection for which band to use. 2). My SSID on each laptop has that laptops name. The manage connections for the wifi shows a red X on each laptop because I'm not connected to the router at home. 3). If I select start or the Network Connections followed by start I get the following on either laptop, Nor does each laptop pick either SSID I entered.

Output screen

The hosted network mode has been set to allow. The SSID of the hosted network has been successfully changed. The user key passphrase of the hosted network has been successfully changed.

The hosted network couldn't be started. The group or resource is not in the correct state to perform the requested operation.

4). I couldn't find info on your website for these error messages. Moreover disabling and enabling the Wifi manage connection shown doesn;'t fix the problem, nor does uninstalling and reinstalling the network driver.

Both laptops work connecting to the internet directly, and I've been able to transfer files between via network sharing; however, the ISP router sometimes resets, so I wanted to do laptop to laptop ad-hoc to bypass the router til the files are transfered over to the other laptop which is about 200 gigs. With the router, I'm lucky to get halfway done after 8 hours and the thing resets and have to start over.

If I do "Show Wlan Drivers" I see that "Hosted network supported:No" . Is this the reason even though the start status message says it was set to allow?

swgmike commented 10 months ago

I did some further investigation and came across this on a MSoft forum. It's Windows 10's WDI problem.

Same wireless chip, same problem as your, emailed to Killer and here the response:

"The Windows 10 version of our driver does not support the "Hosted Network" feature because Microsofts own WDI driver does not yet support this. Microsoft is having all wireless vendors move to the WDI model, thus this feature will not work on Windows 10 drivers until after Microsoft has decided to implement it in their base wireless WDI driver.

So it appears MIcorosoft doesn't ad-hoc capability on new WIndows OS' such as win 10. The forum stated to go back to the Windows 8.1 driver for the wifi card. I assume it comes with its own WIDI driver and doesn't have this problem. However, my laptop uses the same driver for Windows 8/8.1/win10 since laptop originally came with Windows 8 and has been upgraded to windows 10.

So is there a free opensource WIDI driver for Windows 10 to ad-hoc will work again?

swgmike commented 10 months ago

Intels explanation of ad-hoc removal. Looks like Intel 7260 and earlier can do it per their driver. https://www.intel.com/content/www/us/en/support/articles/000023257/wireless.html

You may want to update the tool that checks for this and gives the user a clear message that their wifi chipset doesn't support it.