Unable to PXE boot after subnet change [solved in comments]
Hey all,
We recently migrated our K2000 to a new subnet, and now are unable to use ipxe. When attempting to pxe boot the message only displays the local stations IP. I'm curious as to what I need to exactly change to fix this?
We have changed DNS records to reflect the Kbox's new IP. What am I missing?
thanks!
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
Channeler
4 years ago
DNS should no be involved in the iPXE process, if you are using SDA hostname or FQDN, please switch to Static IP.
Post a screenshot showing where it's getting stuck.
Remember that devices need to come INTO the KACE SDA (formerly known as K2000), with the Help of the DHCP.
Is the DHCP pointing to the KACE SDA IP address in Option 66?
Comments:
-
Channeler, I've added a very large and poorly adjusted picture of where it gets stuck.
If I'm reading this correctly, It looks like it actually does pxe boot, and the station is assigned an address (learned a little during lunch on the process).
So I'm thinking it might be what you're saying, and that the DHCP isn't pointing to the new address in option 66. Thoughts? Also, the SDA is on a static address.
edit:
Ok, I think I understand a bit. At this point, I've booted into ipxe, and assigned the client an address. Next step should be loading the client into the SDA, which is controlled by option 66. From there I imagine I'm probably all set. If this is correct, THANK YOU, and learning is fun. - Cheecho 4 years ago-
In the picture, it looks like the computer is trying to find a DHCP with PXE boot information.
(option 66 and option 67).
And it's unable to do so.
I would check the DHCP settings for that particular subnet and the value of option 66. - Channeler 4 years ago-
Changing the DHCP scope in option 66 resolved the issue. Thanks much, this has been a good learning experience. - Cheecho 4 years ago
