I would recommend running a VLAN probe on all of your VLANs to see which one responds with that subnet. If you can't find one, I'd like to see a client monitor so we can see what the DHCP process looks like for that client. Or we can get a packet capture to get an indepth view of the DHCP process.
We can run a VLAN probe in the HiveManager GUI, or you can run it on the CLI of an AP with the following command:
int mgt0 dhcp-probe vlan-range # #
Where you see the #, we would enter the VLAN number we are testing. You can do a range, for example (int mgt0 dhcp-probe vlan-range 1 5, to scan VLANs 1-5), or you can do a single VLAN (int mgt0 dhcp-probe vlan-range 5 5, to scan a single VLAN, VLAN 5 in this case).
Packet capture guides (depending on your HiveManager platform)
HiveManager Classic (myhive.aerohive.com)-https://thehivecommunity.aerohive.com/s/article/Packet-Capture
HiveManager (formerly NG, cloud.aerohive.com)- https://thehivecommunity.aerohive.com/s/article/Packet-Capture-in-NG
Also if you're going through a CWP, the client will be assigned an internal IP address temporarily until they get through the CWP and fully authenticate, in which case they would be pulling from your usual DHCP server. If you're using a CWP object, check the network settings within that object to see what IP range we're giving clients while they go through the CWP.
