Server ignoring (some) reservations

[Big Jim]

I have DHCP running on a W 2012 R2 server (with failover)

I have just installed 2 identical IP Cameras, i set them up initially with auto-assigned IPs, then I gave them both a reservation using IPv4 in the DHCP "control panel"
1 of them works fine, 1 is still being handed out an address from the "pool" instead of the static IP I want it to have.

I also have a BT cloud based phone made by Yealink that the server isn't handing out the assigned static IP to either.

I have looked at the log in c:/windows/system32/DHCP and it doesn't reference either the assigned static IPs, the auto assigned IPs from the pool or the NETBIOS names.
The log on the failover DHCP server shows even less information.


any ideas what I need to be doing or where I need to be looking ?

 

[HCHTech]

Did you get the MAC address correct when you were doing the reservation? I have seen devices that have a MAC address printed on them, but show up on the network with a MAC address that has one character different (usually the last character incremented by 1). So I would run an IP scanner on the network to find out what MAC address it is actually advertising and then use that in the reservation.

 

[Sky-Knight]

Yeah double check the MAC address, because it's probably fat fingered.

Better way to make them? Delete your old reservation, right click on the lease attached to that camera to make a new one. That will make one based on the current IP address. Then go edit that reservation to change the IP.

No chance of terminal fat finger when you do that.

 

[HCHTech]

No chance of terminal fat finger when you do that.

I can't wait until we all have to start typing IPv6 addresses for stuff. NOT.

 

[Big Jim]

mac address is correct in both cases, already tried making new reservations,
MAC is same as reported by the device in config, the MAC windows is picking up and the one picked up by an IP scanner.

oh also when I make a reservation it does not appear in the list of IP leases. I removed the reservation and it appeared back in the list of leased IPs

 

[Sky-Knight]

I can't wait until we all have to start typing IPv6 addresses for stuff. NOT.

*If* You use its short hand sytax correctly, it's not that bad. But yes... that's a thing.

@Big Jim It sounds like your device isn't standards compliant. Unplug it, delete the lease off the server, and let it sit for half an hour or so. Then power the device back up. It should get the correct address then. It sounds like it won't let go of an existing lease because it's prioritizing renewal over address change. It's a VERY common issue with China junk IoT devices.

 

[Haole Boy]

I haven't touched a camera in a while, so I'm not sure this is still relevant, but I seem to recall needing to update the firmware in a couple of cameras a few years ago. Is perhaps one of them updated and the other not?

Harry Z

 

[SlickMinnow]

@Big Jim
Did you get this one figured out?

 

[SAFCasper]

I had some weird quirks with DHCP on a 2012R2 server yesterday. Not quite the same but sounds similar.

Was resolved by reconciling the DHCP scope. Suddenly about 15 leases appeared which weren't showing previously and the VOIP phones I was troubleshooting burst into life.

https://www.serverbrain.org/mainten...le a scope,then reconcile the server's scopes.

 

[Big Jim]

@Big Jim
Did you get this one figured out?

Kind of, I think I ended up setting the IP pool to start at the IP I needed and the server then assigned the correct IP to the camera.
Once that was done I reset the IP pool back to how it was before.
Have since purchased a 3rd one and that one (like the first one) setup just fine.

Still haven't managed to get the BT Yealink cloud/IP phone to be correctly assigned, but that really doesn't matter since I cannot access it anyway. so long as it has an internet connection I can make and receive calls