> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/2pxe-server/4.0/troubleshooting/multi-nic-and-trunk-configurations.md). # Multi-NIC and trunk configurations Guidance for configuring 2PXE when the server has multiple network interfaces or participates in networks with multiple VLANs. A 2PXE server with multiple network interfaces, multiple IP addresses, or access to several VLANs may need additional configuration. The important point is to make sure that DHCP and TFTP traffic use the intended local IP address. 2PXE uses separate settings for the DHCP and TFTP traffic: * **Bind to IP** controls the local IP address used by the DHCP threads. This determines which local address 2PXE uses when creating the DHCP sockets and sending broadcast or multicast replies. * **ListenToTftpIp** controls the IP address used by the TFTP server. On a multi-NIC server, TFTP replies can sometimes leave through the wrong interface or use an unexpected source address. Set this option to the address that should be used for TFTP responses. In most deployments, both settings should use the same IP address. They can be different when the network design intentionally uses different interfaces for DHCP and TFTP traffic. ## Common network layouts ### Server with multiple network interfaces A server may have one interface connected to a client or PXE network and another connected to a management or server network. In this case, identify the IP address that should handle PXE traffic and use it for **Bind to IP**. If TFTP replies use the wrong source address, set **ListenToTftpIp** to the intended TFTP address as well. ### Server connected to multiple VLANs A server may be connected to a trunk or have separate interfaces for different VLANs. Make sure the required VLAN interfaces and IP addresses are configured in Windows and that the network infrastructure forwards PXE traffic to the correct 2PXE address. The 2PXE settings select local IP addresses for its DHCP and TFTP services. They do not create VLAN interfaces, configure switch trunking, or replace DHCP relay/IP Helper configuration on routers and Layer 3 switches. ### Multiple IP addresses on one interface If an interface has more than one IP address, confirm which address clients should use to reach 2PXE. Configure **Bind to IP** and, if required, **ListenToTftpIp** with the intended address rather than relying on an unintended default. ## Configure the 2PXE network bindings 1. Identify the Windows network interface and IP address that should handle PXE traffic. 2. Open the **Configure 2PXE** configuration editor. 3. Set **Bind to IP** in **General settings** to the intended local IP address. 4. Turn on **Show advanced** and set **ListenToTftpIp** if TFTP responses need to use a specific address. 5. Click **Verify**, then **Save**. 6. Restart the **2Pint 2PXE Server** service when prompted. For more information about the settings, see [Configuring 2PXE Server](/2pxe-server/4.0/configuration/2pxe-config-file.md). ## Troubleshooting If clients receive a PXE response but fail while downloading the boot program or other files, check the traffic separately: * Confirm that the DHCP/PXE response is sent from the intended 2PXE address. * Confirm that TFTP replies use the expected source IP address and interface. * Check that Windows has the expected IP addresses and routes configured on each interface. * Verify that the router, switch, DHCP relay, and firewall configuration allows the required traffic between the client subnet and the selected 2PXE interface. * If the server has multiple active interfaces, capture network traffic during a test boot to identify which local address is actually used for each response. The **Bind to IP** and **ListenToTftpIp** settings are configured in the **Configure 2PXE** editor. **ListenToTftpIp** is only shown when **Show advanced** is enabled. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.2pintsoftware.com/2pxe-server/4.0/troubleshooting/multi-nic-and-trunk-configurations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.