Issue with PXE booting on SDA

Hi Everyone,

I've had this issue for a while on one of my RSA servers, and I'm not exactly sure why.  When I PXE boot into my server, it gives me the below error.


I have all of my DHCP servers set up correctly, and also have my RSA pointing to a known good DNS server.  Has anyone seen this before? 

0 Comments   [ + ] Show comments

Answers (2)

Posted by: Nico_K 2 years ago
Red Belt

at first you can see that it tries to boot from http:///boot/boot.php instead of http://sda/boot.php.
This means the RSA cannot find the correct name.

Which version(s) do you use?
VM (I see vmware  with a really outdated year=

Do the other RSA work well?
What happens if you use the onboard DHCP of the RSA`?

  • Nico,

    My SDA is at 8.0.194
    The RSA is at 8.0.194
    Vmware ESXi 6.0.0

    The other RSA devices at other locations seem to work fine.

    I have tried onboard DHCP and it hasn't worked out very well either. - zgillette 2 years ago
Posted by: Net_Taco 1 year ago
White Belt

Did you ever figure this out?

We have the same http:///boot/boot.php error that times out. We have rebuilt the DHCP scope policies, tested with on-boarding DHCP, recreated the DNS records but nothing has worked. This seems like a setting within SDA that needs to either point to the IP address or host name of the SDA in between http://IP or Hostname/boot/boot.php but for the life of me I can not locate it. Kace support hasn't been helpful as we have been dealing with this for over 3 weeks now and can not image.

  • please contact support after you verified the environment is supported. - Nico_K 1 year ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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