/build/static/layout/Breadcrumb_cap_w.png

KACE: How Do I Configure SonicWall for PXE Clients?

Summary:  I have a SonicWall.  How do I configure it to allow PXE boot for my K2000 appliance?

Solution:

To configure SonicWALL for PXE clients:

- Open Network | DHCP Server

- Edit DHCP Lease Scope range

- Check box Allow BOOTP Clients to use Range

- Click Advanced tab and enter:

Next Server: IP Address of the TFTP server

Boot File: name of the boot file

Server Name: name of the server (not required)

- Click OK

 


Comments

  • Great tip, thanks. - jcoffey 8 years ago
  • The DHCP configuration requirements have changed for UEFI PXE booting. Anyone know how to configure DHCP on a SonicWALL firewall? This works well using Windows as shown in the attached link, but I have not yet found documentation for SonicWALL configuration and SonicWALL support has been unable to configure multiple objects for the same group option - throws an error duplicate exists.
    https://support.quest.com/kace-systems-deployment-appliance/kb/217556/dhcp-configuration-for-bios-and-uefi-pxe - AKaceUser 5 years ago
    • KACE SDA now uses iPXE and that is an Open Source Protocol, see:
      https://en.wikipedia.org/wiki/IPXE

      All the settings are the same regardless of the Imaging solution being used, the only that will change is the IP address to reflect yours.

      Also there are some DHCPs like Windows Server 2008 and older, that are UNABLE to handle UEFI and Legacy boot files at the same time, hence you need to manually change the value of your bootfile to either

      undionly.kpxe for Legacy
      OR
      ipxe.efi for UEFI


      You may want to share that Wiki link with them, as this is not a software developed by Quest, and UNIX based open-source.

      There are guides for others DHCPs on Quest's site, but not for Sonicwall.

      InfoBlox DHCP:
      https://support.quest.com/kace-systems-deployment-appliance/kb/155657/how-to-setup-infoblox-pxe-to-work-with-the-kace-systems-deployment-appliance

      BlueCat DHCP:
      https://support.quest.com/kace-systems-deployment-appliance/kb/234459/bluecat-dhcp-configuration-for-bios-and-uefi-pxe

      Cisco Solaris and Other Linux based:
      https://support.quest.com/kace-systems-deployment-appliance/kb/112037/setting-up-non-microsoft-dhcp-server-cisco-solaris-and-others-

      PFSense DHCP:
      https://support.quest.com/kace-systems-deployment-appliance/kb/218032/pfsense-dhcpd-configuration-for-uefi-and-bios-pxe-boot


      So SONIC Wall guys need to determine if that DHCP is capable of handling Legacy or UEFI at the same time, if not, they just change the bootfile name value to one of TWO values above, and try again. - Channeler 5 years ago
This post is locked

Don't be a Stranger!

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

Sign up! or login

Share

 
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