asked on DHCP Reservation BAD_ADDRESS
I am trying to implement some DHCP Reservations. It is on a SBS 2011 Server. When I look in the DHCP under Address Leases I see 172.18.2.132 BAD_ADDRESS with a description "This Address is ALready In Use".
I am assuming it means the IP address is already in use? When I sort the leases there is only one 172.18.2.132 that shows up. How can I tell what other device is using 172.18.2.132? (if that is the problem)
I am assuming it means the IP address is already in use? When I sort the leases there is only one 172.18.2.132 that shows up. How can I tell what other device is using 172.18.2.132? (if that is the problem)
SBSDHCP
Last Comment
John
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Well.... it look like it already assigned 132 which is normal. I am adding the reservations after the fact and will be stepping on some already assigned IP address. So how to you implement reservations "after the fact"?
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
There is only one DHCP server. It is the SBS 2011 Server. What is was doing made sense. When the day started out 132 was assigned by the DHCP server. Then I decided I wanted to reserve that IP and since it was already assigned I got the error.
So what I did was re-define my scope so it wouldn't pass out IPs in the range I want to reserve and rebooted. Still getting the BAD_ADDRESS error but not if the IP should be in use at this point. So now what?
So what I did was re-define my scope so it wouldn't pass out IPs in the range I want to reserve and rebooted. Still getting the BAD_ADDRESS error but not if the IP should be in use at this point. So now what?
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
That was a pain. Even re-assigning the range on the scope and rebooting the workstations did not release their IP address. I had to go to each computer individually and release it. Did finally get all the reservations added and it appears to be working.
Thanks. Yes! It was a pain for us as well, and partly good luck that we found the machine relatively quickly