NBP filesize is 0 Bytes; PXE-E18: Server response timeout
-
@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? -
@frazzor123 So your test tftp computer is on a different subnet as your FOG server?
If your test computer was on a different subnet then do you have another computer on the same subnet as the FOG server? I’m suspecting there is some type of screening firewall between the two subnets. If we can test tftp from a device on the same subnet as the FOG server that will tell us where the problem isn’t
If the above test fails then you should install the tftp client on your FOG server (understand we keep moving towards the source with these tests). Then issue the following command from your fog server
tftp -4 192.168.140.176 -c get ipxe.efiIf that fails then the problem is surely in the FOG server host OS.Edit: BTW the output from the netstat commands means that the tftp service is listening on the proper port and its up.
-
@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.
-
@frazzor123 said in NBP filesize is 0 Bytes; PXE-E18: Server response timeout:
Do you have any thoughts on that? I implemented a rule that allows all traffic through all ports between the two networks.
Well since they are on different subnets, can the workstations on the remote subnet ping the FOG server or connect to the web ui? (realize I know nothing about how your network is designed)
If yes then network routing is setup correctly. If no then you need to look into how the fog server’s networking is setup. Is a default route defined? I’m assuming yes since you were able to install fog, because the fog installer needs to reach the internet to download the binary package for fog.
-
@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. -
@frazzor123 So just to be clear the firewall you speak of should be between the vlans on your campus. So you will need your infrastructure team to look at it.
FOG uses a number of ports/protocols that need to be open in firewalls to make imaging work.
tftp
ftp
http
nfs -
@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! -
This just started happening for me too, completely randomly. Any idea what would cause it? I didn’t change anything on the server or domain controller. Any help would be greatly appreciated!
Thanks!
-
This post is deleted! -
@foggymind Please open a new thread because your conditions are probably different than the OP of this thread. In his case it was a setting on their firewall that was causing this issue.
BUT confirm that you only have 1 dhcp server on your network. I’ve seen rouge dhcp servers cause random pxe boot errors.
-
@george1421 Thanks so much for your quick reply! I do have 3 DHCP servers that sync with each other but all the settings seem to be correct. I will start a new topic.
