Do you still get the exact same error message “No DHCP or proxyDHCP offer received”? If not, post another picture.
No I never got that error I always got the TFTP timeout error.
@sebastian-roth I started from scratch with a new VM and used a different subnet to see if that was the issue but it’s all the same.
Thank you for reminding me about those changes. I added them to dhcpd.conf again but still no dice. I’m back to square one.
Yes I work at a recycler there’s lots of different equipment I’ve checked.
I was able to even capture a few windows images using VirtualBox. But I just figured out that everything works fine ONLY in VirtualBox. Nothing has changed when trying to PXE boot a physical laptop or PC. Still get a TFTP timeout error.
A dumb switch doesn’t make a difference for either the virtual or physical PXE attempt. (Virtual works every time, physical does not). I’m not using any fancy networking. The physical laptop uses the same exact adapter that is bridged to VirtualBox when it succeeds so I have no idea what is going on. I have restarted both the VM’s and the actual server but that hasn’t fixed it.
Server ->VirtualBox - Success
Server->Dumb Switch->Physical Laptop-Fail
I captured two pcap files. One from the successful VirtualBox and one from the unsuccessful TFTP timeout physical laptop.
With debug enabled you should get to a command shell after a while. Please run the following commands and take a picture:
Here you go:
By the way, did you see my post on extending your dhcpd.conf to get option 66/67? https://forums.fogproject.org/post/141631
Yes I made those changes but nothing changed with either the attempt to PXE boot VirtualBox or the physical laptop.
Can you please run tail -f /var/log/apache2/access.log while PXE booting the VirtualBox VM? You should see requests for boot.php, then bzImage and init.xz and lastly another request as connection check which we see in the picture. Do you see all those?
I PXE booted to the failed registration attempt but unless I’m doing it wrong this file is completely empty for me. See below:
@sebastian-roth Disabled the firewall but the issue persisted. I got something else though.
Here’s the pcap file for the following registration attemp I’ve outlined below: output.pcap
I tried doing a registration like you suggested and I got this:
However, if I wait a couple of seconds while in the FOG menu, the registration will start (I tested waiting a few seconds on memtest and it started running fine) but DHCP will fail. See here:
As far as the setup, I have my physical proxmox server with the installed FOG VM setup to use its interfaces. I have a laptop with VirtualBox running that is plugged directly into the back of the server. To PXE boot I have a bridged adapter for VirtualBox to use to PXE in the VirtualBox settings.
I’ve tried eliminating the complexity by also by just physically PXE booting the actual laptop. But I keep getting the same results anyways so it’s just faster to use VirtualBox for me without having to restart over and over again.
Edit: Thought I should clarify though, that the TFTP timeout issue when PXE booting the actual laptop hasn’t changed. Just thought that VirtualBox getting past that might say something about what issue could be.
@george1421 I think I might have something.
I tried something and I think I got something. I tried PXE booting using Virtualbox instead. IT DOES SUCCESSFULLY PXE BOOT but take a look at network interface. During the PXE boot you can see that it’s not up initially.
After getting to the fog menu this is what happens when you try and pick an item (in this case memtest). You can see that the connection is dropping for whatever unknown reason.
The cables are good. The equipment and ports are good, everything lights up. DHCP is working. Fog management page is accessible.
I’m out of ideas here.