/build/static/layout/Breadcrumb_cap_w.png

PXE-E53 error

I am trying to boot into PXE in order to capture an image. I am getting the error PXE-E53: No boot filename received.

I don't know how to fix this. I know I captured the image of this computer before but it was in a different subnet at the time. Does it matter if my KACE2000 is in a different subnet from the computer to be imaged?

Thanks.


0 Comments   [ + ] Show comments

Answers (2)

Posted by: dugullett 11 years ago
Red Belt
2

Check option 67 in your DHCP scope. Make sure it's set to kbox2000.0.


Comments:
  • Since my office moved to another building it didn't occur to me that I couldn't do this, but the network admin says that I can't. - jfrasier 11 years ago
    • If you have to rely on someone else to set your DHCP options, and they are unwilling then you might want to look into creating a bootable flash drive. - dugullett 11 years ago
  • The only way to pxe is to set this option. On MS DHCP, its option 66, on linux and other servers its know as next-server and should be set to the ip of the K2000. Option 67 or bootfile should be k2000.0 (though kbox2000.0 does work, its just legacy).

    As dugullett mentioned, if they won't set this for you, you will have to use the CD/USB option to network boot.

    Corey
    Lead L3 Enterprise Solutions Engineer, K2000
    If my response was helpful, please rate it! - cserrins 11 years ago
Posted by: SMal.tmcc 11 years ago
Red Belt
2

If you are running MS dhcp the server gods can easily add the options on a per subnet basis.  If they will not work with you talk to your network people about getting a vlan and switch in you new area that is on the same vlan or your own private vlan (we do this in our test lab, and set dhcp options on this subnet).

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ