Some wireless bridge clients intermittently do not get DHCP IP address after association
I'm having an issue where some mobile equipment using a WB will show registered with the WLC but will not always get an IP address. Instead the history for the device in Prime shows a blank IP address and IP Address Type "not detected". This appears to be happening randomly on different access points at different times.
Here is a snippet of the history for one of the WBs with this issue.
I haven't been able to find anything on a problem like this.
Re: Some wireless bridge clients intermittently do not get DHCP IP address after association
first try to relate this to specific hardware.
The client handles the DHCP request.
some drivers want to renew/reuse a previously obtained IP-address and DO NOT request a new one.
and they ignore the NACK received from the DHCP server. -> here the driver needs update or you need manually release/renew the address.
second check your DHCP server logs, it may be the DHCP server receives the request and returns the response, but for any reason the respons is not sent over the wifi to the client, this will need further troubleshooting.
Everyone likes to go fast. The speed of your business, your network and your Wi-Fi is critical to how quickly you can move forward.
In this latest generation of wireless networking, Wi-Fi 6, speed is a focus, but it’s not about just individual devi...
My report tells you the experimental results of the performance of Cisco ClientLink supported on Cisco Aironet access points. You can remember the great performance of ClientLink forever.I have learned that new access points for IEEE802.11ax are Cisco ...
Join us live on Tuesday, March 3 at 10:00 am PT (and on demand after) to learn about how Wi-Fi 6 and 5G will change the wireless landscape in the enterprise? We'll be talking to Cisco's wireless CTO, Matt MacPherson, who will dive into each of t...
Join us live on Tuesday, March 3 at 10:00 am PT (and on demand after) to learn about how Wi-Fi 6 and 5G will change the wireless landscape in the enterprise? We'll be talking to Cisco's wireless CTO, Matt MacPherson, who will dive into each of these techn...
SymptomsWe deploy an SSO pair of 5520's in our DC and DR sites running 220.127.116.11 code.Our Enterprise WLAN had been somewhat reliable until several months back. Suddenly users began creating service tickets complaining that one or sometimes both...