![]() ![]() I am pretty sure it's not in the DHCP RFC. Why would the DHCP server replace the MAC with this convoluted string? Is this covered in any manual? It's an inverted hexadecimal representation of the ip address that is being complained about. They all have unique first 3 characters, but everything after that is 1150a. What surprised me was that these bad_address entries' reservations were changed to have an invalid MAC address.Īll of them start with a 0 or a 1 and are only 8 characters long. I assume they will fail either at lease renewal or the next time they are power cycled. Some of them seemed to remember their IP and are still functional, even though their reservation says bad_address. The server (of course) has a UPS and so does most of our infrastructure (switches etc).īut it seems that one type of Printer that we have, were all switched to bad_address and they could not pick up their reserved IP address. Some were right after the other (1 or 2 seconds) others Yesterday we had a series of short power outages. That said, I am using Window 2003 and we are running DHCP. ![]() I understand about Bad_Address and the things that can cause it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |