Static IP clients stuck on dhcp_reqd after upgrade to LAP

Unanswered Question
Sep 17th, 2007
User Badges:

I have wireless thermal printers that have static IP addresses. They are on an open wlan and the dhcp required box is not checked.


The client gets hung at DHCP_REQD even though the client has a static address.


Controllers are standalone wlc4402(x2) running 41.1.185.0. Access-points are a mix of 1510, 1231 and 1242. Clients running 802.1x PEAP and DHCP are ok (different SSID).



This is the log from the WCS troubleshooting window:

09/17/2007 06:57:49 EDT INFO 42.201.0.40 Controller association request message received.

09/17/2007 06:57:49 EDT INFO 42.201.0.40 Received reassociation request from client.

09/17/2007 06:57:49 EDT INFO 42.201.0.40 The wlan to which client is connecting does not require 802 1x authentication.

09/17/2007 06:57:49 EDT INFO 42.201.0.40 Client does not have an IP address yet.

09/17/2007 06:57:49 EDT INFO 42.201.0.40 Client Moved to DHCP Required State.

09/17/2007 06:57:49 EDT INFO 42.201.0.40 Client moved to associated state successfully.

09/17/2007 07:00:00 EDT INFO 42.201.0.40 Controller association request message received.

09/17/2007 07:00:00 EDT INFO 42.201.0.40 Received reassociation request from client.

09/17/2007 07:00:00 EDT INFO 42.201.0.40 The wlan to which client is connecting does not require 802 1x authentication.

09/17/2007 07:00:00 EDT INFO 42.201.0.40 Client does not have an IP address yet.

09/17/2007 07:00:00 EDT INFO 42.201.0.40 Client Moved to DHCP Required State.

09/17/2007 07:00:00 EDT INFO 42.201.0.40 Client moved to associated state successfully.

09/17/2007 07:00:05 EDT INFO 42.201.0.40 Controller association request message received.

09/17/2007 07:00:05 EDT INFO 42.201.0.40 Received reassociation request from client.

09/17/2007 07:00:05 EDT INFO 42.201.0.40 The wlan to which client is connecting does not require 802 1x authentication.

09/17/2007 07:00:05 EDT INFO 42.201.0.40 Client does not have an IP address yet.

09/17/2007 07:00:05 EDT INFO 42.201.0.40 Client Moved to DHCP Required State.

09/17/2007 07:00:05 EDT INFO 42.201.0.40 Client moved to associated state successfully.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
irisrios Fri, 09/21/2007 - 09:51
User Badges:
  • Silver, 250 points or more

When configuring the WLAN on the controller make sure DHCP addr.assigent is option is not set for the SSID

c.netherton Fri, 09/21/2007 - 10:03
User Badges:

As mentioned above, the DHCP Required box is NOT set for that SSID.

Scott Fella Wed, 06/04/2008 - 05:24
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    The Hall of Fame designation is a lifetime achievement award based on significant overall achievements in the community. 

  • Cisco Designated VIP,

    2017 Wireless

Does you thermal printer go into sleep mode? Check the power setting on the wireless and make sure you have it set to maximum performance. I have seen this when the WLC doesn't see the client because the device goes into sleep mode and shuts the wireless card down.

s.hellman Wed, 06/04/2008 - 22:06
User Badges:

We got wireless network cameras (Axis 207W) that only connects when they are configured with DHCP, If they are configured with IP-addresses they get stuck at DHCP_REQ.

Our Laptops connects with both DHCP or IP configured, on the same WLAN as the cameras.

The cameras has no sleep mode.

nilsson.magnus Tue, 10/14/2008 - 01:06
User Badges:

Have seen the same problem on a 4402 running 4.2.112. The debug client [client_mac]command in the controller gives:

DHCP_REQD (7) DHCP Policy timeout

DHCP_REQD (7) Pem timed out, Try to delete client in 10 secs.

Lhausklsg Tue, 08/23/2016 - 05:45
User Badges:

I know it is alomost 10 years ago, this ticket has been created.
But I had the same issue.

My solution: Enable "Passive Client" in wireless advanced...

Actions

This Discussion