Tech help that's really helpful!
Created: 03 Oct 2007 ::: Last updated: 08 Oct 2007
Applies to:
_ Win95
_ Win98
_ WinMe
_ Win 2000/NT
X WinXP
X WinVista
_ MacOS
By Andy Walker
Have you been in a public place with your laptop (usually an airport) and noticed a Wi-Fi network called "Free Internet" or "Free Wi-Fi," or something like that, and yet, when you try to connect, it won’t?
Here’s what’s going on: Your Wi-Fi-enabled computer is able to go into “ad-hoc” mode. That means that it can connect to another Wi-Fi-enabled computer nearby, usually within 300 feet.
The problem is that if you connect to this so-called free Wi-Fi network, your system too will also send out beacons for that network.
If you connect to one of these in an airport lounge, and then power up your notebook on the plane, your system will start to advertise itself as a "Free Public Wi-Fi" access point.
The cycle continues when other passengers connect to this ad-hoc connection. Then their machines will advertise "Free Public Wi-Fi" too. These SSIDs spread as travelers open their laptops all over the world.
To ensure that your computer doesn’t suffer this problem, use a third-party Wi-Fi utility to manage your wireless connections. Windows is the culprit here. A Wi-Fi client may have come with your wireless router so use that. Or instead, download the free Boingo client from http://boingo.com/download.html and use that.
If you still want to let Windows manage Wi-Fi, here’s a fix for XP and Vista.
First, let’s talk about XP. Follow these steps:

Ad-hoc networks will no longer be detected when you browse for access points.
To do this on Vista, the fix is a little more geeky:

Note that Netsh is a command-line scripting utility that lets you display or modify the network configuration of a computer.
This page was printed from www.cyberwalker.com on 21/11/2009
Copyright Cyberwalker Media Inc. © 2009.