EA-N66 times out getting DHCP from Cisco AP

[s814jdh]

Here at the office there is a Cisco AP providing Internet access that is isolated away from our internal network. That way devices not owned by the company (phones, vendor laptops, etc) can use their wifi connections to get to the Internet. More than just guest mode on consumer routers, these APs connect directly to Internet provider lines and are physically separate from our internal network.

I am trying to use the EA-N66 as a wireless ethernet adapter from a Windows 7 PC. GUI of the EA-N66 says that I am connected to the Cisco AP, but my Windows 7 PC times out trying to get an address assigned from DHCP. I can connect using the same PC and the onboard wireless adapter and get a DHCP address allocated immediately.

I have also tried using the same EA-N66 to connect to a different wireless network, and it worked just fine to allocate an IP address of the wireless network to my PC from the DHCP server on that network.

So my question is, can the Cisco AP be configured in a way to recognize the EA-N66 device as one capable of acting as a network bridge (company went to great lengths to isolate the internal wired network and this "external" wireless network at the office) and not assign a DHCP address? Is it possible that some configuration in the Cisco AP sees the request being made by the EA-N66 on behalf of the PC to get a DCHP reservation and won't assign one because the device could potentially be used to bridge networks?

 

[jdabbs]

I cannot speak for every Cisco AP (that's anything from Best Buy fodder to Aironet), but here's what I can do from my Cisco WLC:

Identify any AP broadcasting in range of one of my APs (rogue AP detection)
Report if a rogue AP is broadcasting with my WLAN's SSID
Note if any of my wireless clients connect to a rogue AP
Determine if a rogue AP is connected to my network (with some limitations)
Flag the AP as a threat if it meets specified criteria
Blacklist clients by MAC
Drop traffic from clients that use static IPs or steal/reuse IPs from other clients (basically any IP that there is not a valid IP/MAC combo for)

Things I can do to mess up a rogue AP's day:
Boot every client that joins the rogue AP's wireless network

I've always been concerned about APs being connected to our wireless network, and haven't really thought about a rogue AP being connected to the wireless network with wired clients attached. I'm not sure how it would be handled. It could be that the Asus AP has been flagged as a rogue, and denied connectivity accordingly. It could also be that the controller keeps track of the MACs used to join the wireless network. The PC, using the MAC of the wired NIC (assuming the AP is acting as a bridge) would not have an corresponding connection event and may be treated differently.