Tranquil IT Forum

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:

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)

No time to see a message at that moment?

Not at all, it goes straight back to startup mode.

Does anything appear in the server's access.log file?

Nothing either...

Regarding your tutorial on the webinar, when I boot via PXE, I don't see this:

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.

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.

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.

The WAPT server runs on Linux, but the administration console is located on a Windows server...

Your solution was configured before my arrival.