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!
[RESOLVED] WADS - Server IP address changed during deployment
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2342
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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
-
dcardon
- WAPT Expert
- Messages: 1978
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
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
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
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
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!
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!
-
dcardon
- WAPT Expert
- Messages: 1978
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Mathieu,
thanks for the feedback.
By the way, sfonteneau -> Simon Fonteneau.
He's currently on vacation, he shouldn't be offended. 
Denis
thanks for the feedback.
By the way, sfonteneau -> Simon Fonteneau.
He's currently on vacation, he shouldn't be offended. Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
