Hello,
My apologies, I misspoke.
When I removed the double slash as instructed, the computer tried to retrieve a configuration from Boot\x86\wdsnbp.com (which is no longer used). This was where things improved, in a way, as it went beyond simply obtaining an IP address.
By deleting line #67 Boot\x86\wdsnbp.com and then running another test, the computer retrieves an IP address but then returns to the BIOS startup screen where it asks to choose the boot mode (PXE, USB, etc.).
Here is my DHCP configuration:
[SOLVED] DHCP configuration for ISO 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
-
admgautier
- Messages: 45
- Registration: Sep 24, 2018 - 4:48 p.m.
- Attachments
-
- DHCP configuration option.png (16.3 KB) Viewed 5592 times
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
No time to see a message at that moment?admgautier wrote: ↑Sep 12, 2022 - 09:07 By deleting line #67 Boot\x86\wdsnbp.com and then doing a new test, the machine retrieves an IP address but then returns to the BIOS startup where it asks to choose the boot mode (PXE, USB etc)
-
admgautier
- Messages: 45
- Registration: Sep 24, 2018 - 4:48 p.m.
Not at all, it goes straight back to startup mode.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Does anything appear in the server's access.log file?
Code: Select all
cat /var/log/nginx/access.log |grep -i pxe-
admgautier
- Messages: 45
- Registration: Sep 24, 2018 - 4:48 p.m.
Nothing either...
- Attachments
-
- log access.png (2.42 KiB) Viewed 5576 times
-
admgautier
- Messages: 45
- Registration: Sep 24, 2018 - 4:48 p.m.
Regarding your tutorial on the webinar, when I boot via PXE, I don't see this:
- Attachments
-
- 2022-09-09 14_52_03-(4) WAPT 2.2 Webinar - Discover OS deployment via WAPT! - YouTube – Br.png (78.9 KB) Viewed 5576 times
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Do you see something like the word "ipxe" appear?
The logs indicate that ipxe isn't contacting the URL specified in the DHCP configuration, since there's nothing in the logs containing the word "dhcp" (note: have you tried again today? The logs are normally regenerated daily).
That's why the menu isn't appearing.
In order:
- The machine (the BIOS) sends a DHCP request; DHCP tells it to start ipxe.edi or undionly.kpxe depending on the architecture
. - At that point, you should see the word "ipxe" somewhere in the system's startup sequence.
- Then, IPXE makes another DHCP request. DHCP detects that it's not the BIOS making the DHCP request but IPXE and provides a URL (the API/v3 URL, etc.).
There's nothing in the server logs, so either IPXE doesn't start or it can't reach the URL provided by DHCP.
The logs indicate that ipxe isn't contacting the URL specified in the DHCP configuration, since there's nothing in the logs containing the word "dhcp" (note: have you tried again today? The logs are normally regenerated daily).
That's why the menu isn't appearing.
In order:
- The machine (the BIOS) sends a DHCP request; DHCP tells it to start ipxe.edi or undionly.kpxe depending on the architecture
. - At that point, you should see the word "ipxe" somewhere in the system's startup sequence.
- Then, IPXE makes another DHCP request. DHCP detects that it's not the BIOS making the DHCP request but IPXE and provides a URL (the API/v3 URL, etc.).
There's nothing in the server logs, so either IPXE doesn't start or it can't reach the URL provided by DHCP.
-
admgautier
- Messages: 45
- Registration: Sep 24, 2018 - 4:48 p.m.
When I look closely, I can't see what's happening on the machine. It correctly detects the DHCP server, which provides it with an address (see attached image), but then it reboots.
However, looking at the logs, it seems there's an error somewhere regarding the WAPT version (see log).
What's strange is that on the server where the WAPT console is installed, there's one WAPT console located in the "WAPT Server" folder, which is version 2.1.2, and another console in the "Wapt Setup" folder, which is version 2.2.1.
The error might be coming from there. However, I can't update the console from WAPT Server; each time, it tells me to reinstall the update.
I was using a version 2.2.1 console until now.
However, looking at the logs, it seems there's an error somewhere regarding the WAPT version (see log).
What's strange is that on the server where the WAPT console is installed, there's one WAPT console located in the "WAPT Server" folder, which is version 2.1.2, and another console in the "Wapt Setup" folder, which is version 2.2.1.
The error might be coming from there. However, I can't update the console from WAPT Server; each time, it tells me to reinstall the update.
I was using a version 2.2.1 console until now.
- Attachments
-
- Console wapt.png (19.28 KB) Viewed 5554 times
-
- log wapt.png (87.06 KB) Viewed 5554 times
-
- boot pxe.png (55.2 KiB) Viewed 5554 times
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
I'm confused; are you running a WAPT server on Windows or Linux?
Your screenshot shows a WAPT server running on Windows in the Start menu, but according to the logs, it's running on Linux.
Your screenshot shows a WAPT server running on Windows in the Start menu, but according to the logs, it's running on Linux.
-
admgautier
- Messages: 45
- Registration: Sep 24, 2018 - 4:48 p.m.
The WAPT server runs on Linux, but the administration console is located on a Windows server...
Your solution was configured before my arrival.
Your solution was configured before my arrival.
