11-07-2018 09:28 AM
The AP's can get IP by DHCP but the clients don't, dhcp probe says it works, if I set up with static IP it connects but DNS doesnt work, not ours not even public (8.8.8.8/8.8.4.4) but on firewall says it has traffic (really small amount) so on the firewall no policies are blocking it and on AP's firewall I have full permit, I have tried everything.
Network Service: DNS Permit
Network Service: [-any-] Permit
and default also Permit, still nothing.
Also a PC on the same vlan gets DHCP IP, DNS, all.
Solved! Go to Solution.
11-07-2018 03:31 PM
I've done it and while looking at it I found something strange in the Network Interface and User Configuration, the Management and Native VLAN Settings were set "wrong" (trunk vlan) and just by switching it to the "correct" (vlan 10, mine of wifi) solved it, so thank you for the inside point that help solve it.
11-07-2018 03:31 PM
I've done it and while looking at it I found something strange in the Network Interface and User Configuration, the Management and Native VLAN Settings were set "wrong" (trunk vlan) and just by switching it to the "correct" (vlan 10, mine of wifi) solved it, so thank you for the inside point that help solve it.
11-07-2018 01:09 PM
Could you get a packet capture taken while the client device attempts to get an IP address? This will let us see what DHCP packets are being generated, which will help us narrow down the issue for you.
This guide goes over how to run a packet capture in HiveManager (formerly NG): https://thehivecommunity.aerohive.com/s/article/Packet-Capture-in-NG
This guide goes over how to run a packet capture in HiveManager Classic: https://thehivecommunity.aerohive.com/s/article/Packet-Capture
There are credentials for our FTP server at the end of those guides, if you could just let me know the file name once you've uploaded the packet capture, I'll take a look and let you know what we're seeing.