FAQ: Windows 8.1 and Windows 10 AdHoc network support solution

Download: AdhocConnect.exe

IMPORTANT NOTES:

Note 1: Flex WiFi units on the 26 firmware or above now implement a Soft-AP network type which is compatible with all major operating systems. This FAQ applies to Flex WiFi units with firmware 21 or lower, or iTach WiFi units.

Note 2: This Adhoc solution no longer works reliably for the majority of windows machines. The most reliable method for connection to Adhoc networks is to use an iOS, or MacOS, or Windows device pior to Windows 8.1.

---

Starting with Windows 8.1, Microsoft reduced support for Adhoc Wifi networks.  As a result, Windows 8.1 does not detect or display Adhoc networks in the list of available wireless networks (also known as the "wireless network picker").   Windows 10 behavior is slightly different, as it does detect and display available Adhoc networks, but when attempting to connect, it fails with a "Cannot Connect to Network" error.

This is a problem when using Windows 8.1 or Windows 10 to perform initial setup/provisioning of iTach WiFi or iTach Flex WiFi devices.

Some WiFi adapter manufacturers provide their own wireless management software with support for Adhoc networks.  However, if this is not the case, a workaround procedure is described below to allow manual connection to Adhoc networks, using the Windows command shell.

Also any iOS device (iPhone, iPad, iPod), or Mac OS X device can connect to adhoc networks and can be used to perform the configuration of the Global Caché device.

UPDATE - 8/24/2016 - We have created a script called AdhocConnect.exe to automate this process.

UPDATE - 12/13/2019 - We have received several reports of users receiving an "ibss type not valid" error running this script.  If this occurs the wireless driver on your PC does not support ad-hoc and unfortunately that machine cannot be used for provisioning ad-hoc devices.

The following gif shows an example usage of the AdhocConnect.exe script.

 

 

After the connection is completed by the AdhocConnect.exe script open a browser and continue setup per normal setup instructions by entering the unit's default IP address in your browser.

 

Note: If the AdhocConnect.exe script gives an error including "ibss type not valid" this may mean that the wireless card in your machine does not support Adhoc.  In these cases a different device must be used.

 

Manual Entry

If you would like to manually enter the commands the instructions are maintained below.

Because the wireless network picker in Windows 8.1 does not show Adhoc networks, connection must be done with several manual steps. 

(A text file is attached containing all required commands and instructions, allowing cut/paste of commands, and a find/replace of the <ssid> parameter).

From the Start Menu, find and launch "Command Prompt", or type "cmd.exe" and <ENTER> in the search box.

To see all networks in range, including Adhoc, run the following command in the command window:

> netsh wlan show networks

SETUP

The following must be done once for each network:

• 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 adhoc network (as shown by "netsh wlan show networks") into the "Network name" field
• Configure security settings accordingly
• Uncheck "Start this connection automatically" (important)
• Click "Next", then "Close"

Run the following command. Replace <ssid> with the SSID of your network for all following commands:

> netsh wlan set profileparameter <ssid> connectiontype=ibss

***NOTE***

For Windows 10, the command is:

> netsh wlan set profileparameter <ssid> connectiontype=ibss connectionmode=manual

CONNECT

After setting up, run the following command whenever you want to connect:

> netsh wlan connect <ssid>

Replace <ssid> with the SSID of your wireless network.

Hovering over the WiFi icon in the system tray will show the name of the network you are currently connected to, even if it's an adhoc network (the network picker will not show it if it's adhoc). The name is also visible in "Network and Sharing Center" window.

DISCONNECT

To disconnect from the adhoc network connect to a different network, turn off WiFi, or run the following command:

> netsh wlan disconnect

CLEANUP

To remove the network profile from Windows, run the following command:

> netsh wlan delete profile <ssid>

Source: http://answers.microsoft.com/en-us/windows/forum/windows8_1-networking/windows-81-ad-hoc-not-showing/5d75d887-ff59-425e-a480-9f80ada63627

An additional note on Adhoc. There have been reported issues with the need to enable Adhoc mode within the Wireless Adapter drivers for the PC.

Go to Device Manager-->Network Adapters--><your wireless adapter>-->Advanced.

There may be a setting for Adhoc mode available. If attempting to connect to Adhoc with an iTach that uses 802.11b, do not have 802.11n Adhoc mode enabled.  Please let us know other examples that you find within the driver settings by commenting on this post.

***Microsoft Surface devices do not support Adhoc in the embedded wireless chipset in use.**

There is also another utility available that does not require the command line solution that is outlined above.

Download the Wi-Fi Scanner found here: http://lizardsystems.com/wi-fi-scanner/.

After running, the iTach or Flex may show up in the list of broadcasting devices. Right-click on it and select "Connect". If it is successful, try opening a browser and entering the default IP of the iTach (169.254.1.70) or Flex (192.168.1.70). If the device has connected, the web configuration page will appear, and you can proceed with configuring the device to connect to the local SSID.

It may be necessary to Disconnect the device with the Wi-Fi Scanner after completing the configuration.