Garrett Gustafson May 28, 2015 • 7 • General / Tech Tips & Solutions
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.
(A text file is attached containing all required commands and instructions, allowing cut/paste of commands, and a find/replace of the <ssid> parameter).
Because the wireless network picker in Windows 8.1 does not show Adhoc networks, connection must be done with several manual steps.Source: http://answers.microsoft.com/en-us/windows/forum/windows8_1-network...
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
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
For Windows 10, the command is:> netsh wlan set profileparameter <ssid> connectiontype=ibss connectionmode=manual
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.
To disconnect from the adhoc network connect to a different network, turn off WiFi, or run the following command:> netsh wlan disconnect
To remove the network profile from Windows, run the following command:> netsh wlan delete profile <ssid>
Brian Kerth Jun 16 • General / Announcements
The latest firmware is available for the Flex_IP and Flex_WiFi units on the Downloads page here: http://www.globalcache.com/downloads/
This is a minor (non-critical) update with a small fix that will increase the speed of IR transmission in some cases.
To update the firmware on your device, download iHelp 4.92 and follow the instructions here: http://www.globalcache.com/support/upgrade-flex-firmware/
Be sure to check your current firmware version and hardware (PCB_PN) revision as detailed in the instructions for compatibility before updating.
Brian Kerth Jun 15 • Utilities / FAQ's and Tutorials
New tutorial on using iLearn found here:
Brian Kerth Jun 14 • iTach / iTach FAQ's
While configuring the iTach WiFi units (WFIR,WFSL,WFCC) in Adhoc mode, you may run into challenges attempting to add the unit to your wireless network. When the iTach is connected to the network, or in Adhoc mode, the LED above the power input will blink once-per-second. When the unit is configured, but not connecting, the LED will be steady ON. Below is a list of known issues that users have encountered:
The Flex Wifi is 802.11b, 2.4 gHz. Networks without allowed connectivity for 802.11b will not allow the iTach to connect.
For the Ubitiquity Unifi, please see this forum post on how to enable 802.11b:
Wifi channels 12 and 13 are not supported. These are normally only seen on non-US routers.
Non-alphanumeric characters (!,?,-,^) may not work if used in the SSID or password. Please use only letters or numbers (upper or lower case).
Network security type, SSID and security information are case sensitive, and must be correctly and identically entered to allow for iTach connectivity.
Security type and information must match the type of security that is enabled. WEP Authentication and WEP keys should not be entered for a WPA secure network and vice versa.
WPA/WPA2 Mixed Mode: Routers will sometimes have this option as "Mixed", "Both", or "Auto". We recommend NOT using mixed mode. Please enable "WPA2 (PSK) Only", as available.
One basic test for Security settings is to set the router and Flex to "OPEN" security. If the unit connects, the issue is most likely the password, or the Mixed mode setting.
If all of these fail, change the wireless radio mode for the network to 802.11b only mode. If your unit connects once this setting is changed, then the wireless router or access point you are using does not properly implement a mixed radio mode and will need to stay in 802.11b only mode or a new wireless router or access point must be added to the network.
For connecting to Adhoc mode in Windows 8.1 and 10, please view this FAQ:
For information on how to reset the unit, please view this FAQ:
If you are still having difficulties after reviewing these items, please contact email@example.com, or open a direct ticket using this support portal.