@frankv24 - RESOLVED - First thank youfor all your responses the forum is great. We narrowed this down to the issue to be on the 4th floor IDF of the 10.15.100.* subnet by shutting down each fiber interface on the MDF to the floors IDF’s - Once the 4th floor was shutdown the PXE boot worked. We then narrowed are search to the 4th floor IDF switch where we found a NETGEAR wireless router connected in student lab to the 4th floor IDF - Once this swithc was reemoved - the entire 10.15.100 subnet was able to PXE boot

@frankv24 - RESOLVED - First thank youfor all your responses the forum is great. We narrowed this down to the issue to be on the 4th floor IDF of the 10.15.100.* subnet by shutting down each fiber interface on the MDF to the floors IDF’s - Once the 4th floor was shutdown the PXE boot worked. We then narrowed are search to the 4th floor IDF switch where we found a NETGEAR wireless router connected in student lab to the 4th floor IDF - Once this swithc was reemoved - the entire 10.15.100 subnet was able to PXE boot

@Sebastian-Roth Thanks for the response - We did not capture from our DHCP server, We used another machine connected to the same switch and subnet 10.15.100.* as the machine we were pxe booting from.

@george1421 The filter was set on the witness machine and was not specific to .203. We saw traffic, but no traffic from .203 which was the machine we were pxe booting - Thanks for the response.

@george1421 - Thanks We captured data while trying to image a machine on the 10.15 network where are fog server is on the 10.8 network all other subnets work except 10.15 subnet, when adding capture filter 67 and 68 no data was found for .203 machine we remove the capture filter and get this output for ,203

see new attachment of message when we enter the the tftp server 10.1.100.201

We have been using FOG for 10 years, Recently we can not image from ONE of our subnets but all other subnets still work. ALL subnets worked previously. The scope has! been recreated for the subnet we are having problems with. The scope options 66 and 67 are the exact same on all our subnets DHCP scopes and have been confirmed. We have configured a test FOG server to rule out this is a FOG server problem and it still is not working.