We have a wireless network and everything was fine until the welchia worm. We have fixed the worm problem but all of a sudden we are now seeing computers that have ad hoc activated in the wireless settings is this a result of the welchia or can it be a some file sharing program that was installed and is activating ad hoc. This is causing a probblem since our wireless network uses access pionts. Has anyone ever seen this before?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Ad Hoc is being activated
- Thread starter scotch
- Start date
Operating system?
Adapter make and model?
Client software?
WEP?
Radius or other 802.1x?
If your clients are all set to infrastructure mode, they may see other possible APs and ad hoc clients, but this should not compromise your network.
Adapter make and model?
Client software?
WEP?
Radius or other 802.1x?
If your clients are all set to infrastructure mode, they may see other possible APs and ad hoc clients, but this should not compromise your network.
- Thread starter
- #3
The machines that pick up the ad hoc network are all xp os.
We have lucent accesss pionts and the orinoco gold and proxim a and g wireless cards and the laptops are all intergrated wireless mostly gateways and dells . we are using the micrsoft client with 128 wep, no radius. If someone configured a wireless card wrong and turned on ad hoc and gave it the same essid as the the access points and same password can this cause a problem with the wireless computers that are configured right.
We have lucent accesss pionts and the orinoco gold and proxim a and g wireless cards and the laptops are all intergrated wireless mostly gateways and dells . we are using the micrsoft client with 128 wep, no radius. If someone configured a wireless card wrong and turned on ad hoc and gave it the same essid as the the access points and same password can this cause a problem with the wireless computers that are configured right.
You are going to see a lot of available points of connection, you might consider running Net Stumbler on one notebook client to see what is in your wireless space.
Warning: I like Net Stumbler, but be sure you have a good registry monitoring or uninstallation tool running prior to installing this application. It installs some NDIS service entries that could completely confound the entries from your regular use of your wireless adapter. You really need to know, and therefore can later easily remove, entries made in c:\windows\system32 for NDIS services.
As you are using the XP Wireless Zero Configuration service, it is important the each client have the authentication and mode properties set correctly. In your case you should disable the 802.1x authentication, remove the WPA Hotfix #815493 through Control Panel, Add/Remove programs, and in setting authentication check to enable only AP access from your list of secured APs. The mode of course should be infrastructure and not adhoc.
This MS KB article explains the importance of creating a preferred list of available sites, and indirectly the issue of why SSID broadcast should be on and not disabled:
Warning: I like Net Stumbler, but be sure you have a good registry monitoring or uninstallation tool running prior to installing this application. It installs some NDIS service entries that could completely confound the entries from your regular use of your wireless adapter. You really need to know, and therefore can later easily remove, entries made in c:\windows\system32 for NDIS services.
As you are using the XP Wireless Zero Configuration service, it is important the each client have the authentication and mode properties set correctly. In your case you should disable the 802.1x authentication, remove the WPA Hotfix #815493 through Control Panel, Add/Remove programs, and in setting authentication check to enable only AP access from your list of secured APs. The mode of course should be infrastructure and not adhoc.
This MS KB article explains the importance of creating a preferred list of available sites, and indirectly the issue of why SSID broadcast should be on and not disabled:
- Status
Similar threads
- Locked
- Question