@george1421
Yes, I just figured it out. It had something to do with a little Tool called “TFTP Helper” I needed it to activate in the firewall.
Now everything is going great.
Thanks a lot for your help!

@george1421
Yes, I just figured it out. It had something to do with a little Tool called “TFTP Helper” I needed it to activate in the firewall.
Now everything is going great.
Thanks a lot for your help!

@george1421
Yes, I can ping the FOG server and even open its web ui. The server has also access to the internet.
I’m pretty convinced that it is a firewall issue and I will head out to search for the problem on that side.
Thanks a lot for the help and I will come back with the solution as soon as I got it. Maybe someone else experiences the problems.

@george1421
If I put the two computers on the same subnet it does work and I can get the ipxe.efi file with windows…
I guess that is progress and we can be pretty sure that it is a firewall issue.

Do you have any thoughts on that? I implemented a rule that allows all traffic through all ports between the two networks.

@george1421
Yes, they are are on different subnets. That worked earlier.

The netstat output is:

udp      0    0 0.0.0.0:69             0.0.0.0*
udp6     0    0 :::69                  :::*

The linux firewall (ufw) is disabled and inactive.

I one more time turned off the windows firewall and tried to get the ipxe.efi over tftp in windows command line. There was a request timeout.
Do have anything else I could check?

@george1421 Sorry about that!! Should be public now

@george1421
I already did the tcpdump some hours ago, but i did a new one right now. You’ll find it here: https://drive.google.com/open?id=1BGH3VrgHNrPYtt9DzUF2BUEI3YL59mkf
192.168.110.100 is the client (before ip address was assigned through our dhcp)

While triple checking everything I found that the TFTP PXE KERNEL DIR has been set to /var/www/fog//service/ipxe/
I changed it and deleted the second “/”, but it didn’t change anything. Since this is a fairly fresh installation and I’m pretty sure I didn’t change the directory, I’m thinking if it maybe was on purpose, but I don’t see a reason why.

Hey George,

thanks for your fast reply.
No, the VLANs are not on the same subnet, but - for testing purposes - no traffic is blocked between the VLANs and all ports are open.
When it was working clients and server hasn’t been on the same subnet either (it was just a different one).
Do you have anything in mind what could have been misconfigured on the tftp service on the server?

Hi Guys,

first of all, let me tell you that you already helped so much! Great forum and awesome community.
Unfortunately, I have an issue I didn’t find a solution in the forum or wiki.

I’ve set up a fog server yesterday. Actually it was a bit of a pain cause of my nvme drives on host and server, UEFI, firewall/gateway, etc. but finally, I figured everything out with your help and all of the previous topics in this forum and got it up and running. Next step was to relocate the server back to the VLAN it belongs and everything stopped working. (Actually it was in a different VLAN than the clients all the time, but it was the wrong one. I know… Stupid mistake…).

My configuration:
FOG Server - 1.5.7
Ubuntu 18.04 LTS
Sophos Firewall between the VLANs (also my DHCP)
40ish clients, all with the same specs (AMI Motherboard, Intel i7, nvme, etc.)

I’m getting the error message:
NBP filename is ipxe.efi
NBP filesize is 0 bytes
PXE-E18: Server response timeout.

I had the same issue yesterday because I forgot to set up the “next-server” in my DHCP settings (I just had 66 and 67).

What I tried to fix it:

• Check DHCP settings - 66, 67 and next-server all seem to fit
• restarted TFTP service
• logged in via FileZilla (everything is up and running and the filesize of the ipxe.efi is something around 8MB if I recall correctly)
• tried to get ipxe.efi via TFTP in windows CLI (didn’t work though)
• checked the FTP credentials everywhere
• I didn’t change anything on the client-side from the working state, so I didn’t touch their configuration since the error
• I did a tcpdump and checked it in Wireshark - the client sends the request but the server doesn’t answer
• reinstalled the FOG server (just in case)

The clients I checked with worked perfectly fine (after changing half of the BIOS setting, including AHCI or turning off secure boot, and changing the host’s disk to /dev/nvme0n1), and it only worked with the ipxe.efi so far. But I tried the undionly.kpxe first.
I hope, that I didn’t forget any of my tries to fix it.

But right now I have no more idea what to do.

Does anybody have a clue on that one? Is there any more data I can provide?

Thanks a lot in advance,

Mo