We have a DHCP server. The clients are configured to receive IP addresses when the boot up. Normally, this would not be a problem. Except that we also have a security device permits/denies a client based on the IP address.
For example, Computer A initially received address of x.x.x.30. The security device has a setting that tells it that x.x.x.30 has full access.
Computer A shuts down for the night to go home.
Now the DHCP server gets rebooted (maintenance work, changing the battery backup, etc).
Next day, when Computer A boots up, I would expect it to get x.x.x.30. Instead it gets x.x.x.40. The security device has a setting that tells it x.x.x.30 has full access, but x.x.x.40 has limited or no access.
So Computer A tries to gain access to the secured site, but is denied because it has obtained a different IP address.
Why would the DHCP server assign a new address if the all Computer A did was shut down
and the server was rebooted AFTER Computer was down?
Also, aside from assigning reservations on the DHCP server (which I would prefer not to do), is there a method to insure that the client was ALWAYS receive the same IP address EACH AND EVERY SINGLE TIME?
I also have several devices that are assigned static addresses. If my range to give out is x.x.x.15 to x.x.x.100 AND some of these devices fall into that category, do I have to, repeat, have to exclude these addresses on the DHCP server?
Hoping to hear from you.