@Sebastian-Roth, yes I change my server. I installed in another distro (Fedora 30) and set IP 172.24.3.71, because I’m tired to deal with Ubuntu is FOG Enemy.

Let me give a feedback to this issue, as I faced it recently. In my case, the culprit was faulting parameters in Microsoft DHCP.

It was faulting “MSFT Quarantine” User Class and PXE Vendor Class is not properly configured (It was typed “PXEclient:Arch:00007” instead of “PXEClient:Arch:00007”).

After doing this corrections, PXE got successfully redirected Boot instructions to FOG Server.

@george1421 I make another test with another client 172.24.12.65 running on same subnet to 172.24.12.35 - talking to the same server and got successfull - 12.65 - 3.70.pcap

@george1421 No, 172.24.5.180 is not the FOG Server, it’s 172.24.3.70… I don’t even know where PXE come with this idea…

@george1421 Look at this pcap file about the other FOG server (172.24.3.71) - It’s working. That’s a 1.5.9 FOG running in Fedora 32 - I think it’s a client issue, because another client could caugth naturally PXE TFTP… I will exam differences between the two clients.

@george1421 Here: 12.35.pcap

@george1421 I understand. There is another FOG server on the same subnet (172.24.3.71) that is normally working. I changed by this new one. Here are pcap file you asked before 12.35.pcap

@george1421 the server is in default subnet (172.24.0.0/22) and the workstation 172.24.12.35 is in WLAN 12 (172.24.12.0/23).

Hi,

I cannot understand why a computer is not getting PXE boot, even when I configured everything correctly (I think so). I raised FOG 1.5.10 in Fedora 38 server, but when I try to boot a machine, I see the classical error: “Pxe-E32: TFTP open timeout”.

I use a Windows Server 2019 DHCP and everything is fine, as this imagem suggest:

Why it gathers 172.24.5.180 and not 172.24.3.70?

@sebastian-roth I successfully installed 1.5.9 in Ubuntu 18.04! It installed php7.2 on it. Thanks!.. It’s interesting to update installation wiki, because there is written 16.04 as high Ubuntu release that support FOG.

@sebastian-roth I’m not interested in keep Ubuntu 16.04 in these machines. I’ll try in 18.04, for example, but I tried installing a fresh in Ubuntu 22.04, and the error was exactly the same!! But I think this release is too new for this test, ok? I’ll be back with the results about upgrading my server to 18.04