The DHCP server did not respond to the Client.

  • 1
  • Question
  • Updated 1 year ago
Hello,

I am having DHCP issue from while and somehow I am not able to figure it out that what exactly it causing this. Any help would be appreciated. 
Photo of Arpit Parikh

Arpit Parikh

  • 8 Posts
  • 0 Reply Likes

Posted 1 year ago

  • 1
Photo of Sam Lynn

Sam Lynn, Moderator

  • 96 Posts
  • 12 Reply Likes
Hello Arpit Parikh,

Try running a VLAN proble on the CLI of the AP this client is trying to connect to. The command is:

int mgt0 dhcp-probe vlan-range # # 

Where the #s are, we want to enter the VLAN number. If you are only running this on one VLAN, you'll want to enter the VLAN number, put a space, and enter the same number. For example, if you want to run a VLAN probe on VLAN 10, the command would be "intmgt0 dhcp-probe vlan-range 10 10". If you want to run the probe across several VLANs at once, you'll want to put the starting VLAN first followed by the ending VLAN. For example, if you want to run the probe for VLANs 5-10, the command would be "intmgt0 dhcp-probe vlan-range 5 10".

This command sends a DHCP probe down that VLAN. If it gets a response from a DHCP server, the test comes back as successful and gives you the subnet the DHCP should be handing out addresses from. If it fails we'll need to find out why the VLAN is not active, which is likely a switch issue.

Hope this helps!
(Edited)
Photo of Arpit Parikh

Arpit Parikh

  • 8 Posts
  • 0 Reply Likes
Hello Sam,

Thank you so much for your respond and yes I did this and I am getting the right respond with correct IP scope. 

But still getting DHCP error. 
Photo of Sam Lynn

Sam Lynn, Moderator

  • 96 Posts
  • 12 Reply Likes
Hello Arpit Parikh, 

I'm sorry that step didn't help clear up the issue. I would try setting a static IP on your client next. If that works, you know it's an issue with the DHCP server itself and not the Aerohive side of things.

You could also run a packet capture with wireshark to see what DHCP packets you are getting. If you run a packet capture, you'll want to filter for the client device's MAC address that isn't getting an IP address, then sort by packets. You'll want to find the DHCP section and see which of the four DHCP packets you are getting. We should see Discover, Offer, Request, and Acknowledge packets for a successful communication with the DHCP server. If we are only seeing Discover packets, we are likely not getting traffic to the DHCP server. If we see Discover and Offer packets, that typically indicates that the DHCP server is reachable but is not handing out addresses. The most common reason for this would be that the DHCP server is out of addresses, in which case you'll want to lower your lease times and/or increase your IP pool. 

Hope this helps!
Photo of Arpit Parikh

Arpit Parikh

  • 8 Posts
  • 0 Reply Likes
Hello Sam,

I checked my DHCP scope and it looks like I have enough IP pool. 
Also I did lower my lease times from 12 Hours to 8 Hours so let's see weather it helps or not. 

Thanks a lot for all this communication and help , much appreciated.