Configure Tftpd64 to act as a DHCP server on Windows 10 by enabling the service in the advanced settings and defining a specific IP pool. This setup assigns addresses to clients, allowing them to communicate with your host machine. While this provides local network connectivity, you must also configure Internet Connection Sharing (ICS) or manual routing rules to grant these clients actual internet access.
Prerequisites and Network Configuration
Before launching Tftpd64, ensure your Windows 10 machine has a stable network interface connected to the internet. You will likely be using an Ethernet adapter or a Wi-Fi connection that acts as the upstream gateway. It is critical to identify which network adapter is providing the internet connection, as Tftpd64 needs to bind to an interface that can route traffic to external networks if you want clients to browse the web.
If you are connecting devices directly via Ethernet, ensure your physical switch or cable allows communication between the host and the client. For wireless setups, verify that your Wi-Fi adapter supports ad-hoc modes or hosted networks if you intend to broadcast the DHCP service over Wi-Fi, though Ethernet is generally more reliable for this specific use case. The goal is to create a isolated subnet where Tftpd64 controls the address assignment while your Windows firewall manages the traffic flow.
Enabling the DHCP Server in Tftpd64
Tftpd64 is primarily known as a TFTP server, but it includes robust DHCP capabilities. To activate this feature, open the application and navigate to the Advanced Settings tab. Here, you will find a checkbox labeled DHCP Server. Check this box to enable the service. Once enabled, the interface will expand to reveal configuration options for the DHCP scope.
You must define the range of IP addresses that Tftpd64 can hand out. In the Start Address field, enter the first IP in your desired pool, such as 192.168.0.100. In the End Address field, specify the last IP, for example, 192.168.0.200. This creates a contiguous block of twenty-one addresses available for client devices. Ensure this range does not conflict with any static IPs you might have assigned manually to other devices on the same network segment.
Additionally, configure the Subnet Mask, typically 255.255.255.0 for home or small office networks. Set the Default Gateway to the IP address of your Windows 10 machine on the local network interface. This is crucial because clients need to know how to reach the router that connects to the internet. If you leave this blank, clients will only be able to communicate with devices on the same local subnet.
Configuring DNS and Router Options
To allow clients to resolve domain names, you must provide DNS server information via DHCP. In the Tftpd64 Advanced Settings, locate the DNS Server field. You can enter public DNS servers like Google’s 8.8.8.8 or Cloudflare’s 1.1.1.1. Alternatively, you can point clients to your Windows machine’s IP if you are running a local DNS resolver. This step ensures that when a client pings google.com, the request is properly forwarded and resolved.
For more advanced control, you can set the Router Option (Option 3) to explicitly define the gateway. This overrides the default gateway setting in some configurations and ensures consistency. If you need to add specific options like NTP servers, refer to our guide on Adding NTP Server DHCP Option for Windows Clients to extend the functionality of your DHCP lease. Properly configured DNS and Gateway options are the difference between a device having an IP address and actually being able to use the internet.
Enabling Internet Access via Windows Features
Assigning an IP address is only half the battle. For clients to access the internet, your Windows 10 machine must forward their traffic to the upstream network. The easiest way to achieve this is through Internet Connection Sharing (ICS). Go to Control Panel > Network and Internet > Network Connections. Right-click the adapter that has internet access (e.g., Wi-Fi) and select Properties.
Navigate to the Sharing tab and check the box that says Allow other network users to connect through this computer’s Internet connection. Select the local network adapter that Tftpd64 is bound to from the dropdown menu. Windows will automatically reconfigure the IP address of the selected adapter to 192.168.137.1 if it isn’t already in that range. Note that this may override your custom Tftpd64 subnet if not aligned; ensure your Tftpd64 DHCP pool matches the ICS subnet or adjust ICS settings accordingly.
If ICS causes conflicts, you can alternatively configure static routes or use third-party routing software. However, ICS is built into Windows and requires no additional installation. Be aware that enabling ICS may trigger Windows Firewall alerts. You might need to adjust firewall rules to permit DHCP traffic (UDP ports 67 and 68) and forwarded traffic. For detailed steps on managing these permissions, see Configuring Specific IP Addresses with DHCP Offer on Windows Firewall.
Troubleshooting Common Issues
If clients fail to receive an IP address, verify that the Tftpd64 service is running and bound to the correct interface. Check the Windows Firewall to ensure it is not blocking inbound UDP port 67. Sometimes, multiple network adapters can cause confusion; disable unused adapters temporarily to isolate the problem.
If clients get an IP but cannot ping the gateway, check the Default Gateway setting in Tftpd64. It must match the IP of the Windows adapter that the clients are physically connected to. If the gateway is incorrect, clients will send packets to a non-existent device. Also, ensure that the Lease Time is set appropriately; too short a lease can cause frequent renewals, while too long a lease might exhaust the pool during testing.
Another common issue is IP conflicts. If another DHCP server exists on the network, such as a home router, it may interfere with Tftpd64. Ensure Tftpd64 is the only active DHCP server on the local segment. You can check for conflicts by reviewing the DHCP log in Tftpd64, which records every offer and acknowledgment. If you encounter inactive reserved IPs causing issues, review Windows Server 2022: Inactive Reserved IP Address Used by Another Device for broader context on reservation management.
Frequently Asked Questions
Can I use Tftpd64 DHCP for production environments?
No, Tftpd64 is designed for testing, troubleshooting, and small temporary networks. It lacks the reliability, security auditing, and high-availability features of enterprise DHCP servers like Windows Server DHCP or ISC DHCP. Use it only for development or diagnostic purposes.
Why do my clients get APIPA addresses instead of DHCP leases?
This usually indicates that the DHCP server is unreachable or blocked. Check your Windows Firewall settings to ensure UDP port 67 is allowed. Also, verify that Tftpd64 is bound to the correct network adapter that the clients are connected to.
How do I reset the DHCP lease table in Tftpd64?
Tftpd64 does not have a direct "clear all leases" button in the UI. You can restart the Tftpd64 application to clear the memory-based lease table. For persistent storage, you can export the current leases to a file and delete the associated data files if they exist in the installation directory.
Does Tftpd64 support IPv6 DHCP?
The standard version of Tftpd64 focuses primarily on IPv4. While some newer builds may offer limited IPv6 support, it is not fully featured compared to dedicated IPv6 DHCP servers. Check the official documentation for your specific build version regarding IPv6 capabilities.
Can I combine Tftpd64 with a local DNS server?
Yes, you can configure Tftpd64 to hand out the IP address of a local DNS server (like BIND or Windows DNS) as the DNS option. This allows clients to resolve internal hostnames. Ensure the DNS server is running and accessible on the same subnet.