I can confirm that absolutely nothing needs to be done to the configuration of the DHCP server to get PXE boot to work with Acronis PXE Server. The only case where configuration of the DHCP server actually needs to be extended with some additional options is when Acronis PXE Server and DHCP are on the same system which is obviously not the case here because it's a Linux-based DHCP server and components of Acronis Snap Deploy 3.0 can't be installed on Linux. Adjusting the settings of the DHCP server to get PXE boot to work across subnets is a common mistake. Once again, that is not required unless both Acronis PXE Server and DHCP are on the same system. See Section 3.7.3 "Setting up PXE and DHCP on the same server" of the Acronis Snap Deploy 3.0 User's Guide for details. The reason for both "PXE-E53 No Boot filename Received" and "PXE-E55 ProxyDHCP service did not reply to request on port 4011" errors is explained in Microsoft KB article #259670. *NOTE: Even though you are using a Linux-based DHCP server the above article still applies as in most cases extended DHCP options simply can't be used to re-direct PXE traffic across subnets. To resolve the problem, please completely remove all PXE-related options (60, 66, 67, etc.) from the configuration of your DHCP server and instead configure the IP helper table on the router/switch placed between the subnets to re-direct PXE clients to the proper PXE proxy as suggested in Section 3.7.4 "Setting up the PXE to work in other subnet" of the Acronis Snap Deploy 3.0 User's Guide and Microsoft KB article #257579. Please also note that generally (i.e. with pretty much any PXE server) the only two ways to get PXE boot to work across subnets are to either install a separate instance of the PXE server in each subnet which by the way you can do with Acronis PXE Server because it's not licensed and you can have as many PXE servers as needed or do as suggested in previous paragraph and configure the IP helper table on the router/switch placed between the subnets to relay the PXE traffic in a proper way. There are usually no other options. If the above doesn't help and PXE boot still doesn't work, please also try the following things:
If none of that helps either, please provide us with the following additional information so we can help you troubleshoot the issue further. 1. Provide us with the exact text of the error message that is displayed on the screen of the PXE client upon unsuccessful attempt to boot from PXE. 2. Let us know if PXE boot works when both Acronis PXE Server and PXE client are on the same subnet. 3. Try PXE boot with several different types of PXE clients. Let us know if the problem seems to be specific to a particular type of computer or network card. What are the makes/models of the computers/NICs you are experiencing the problem with? 4. Collect the following information from the computer where Acronis PXE Server is installed, put all that in a single ZIP or RAR archive, then send to us.
