Hello, I have setup FOG and configured it to work with our DHCP server. I am able to always PXE boot straight into fog, but then when trying to contact DHCP for a lease it just fails to get an IP after the third loop.

I was able to successfully get it to work and upload an image by switching the network during the DHCP lease process on my laptop, but ONLY on my laptop. Luxury of having different ethernet cables in the office go to different vlans.

We have the options configured correctly, have available IP’s in DHCP, I disabled the linux firewall, our network has no firewall within the WAN blocking anything. Any idea why I am not geting a DHCP lease and how to fix it?

Thank you,

Brent

Hello,

To use Ubuntu, what is the recommended version to run the latest version of FOG?

Otherwise, does the newest version of CentOS work well for FOG too?

Thanks,

Brent

@Sebastian-Roth It was a windows 7 machine that couldn’t be logged into so it was wiped and then imaged with windows 10. Otherwise, I did nothing else with the machine or the network configuration.

@Sebastian-Roth They are on two different VLANs. One handles DHCP through a cisco switch and the other handles DHCP through a server.

@Sebastian-Roth They are on two networks. They act as DHCP for all of the things on their individual IP scheme. aka .112 and .126 networks. The DHCP doesn’t seem to be the problem because I watch the device get assigned the IP. It is after that when TFTP hangs.

@Sebastian-Roth As far as changes go, none were made before the issue. I disabled firewall to troubleshoot and I can TFTP from any laptop on our network. I have 2 networks set to give DHCP one is a switch and one is a DHCP server both work fine for giving the DHCP address for the PXE boot. It just seems to be this machine having an issue with TFTP.

@Quazz Yes same switch and the same network. I tried switching ports on the switch. I am also using the same cable and port plugged into the other PC’s.

I217-LM network adapter

The machine pulls an IP from DHCP just fine during the boot, it just seems to be TFTP that is not working on this machine.

Hello,

I have not been able to TFTP to FOG using a physical HP EliteDesk, but I have no problem doing it from all of my ProDesks. What is weird is that I was able to image this computer before no problem, but now it cannot connect to TFTP during PXE boot or in CMD in windows with TFTP enabled.

Any thoughts?

Thanks,

Brent

@Sebastian-Roth Fog 1.5.4

label: gpt
label-id: DFAFD110-4056-45E9-93A3-26B20C4262D7
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/sda1 : start= 2048, size= 921600, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=425EA038-B5C0-4F46-897F-D99D3DB7A8D9, name=“Basic data partition”, attrs=“RequiredPartition GUID:63”
/dev/sda2 : start= 923648, size= 204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=510C200E-959C-4838-88C0-B0B1766A8287, name=“EFI system partition”, attrs=“GUID:63”
/dev/sda3 : start= 1128448, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=849A76EF-6F9A-4035-B121-6D90B22EEA9B, name=“Microsoft reserved partition”, attrs=“GUID:63”
/dev/sda4 : start= 1161216, size= 498956288, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=6DCB35C2-4B57-4CB3-B85E-EE6512F0D2B8, name=“Basic data partition”

File was named d1 partitions. Only file with a similar name to the ones above.