This has been a repetitive thorn in my side when dealing with BOOT P.
Controller has been reset to factory default. I plug in my ethernet cable and open up BOOT-P. I see the query right away and assign the controller an IP address in the relation list. The IP address is in the same range as my laptop. When I try to disable BOOT-P, the connection times out and I get a socket connect error.
This happens on multiple laptops, on CLX processors and on SLCs. Sometimes if I open the controller properties AFTER assigning an IP address and then give it a description, it will then allow me to disable BOOT-P, but not always.
This is one of those times, I can't seem to get this damn thing to keep it's IP address. Does anyone know what causes this and how to avoid it?
Controller has been reset to factory default. I plug in my ethernet cable and open up BOOT-P. I see the query right away and assign the controller an IP address in the relation list. The IP address is in the same range as my laptop. When I try to disable BOOT-P, the connection times out and I get a socket connect error.
This happens on multiple laptops, on CLX processors and on SLCs. Sometimes if I open the controller properties AFTER assigning an IP address and then give it a description, it will then allow me to disable BOOT-P, but not always.
This is one of those times, I can't seem to get this damn thing to keep it's IP address. Does anyone know what causes this and how to avoid it?