MAC client dont get an ipaddress

  • 1
  • Question
  • Updated 4 years ago
  • Answered

We have about 5 % of our students MAC product ProBook and MACair. They don't get an IPaddress, we are using ap370 and 6.1r2.

We can see that the mac product is talking to the DHCP-server via Tools - Client monitor.

Our students tell us that they are on the Wireless at home


Photo of Jan Boje

Jan Boje

  • 47 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of Brian Powers

Brian Powers, Champ

  • 396 Posts
  • 92 Reply Likes
The first thing I'd look at is the DHCP server.  Is its pool depleted?  What does the Client Monitor log show?  Can you paste it here?  Can you statically assign an unused IP, SM, DG and DNS servers and the device work?

Are you able to get packet captures from the device and/or AP end?  The HM Help File details out how to do a packet capture from the AP.
Photo of Andrew Garcia

Andrew Garcia, Official Rep

  • 368 Posts
  • 120 Reply Likes
Check the QoS rate control & queuing policy defined for the user profile used by those MAC clients to make sure the 11ac rates are correct. 

See this thread for more info:
https://community.aerohive.com/aerohive/topics/ap_370_no_connectivity

Photo of Jan Boje

Jan Boje

  • 47 Posts
  • 0 Reply Likes


Thanks Andrew I have just looked at our QoS and they are "good".

I have been working at the problem to day, we have made a firewall rule in the accesspoint. seems that some computer is affected bye this rule. It allows student to get an ipaddress from DHCP-server and get DNS. But they are not allowed to go on the internet.

some computers get an IPaddress and some does not get an IPAddress,  I can't see a system.

below you can see from client monitor a client that don't get an IPaddress.

any good idea ?


03/24/2014 01:41:17 PM  70188BA22C3D  E01C413790D4  AG01         DETAIL  (4422)Rx <specific> probe req (rssi 27dB)

03/24/2014 01:41:17 PM  70188BA22C3D  E01C4137BED4  AG03         DETAIL  (5421)Rx <specific> probe req (rssi 35dB)

03/24/2014 01:41:17 PM  70188BA22C3D  E01C4137BED4  AG03         DETAIL  (5422)Rx <specific> probe req (rssi 35dB

03/24/2014 01:41:17 PM  70188BA22C3D  E01C4137BED4  AG03         INFO    (5423)Suppressed by high density, reason:continuous-probe

03/24/2014 01:41:17 PM  70188BA22C3D  E01C4137BEE8  AG03         BASIC   (5424)Rx auth <open> (frame 1, rssi 9dB)

03/24/2014 01:41:17 PM  70188BA22C3D  E01C4137BEE8  AG03         BASIC   (5425)Tx auth <open> (frame 2, status 0, pwr 20dBm)

03/24/2014 01:41:17 PM  70188BA22C3D  E01C4137BEE8  AG03         BASIC   (5426)Rx assoc req (rssi 55dB)

03/24/2014 01:41:17 PM  70188BA22C3D  E01C4137BEE8  AG03         BASIC   (5427)Tx assoc resp <accept> (status 0, pwr 20dBm)

03/24/2014 01:41:17 PM  70188BA22C3D  E01C4137BEE8  AG03         INFO    (5428)Open auth is starting (at if=wifi1.1)

03/24/2014 01:41:17 PM  70188BA22C3D  E01C4137BEE8  AG03         BASIC   (5429)Authentication is successfully finished (at if=wifi1.1)



Photo of Andrew Garcia

Andrew Garcia, Official Rep

  • 368 Posts
  • 120 Reply Likes
Can you post the firewall policy, so we can take a look at it?

Photo of Jan Boje

Jan Boje

  • 47 Posts
  • 0 Reply Likes
sorry I am on Danish time
GU-DC3 is our DHCP-server



Photo of Roberto Casula

Roberto Casula, Champ

  • 231 Posts
  • 111 Reply Likes
You will need a rule allowing the DHCP DISCOVER to the all nets broadcast address (255.255.255.255). Without this, DHCP RENEW will work (unicast to the DHCP server) but an initial discover will fail.

Alternatively, you can allow Any to Any on the default "DHCP-Server" service which will cover both broadcast and unicast outbound from the client.
Photo of Jan Boje

Jan Boje

  • 47 Posts
  • 0 Reply Likes

Thanks have already tried it and it works, thanks again.