Networking Connectivity
Intel® Boot Agent
Using the Intel® Boot Agent in a BOOTP Environment

When configured for PXE, the Intel® Boot Agent can be used via BOOTP without a PXE server present.

To use BOOTP to obtain an IP address only, a BOOTP server must be present. When configured as a DHCP server, Microsoft Windows* 2000 Server and Windows NT* 4.0 Server (with service pack 2 or higher applied) can act as a BOOTP server and will service BOOTP requests. In Windows 2000 Server, you can create a pool of BOOTP addresses to be administered in much the same way that DHCP is administered.

To use BOOTP to both obtain an IP address and download an image, both a BOOTP server and a TFTP server must be present on the network. In Windows 2000 Server or Windows NT 4.0 server, you must configure DHCP to respond to BOOTP requests from a client with the client IP address, the name of the boot file containing the boot image (Boot file name) and the name of the TFTP server holding the boot image (TFTP boot server host name).

Neither Windows 2000 Server nor Windows NT 4.0 Server are supplied with a general purpose TFTP server. To remote boot via BOOTP / TFTP in a Windows environment, you must either have a separate TFTP server on the network or add a third party TFTP service to Windows.

Most Unix variants are supplied with a TFTP daemon. Many TFTP server programs for Windows can be obtained from third party suppliers.

For support and configuration details on Windows support for BOOTP, search Windows help using BOOTP and/or TFTP as keywords.


This applies to:

Intel® Boot Agent

Solution ID: CS-008213
Last Modified: 07-Oct-2013
Date Created: 11-Jan-2004
Back to Top