Just bought a Compaq Mini 110C for my wife. After initial setup, and by providing the relevant encryption key, it successfully connected to my new WAP4410N no problem. Wireless Connection Control for the SSID is Disabled.
The AP has been configured with three SSID's, one each for 802.11b, -g, & -n devices, with different Security Modes and Encryption Keys applied to suit. This is working well, and with Wireless Connection Control now Enabled, and the device physical addresses entered to the AP table, all my Wireless-G computers, iPod touch's etc are still able to gain access to the network via the correct SSID as one would expect.
However, when I add in the MAC address for the new Mini 110C to SSID-G, which according to ipconfig /all has a Broadcom 802.11b/g WLAN chip in it, the AP says "MAC 6 [its the sixth device to be added to SSID-G] must be 12 Hex chars (0-9 and A-F) with optional delimiters (: or -) and the second bit not an odd number". Repeated attempts to input the physical address 0C:EE:E6... etc result in rejection. So the new notebook will only connect with Wireless Connection Control disabled.
After much research, some odd things are noted...
1) This MAC Address is the first I have encountered that does not have 00 for its first byte (octet). Possible nothing amiss there though, as I see examples listed on various sites.
2) By inputting the first half of the MAC Address (the six digits 0CEEE6) into the MAC Address Lookup and Search tool at About.com, significantly no matches are found. This should have indicated the manufacturer of this wireless device!
3) FYI, 0005B5 is Broadcom Technologies, 000AF7 is Broadcom Corp., 001018 is broadcom corporation & 001BE9 is Broadcom Corporation. None remotely like the 110C!
4) According to Wikipedia, a Universally Administered Address is uniquely assigned to a device by its manufacturer, etc etc. Often as a BIA or "burned in address", as in the case of this Compaq PC. A Locally Administered Address is assigned to a device by a network administrator, over-riding the BIA. Universal and Locally administered addresses are distinguished by setting the second least significant bit of the most significant byte of the address. In my case the most significant byte is 0C (hex) = 00001100 (binary). Second least significant bit is 0, so it is a OUI or Organizationally Unique Identifier. It is also EVEN, and therefore should be acceptable to being typed in to the WAP4410N Wireless Control table! So why does it bomb?
Now I know how to spoof the MAC address for this network adapter by tweaking the registry or using SMAC v2.0 and so on, and I am confident that in minutes I could make this computer connect successfully to the AP with MAC filtering switched back on.
But... I do not like things I do not understand, and anyway what would a PC novice do in a situation like this when trying to access a similar protected network?
So, can anyone offer an explanation as to what is happening with my WAP4410N (going to order a 2nd tomorrow!) and this wee computer? And if I do end up having to spoof to fool it, what MAC Address should I go for?