Target device shows an error message 'PXE-E32: TFTP open timeout' when PXE booting.

The target device successfully receives an IP address however can't connect to the TFTP server.

The "PXE-E32" error indicates that the PXE did not get a reply from the TFTP server when sending a request to download its boot file. 

Possible causes for this problem are:

• There is no TFTP server configured for the IP range on which the target device is PXE booting
• Incorrect/ Invalid settings in the Network boot listener sub node Configuration >> Properties >> Network Boot Listener section
• The BCM agent service on the configured network boot listener for the respective subnet/ VLAN / site is not running
• Option 66 and 67 in the DHCP server configuration are not configured properly (e.g the option 66 is set to the OSD manager ip instead of being set the local network boot listener ip)

The value entered in option 66 must be the OSD network boot listener IP address for the scope and the value entered in option 67 must be the boot file name for BIOS x86 / BIOS x64 / UEFI respectively. More information on these settings in the following Knowledge Article (KA): Client Management: Os Deployment - Options 66 or 67, to use them or not to deploy or capture OS images


A- Different scenarios:

Scenario 1:
The Internal DHCP Gateway is enabled in the network boot listener configuration, and options 66, 67 are configured in the DHCP server configuration
Only one or the other must be enabled, not both. The preferred method is the DHCP Gateway, but it requires the target to be in the same subnet tha, the network boot listener.

Scenario 2:
The Internal DHCP Gateway is disabled in the network boot listener configuration, and options 66, 67 are configured in the DHCP server configuration
In this scenario, verify if the option 66 and option 67 are configured correctly:
- verify that the hostname or ip address that is set in option 66 is the one of the local network boot listener - A common mistake is to set the option to the OSD manager ip/hostname instead of setting it to the network boot listener that will be used for this target.
- if f using the hostname and not the IP address then make sure that the name can be resolved from the targets

Scenario 3:
Another network boot listener or another application acts as a tftp server on this subnet. To identify this review the information on the screenshot. This is a very common issue.


B- Download the file:
- install the feature tftp client of windows from Windows programs and features one of the targets, or at least on a device that is on the same subnet
- open cmd
- run the following commands to the network boot listener from there:
If the download succeeds then it should be working for any device booting on this subnet. If not, it is most likely a good time to capture network packets during a BCM OS Deployment/Capture, and then send it to support.