May 21, 2026

PXE Remote Maintenance: Complete Network Boot Guide Announcements Buyer Guide Comprehensive Tips Occasion Product Review Q&A Tutorials Remote maintenance is essential for IT teams, especially when managing multiple devices across locations. However, many professionals face critical challenges when dealing with unbootable systems or bare-metal machines. PXE remote maintenance solves this problem effectively.It allows you to boot and maintain computers entirely over the network, without relying on local storage like hard drives or USBs. What Is PXE? PXE stands for Preboot Execution Environment. It is a network boot standard developed by Intel. Simply put, PXE lets your computer start directly from its network card, before loading the local operating system.This is the core advantage of PXE remote maintenance. Even if a computer’s hard drive is completely failed or corrupted, you can still boot into a maintenance system over the network. Core Components of PXE PXE relies on three essential services working together: DHCP Server: Assigns IP addresses to clients and tells them where to find the boot server TFTP Server: A lightweight file transfer protocol for sending small boot files Boot Files: Special files that load the maintenance system kernel and environment Common Problems & Deep Troubleshooting Guide While PXE is powerful, it has specific requirements that often cause failures. Below are the most common issues with technical solutions and measurable troubleshooting steps. 1. Critical DHCP Configuration Errors This is the #1 cause of PXE boot failures. PXE requires specific DHCP options that most default DHCP servers do not enable.Critical Note: If your network uses VLANs or multiple subnets, PXE broadcasts will not cross routers by default. You must configure DHCP Relay (IP Helper) on your layer 3 switches to forward PXE requests to your PXE server. 2. Network Connectivity Issues PXE is extremely sensitive to network latency and packet loss. For reliable operation: Ensure client and server are on the same subnet (or DHCP Relay is properly configured) Use Gigabit Ethernet (10/100Mbps works, but is much slower) Test network connectivity with ping -t 192.168.1.100 from another machine Check for duplicate IP addresses on the network 3. Legacy vs UEFI Boot File Mismatch This is a very common mistake. Modern computers use UEFI instead of the old Legacy BIOS, and they require completely different boot files. Using the wrong file will cause PXE boot to fail silently. 4. Firewall Blocking TFTP Traffic TFTP uses UDP port 69. Most operating system firewalls block this port by default. You must explicitly allow TFTP traffic on your PXE server. How to Check If Your Computer Supports PXE Before setting up PXE, confirm that your target computers support network boot. Here are the accurate methods for Windows and Linux systems. Check via BIOS/UEFI This is the only 100% accurate method: Restart your computer Press the boot menu key during startup (usually F2, F10, F12, or Del) Look for options labeled: Network Boot PXE Boot LAN Boot IPv4 PXE / IPv6 PXE If you see any of these options, your computer supports PXE. If not, it does not have native PXE support. Check via Device Manager (Windows) Right-click the Start menu and select Device Manager Expand the Network adapters section Right-click your Ethernet adapter and select Properties Go to the Advanced tab Look for properties related to: Wake-on-LAN Network Boot PXE Support If these options exist, your network card supports PXE. Check via Terminal (Linux) Open a terminal window First, identify your network interface name:baship link show Then use ethtool to check for PXE support (replace eth0 with your interface name):bashsudo ethtool eth0 Look for the “Wake-on” line. If it shows g (Wake on MagicPacket) Or mentions PXE, your card supports network boot. Step-by-Step PXE Remote Maintenance Setup This guide uses the most popular and easiest tools for PXE server setup. We recommend Tiny PXE Server for Windows or dnsmasq for Linux, as they combine DHCP and TFTP in a single package. Step 1: Prepare the Server Environment Prerequisite: Your PXE server must have a static IP address. Dynamic IP addresses will break PXE functionality. Assign a static IP to your server (e.g., 192.168.1.100) Disable any other DHCP servers on the same network (conflicts will cause failures) Download and install your chosen PXE server software Configure the DHCP server with the critical options from the table above Step 2: Place Correct Boot Files & Maintenance Images Critical: Choose the correct boot file based on your client’s boot mode. Client Boot Mode Required Boot File Legacy BIOS (old computers) pxelinux.0 Modern UEFI (64-bit) bootx64.efi or ipxe.efi UEFI (32-bit, rare) bootia32.efi Place the appropriate boot file in the root directory of your TFTP server Download a maintenance system image (WinPE for Windows, Clonezilla for disk cloning, or a Linux rescue image) Extract the entire contents of the ISO image to a subdirectory in your TFTP root Update your PXE configuration file to point to the correct kernel and initrd files Step 3: Configure Client BIOS/UEFI Boot Priority Restart the target computer you want to maintain Press the BIOS/UEFI key during startup (F2, F10, F12, or Del) Navigate to Advanced > Network Stack Set PXE Boot or Network Boot to Enabled Go to the Boot menu Set Network Boot (LAN) as the First Boot Priority Save changes and exit BIOS/UEFI Step 4: Boot Into Maintenance System & Perform Operations The client computer will now automatically start the PXE boot process It will send a DHCP broadcast request Your PXE server will respond with an IP address, TFTP server address, and boot file name The client will download the boot file from the TFTP server The boot file will load the maintenance system kernel and environment Once booted, you can perform any maintenance tasks: Reinstall the operating system Clone or backup hard drives Repair corrupted system files Scan for viruses and malware Reset forgotten passwords What If Your Computer Doesn’t Support PXE? Many consumer laptops and some modern ultrabooks have PXE disabled by default or removed entirely. Here are the solutions: USB PXE Boot: Create a special USB drive