boot uefi don't work
-
@george1421
my fog server ip is in 172.16.0
and the scope of computer in 172.16.2. range -
@pascald73 So yes or no target computer is on the same subnet as the FOG server? You tell me IP address but not subnet mask to answer the question.
-
@george1421 said in boot uefi don't work:
o yes or no target computer is on the same subnet as the FOG server? You tell me IP address but not subnet mask to answer the question.
sorry, submask is 255.255.0.0 -
i try the option 60 pxeclient.
i have another errorerror
PXE-E16: No offer received -
@pascald73 OK so the answer is yes they are on the same IP subnet. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
Follow those instructions to create a network pcap (packet capture). Upload the pcap to a file share site and either post the link here or send me a Private Message with a link to the pcap and I will look at it and tell you what is wrong.
-
@george1421
i have tcdump port 67
but i’m totaly newbie in linux.
i don’t kwon to send you the cap -
@george1421
hello
I sent the files by link in private message
thank you for your help -
@pascald73 based on your pcap I think you have your dhcp server configured like this, which is wrong because you did not define dhcp option 66. Understand this is only a guess based on what I see.
-
@george1421
hello george
i have set this for a long time with my fog server 1.2.0
my image capture
-
@pascald73 Ok I see the problem. You need to remove (uncheck) the dhcp option 66 values in each policy. Make sure this is unchecked in your policy
-
@george1421 When you have your policies configured correctly they will look like this.
You see only one value is set in each policy and that is dhcp option 67. The dhcp option 66 is only set at the scope level because that does not need to change between different types of booting computes.
-
@george1421
this is the wrong configuration: option 66 was checked.
a big thank you for your patience and the time spent with me
