@george1421
Thanks for the quick reply!
From the screen shot it looks strange in that there was a discover, then 3 offers from the dhcp server and then after 4 seconds the client sends the request. What is the target computer playing hard to get? – not sure!
Yes, I followed that tutorial, is there something else I need to do with the filters or just type in the command?
@george1421 I ran tcpdump on the fog server and got the following results.
@foggymind Another note, I seem to be able to rename systems so communication with the fog client seems to be working.
I’m taking another look at this and basically have no idea where to go from here, any help would be greatly appreciated!
@foggymind I did this (below) and captured via wireshark but it doesn’t seem to show anything interesting, just the DHCP server that’s serving the IP address. Is there something in particular I should be looking for?
@foggymind Oh yeah, one more thing I just remembered. I noticed that ALL the hosts show up as a red unknown status in the fog interface. They used to show a green status if they were on. I know that they are on but they still show that status. I’m not sure if that happened at the same time, but it definitely wasn’t like that before. The weird thing is that if I apply a computer name change, the fog client picks it up and applies the change.
@sebastian-roth Yeah that could definitely be it, I haven’t captured the DHCP traffic, is that something I would use wireshark for?
@sebastian-roth Thanks for the input, yeah I realize that you could interpret that as randomly occurring - should have rephrased it! Looks like the fog server isn’t receiving the TFTP requests for some reason.
@george1421 Thanks! The TFTP service definitely wasn’t running so that was an issue, but it is now and as a result of attempting to capture the traffic it seems as though the FOG server isn’t receiving any TFTP requests. I’m at a loss because I didn’t change any of the DHCP settings and confirmed they’re correct. I did follow this guide to set it up a while back: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence but it had been working fine until now.
@george1421 They’re Windows servers but I confirmed my suspicions because it turns out the TFTP service wasn’t running for some reason. It’s been restarted now so I’m going to test again. I’ll let you know how it goes. Thanks for the input though, it’s been very helpful!
@foggymind Did some more testing and legacy PXE boot doesn’t work either, with error E-23. So I think it might be something related to the TFTP service. Not sure how to verify the status but I’ll do some digging to see what I can find.
@foggymind Some background, both UEFI and legacy PXE were working fine before this.
@george1421 Thanks for the quick reply! I’m waiting to hear back to see if our DHCP servers are in sync, but the fog server and client are both on the same subnet. I did check the configuration for 66/67 and they are correct on all three DHCP servers so I think everything is configured correctly it just seems like that TFTP service isn’t running for some reason or something is blocking it. This error happens when attempting UEFI boot, but I just tried a legacy PXE boot and the got the message PXE-E32 TFTP open timeout.
Hi all,
Just started randomly receiving this error while attempting to UEFI boot:
NBP filesize is 0 Bytes; PXE-E18: Server response timeout
I have 3 DHCP servers that sync with each other but I haven’t changed any settings on them or the fog server. It just seemed to come out of nowhere. Any ideas?
Thanks!
@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.
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!