Salta al contenuto principale

PXE boot issues - tftp open timeout

Thread needs solution

Hi, I'm having issues with booting from Acronis PXE server.
Our DHCP server is on our domain controller VM, separate from the Acronis Snap Deploy 4/PXE server. DHCP option 66 value is set to FQDN of the Acronis server (tried IP as well), and option 67 is the file name of the .wim file (no path).

When I boot from network, I get an IP address, but TFTP times out with the following error:
PXE-E32: TFTP open timeout
PXE-M0F: Exiting Intel Boot Agent.

I also tried removing DHCP options 66 and 67 and then I'm not even getting an IP address.

Please advise.

0 Users found this helpful

Hello Sushi Cat,

Thank you for posting your question.

I have searched for your error and found this article in our Knowledge Base. To resolve the issue, please disable the Broadcom ASF IP Monitor service.

If you need immediate assistance, please contact Acronis support. More information can be found in our Customer Handbook.

Please let me know if you have additional questions.

Thank you.

Hello Peter,

Thank you for your reply. I also stumbled on that article when searching for a resolution to this issue. However, it doesn't help me since I don't have any Broadcom hardware or services running on my Acronis server.

Hello Sushi Cat,

Thank you for your reply.

Please contact Acronis Support then in order to investigate this issue.

If there is anything else, we can do for you, please let me know.

Thank you.

I have exactly the same problem. The article does not apply to me either. I do not have any Broadcom services running on my machine.

I recently encountered this error. I had both SnapDeploy and Acronis Backup installed. I realized that SnapDeploy offered everything I needed, so I began removing the various Acronis Backup components. Afterwards I started getting the TFTP timeout errors when attempting to connect via PXE. I must have removed something that SnapDeploy needed, because when I ran the setup executable and chose "repair" everything seemed to go back to normal and I was able to connect again. I'd give that a try (repairing via the setup .exe)