Tranquil IT Forum

Hello,

We are currently setting up a WADS deployment via TFTP.

Our WAPT server currently has two network interfaces to separate the uses:

* one interface dedicated to post-installation clients (IP: 192.168.0.1);
* a second interface dedicated to WADS/PXE deployments (IP: 192.168.100.1).

PXE booting works correctly: the client machine successfully obtains its IP address and downloads the boot file `bootmgfw.efi` via the 192.168.100.1 interface.

However, during the installation process in the WinPE environment (connectivity check step with ping tests to 127.0.0.1 and the WAPT server), the workstation attempts to connect to the WAPT server via the address 192.168.0.1 instead of the dedicated deployment address (192.168.100.1), causing the deployment to fail.

We would like to know if it is possible to configure WADS to force the use of the IP address 192.168.100.1 throughout the entire deployment phase (WinPE), or if there is a setting to define the WADS interface/IP address to use when the WAPT server has multiple network interfaces? Unfortunately, I haven't found anything in the documentation and haven't been able to find anything in the server's configuration files.

Thank you in advance for your help!

tdbrm wrote: ↑Jul 9, 2026 - 2:20 PM * a dedicated interface for post-installation clients (IP: 192.168.0.1);
* a second interface dedicated to WADS/PXE deployments (IP: 192.168.100.1).

This method isn't very practical and isn't recommended because it will cause a lot of problems. When the machine changes VLANs, everything will shift, and even using DNS view isn't ideal due to caching.

Why not just make it so that 192.168.0.1 -> 192.168.100.1 is allowed.

Just a routing/firewall rule.

No need for two interfaces on the Wapt server

Hello Mathieu,

I imagine you only want TFTP to be listened to on the 192.168.100.0/24 subnet, and the corresponding DHCP configuration only on that network.

If so, you can put a machine with the wapttftpserver on another machine on the 192.168.100.0/24 network as a secondary repository on that network. And remove the 192.168.100.x address from the wapt server.

Regards,

Denis

Hello Denis and Stéphane,

thank you for your replies; indeed, opening up the data flow was the easy solution, but several of us were discussing this and we wanted an outside perspective!
I hadn't thought of the second solution right away, but it was indeed a good idea. In any case, we ultimately opted for opening up the data flow to avoid creating a bureaucratic nightmare.

Thanks again!

Hi Mathieu,

thanks for the feedback.

By the way, sfonteneau -> Simon Fonteneau. He's currently on vacation, he shouldn't be offended.

Denis