Posts made by dskinner

I restarted a PC in a different building and it immediately booted to FOG. This other building is on a different VLAN than my test PCs or the Fog Server. The FOG server and the test PC are on the same VLAN. We changed VLANs on my test port and the laptop booted to FOG as intended. We are currently looking at ACL settings. I have created a ticket with our network engineers who swore there are no differences between switches or VLANs. Beyond that, I will be setting up DNSMASQ as soon as I find the resolution to the differing VLANs and thank you for your help.

@Sebastian-Roth said in PXE boot VM sucess PXE Boot Laptop Fail:

Just saw this and wanted to say that changing values in .fogsettings does not cause any change in FOG itself. You need to re-run the installer to see the change being applied. If you set us know what exactly you changed we might be able to tell you if this could be related or not.

I miss typed the default gateway address.

@george1421 Thank you for the information. I have another project that I have to pick up for the day but I will be sure to get back to you with my results later this week.

The DHCP server is a VM hosted on a Cicso blade server off campus. That is outsourced and

I can work with the tech on that. I have asked him to confirm setting 66 and 67 a few times in the process, and should be able to get limited support from them for easier stuff. Otherwise, Laptops and the imaging server are on the same VLAN.

@george1421 @Sebastian-Roth The machines are on the same VLAN, and same switch Cicso 4510 r+e. The DHCP server is a VM hosted on a Cicso blade server off campus. That is outsourced and I am not familiar with the specs on that. I just found on error in .fogsettings, fixed it and restarted the Fog VM. This made no effect on the timeout issue.

@Sebastian-Roth I have test these. I am able to manually tftp the file with the windows laptop with the firewall on and off. The fog server and the laptop are on the same vlan as the VM that was able to pxe boot to the fog menu without issue.

I have am running 1.5.9-RC2 on Ubuntu 18.04 LTS, I have Option 66 and 67 set to direct PXE boot as directed. Option 67 being Undionly.kpxe. If I use KVM to create a new machine by PXE booting I am successful. When I try to PXE boot from various laptops I I have a TFTP time out error PXE-E32 and PXE-M0F. I have used Wireshark to monitor the communication. With the VM there is the expected TFTP traffic. With the Laptops there is none. The network ports and switches are configured the same between VM to Fog, and Fog to the laptops. I am using legacy boot on the laptops. Out of curiosity I did test it the other way and had the same outcome. What might I be missing?

Turns out someone was annoyed that our network went down and plugged in their personal router. Thank you for the advice.

@george1421 thank you, that is not the is not an IP that we use in our network. I will look into that.

Hello,
I started experiencing this last week. DHCP is managed by an an outside provider, and they insist that setting 66 and 67 have been updated to make fog the PXE boot server. That in mind they just updated their windows server, and and firewall software. I can use terminal to reach it with tftp, and the status is active. I rolled back to a previous snapshot that worked 100% and I get the same timeout.

Any suggestions?

Thank you