Hi
Sorry, me again.
This may appear like a strange question, but has anyone experienced problems with the new Cisco tri-mode cards getting an IP address via DHCP after successful authentication?
The reason that I ask is that our client has recently purchased through us a batch of these cards and, after having ironed out most of the problems with them (upgrade to IOS on APs etc), we are left with a strange issue. They have two VLANs with one SSID, the ACS providing the VLAN tagging based on user credentials. On VLAN2, authenticating and getting a DHCP-assigned IP address is fine everytime. However, on the other VLAN (where there are two W2K domains) it is totally hit and miss if it gets assigned an IP address or not, but usually not. When we staticaly assign the IP address, as one would expect, it goes straight through.
VLAN2 is a Class C size subnet. VLAN1 is a 21 bit mask, hence potentially having 2048 clients (although it is more like 300 at the moment). Their DHCP scope is large, almost 1000 addresses. I am guessing this is definitely not helping. We tried making reservations in the scope, but that did not really help. The weird thing is that the old Cisco .11b 340 series cards get a DHCP-address almost immediately on both VLANs.
Anyone seen anything like this? Any feedback much appreciated.
Marc
