2729: Acronis PXE Server Conflicts with Broadcom ASF IP Monitor Service

use Google Translate

Last update: 22-09-2009

Client machines cannot boot Acronis PXE Server if it is running on the same machine with Broadcom ASF IP Monitor (AsfIpMon.exe)

Symptoms

  1. You have Acronis PXE Server running on the same machine with Broadcom ASF IP Monitor;

  2. Client machines fail to boot from Acronis PXE Server with an error message similar to the following one:

    PXE-E32: TFTP open timeout

  3. The log file of Acronis PXE Server shows entries similar to the following ones:

    StartUnicast: Failed to bind on specified address 0.0.0.0:69

    Error opening unicast session 0.0.0.0:69

    Error adding locally accessed file C:\Documents and Settings\All Users\Application Data\Acronis\PXEServer\Bootmenu\14581394 as 14581394 to session 10.10.17.1:69

Cause

The Broadcom ASF IP Monitor service uses the same port (Port 69) as Acronis PXE Server.

Solution

  1. End the AsfIpMon.exe process in Windows Task Manager;

  2. Disable the Broadcom ASF IP Monitor service:

    • Hit Win-R and type services.msc;

    • In the Services window right-click on the Broadcom ASF IP Monitor line;

    • Select Properties;

    • Set the Startup type to Disabled and click OK.

More information

Acronis PXE Server uses Port 69 by default and there is no option to change it.

See also Investigating Issues with Acronis PXE Server.

Tags: