PXE-E99: Unexpected Network Error
-
@rlair23 Did you turn on https on the fog server for some reason?
Is 10.10.11.33 indeed your fog server’s IP address?
-
@george1421 I do not recall turning on https, saw the option but selected no. And yes 10.10.11.33 is the IP address of my server.
-
@rlair23 Is this a new FOG install or it has always worked but now it doesn’t. I’m trying to understand did it ever work?
-
@george1421 This is new server. Has never worked.
-
@george1421 The windows DHCP server is on the same subnet. Also applied these settings:
https://docs.fogproject.org/en/latest/installation/network_setup.html
Is this also necessary? - https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy
-
@rlair23 dhcp options 66 and 67 need to be set for basic pxe booting. The issue with dhcp option 67 is that if you need to boot uefi you need to enter ipxe.efi. If you want to pxe boot a bios client you need to change the value to undionly.kpxe. That is the static way of doing it.
The bios uefi coexistence wiki tells you how to setup profiles to give you a dynamic pxe booting. Does it need it, no. Does it make your life easier if you have a mixed environment, yes.
Since this is a new install.
- Make sure the unbuntu firewall is disabled.
- On the client computer make sure secure boot is disabled.
We may need to get a packet capture of the pxe boot process to understand what is going sideways.
If you have more than one dhcp server (such as a fail over dhcp server), make sure you set the options in both servers
-
@george1421 Disabled the firewall on the ubuntu server, the pxe rep would be the ubuntu server correct? Or would that be the client that I am booting to pxe? Thanks.
-
@rlair23 said in PXE-E99: Unexpected Network Error:
the pxe rep
Not sure I understand “rep”.
Secure boot is a setting on the pxe booting computer in the firmware settings.
The unexpected network error bugs me. But first lets check the basics since this is a new install.
-
-
@rlair23 I’ll raise your tutorial with one of my own: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
The next step is indeed to get a pcap of the pxe booting process. You can either use wireshark on a witness computer or for a bit more information since the pxe booting computer and fog server is on the same subnet use tcpdump on the fog server. This will collect both the broadcast and unicast messages between the fog server and target computer.
You can either look at the pcap or post it to a file share site and DM me the link in the fog project chat. If you want to look at it I can give you where to look, though it would be quicker if I looked at it because there are a few exceptions.
