• 0 Votes
    15 Posts
    5k Views
    G

    @george1421 @Tom-Elliott
    Luckily I could schedule a meeting with my System-Admin today, and he tried turning off the serving of the WDS boot file - seems in the configuration of option 66 and 67 of our companies DHCP server was an old Windows Server that served a meaningless WDS file, we changed it to my FOG Server and the issue is now solved.

    I am very thankful for your first-class support and I apologize for the inconvenience! You guys are my heroes!

  • 0 Votes
    7 Posts
    6k Views
    J

    @george1421 said in Dell Optiplex 3080 - UEFI - PXE Boot E-21: Remote boot cancelled.:

    Side note: If your network doesn’t have a dhcp server I would personally use isc-dhcp server on your fog server over dnsmasq. I would use dnsmasq if you have a dhcp server run by someone else and can’t update settings. In this case dnsmasq would supplement your unchangeable dhcp server.

    THANK YOU!

    I set up isc-dhcp and it’s working like a charm.

    For any future people reading:
    I modified /etc/dhcp/dhcp.conf with the below config.
    I disabled dnsmasq. systemctl stop dnsmasq.service
    I started isc-dhcp service dhcpd start
    I tsuccessfully PXE booted with my Dell 3080 a few times.
    I permanently disabled dnsmasq. systemctl disable dnsmasq
    I set isc-dhcp to start automatically. systemctl enable dhcpd

    option space PXE; option PXE.mtftp-ip code 1 = ip-address; option PXE.mtftp-cport code 2 = unsigned integer 16; option PXE.mtftp-sport code 3 = unsigned integer 16; option PXE.mtftp-tmout code 4 = unsigned integer 8; option PXE.mtftp-delay code 5 = unsigned integer 8; option arch code 93 = unsigned integer 16; # RFC4578 use-host-decl-names on; ddns-update-style interim; ignore client-updates; next-server 192.x.x.7; authoritative; subnet 192.x.x.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; range dynamic-bootp 192.x.x.200 192.x.x.254; default-lease-time 21600; max-lease-time 43200; option domain-name-servers 192.x.x.7; option routers 192.x.x.7; class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } }
  • 0 Votes
    6 Posts
    1k Views
    george1421G

    @FuriousGamer065 So did you use my tutorial and config file exactly to setup your dnsmasq service? https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

  • 0 Votes
    8 Posts
    2k Views
    george1421G

    @Fernando-Gietz said in Dell Optiplex 7050 and UEFI boot. Failed:

    I wonder if is a miracle that it has worked well until now in the other hardwares

    I’m glad you have it working now. Yes its strange why you didn’t find another system with the same issues. But that is why I included both, I ran across a system that would boot with the netboot info alone.

  • Dell Inspiron 15 7559

    Hardware Compatibility
    29
    0 Votes
    29 Posts
    10k Views
    M

    @george1421

    Fired up my test Dell Inspiron 7559 through UEFI boot and it first failed but that was my fault. I forgot to undo all the changes to the ltsp.conf I had done on Friday. After I changed the boot files all back to ipxe.efi the Dell 7559 booted just fine to the FOG menu and also successfully registered with the FOG server using the quick registration. I guess your assumption was correct about the funky setup of the Parallels UEFI VMs. BIOS works GREAT on those VMs, it’s just the EFI boot that doesn’t get through the bzImage phase.

  • Default ipxe & dnsmasq

    FOG Problems
    11
    0 Votes
    11 Posts
    9k Views
    S

    @AeonLucid Awesome debugging information!!! Lots of thumbs up for you. I am a bit late now but I did see the post just now. Funny that but I had the exact same thing happening with my home router when trying to debug some other iPXE stuff at home. It seams like there are DSL routers out there which send ‘next-server’ in their DHCP OFFER/ACK without handing a filename to the client. I am not sure why they do (and I guess most don’t). So your client asks for PXE boot. Gets next-server from the router DHCP and your proxy. It seams to be fine in the first run where Intel PXE ROM boots up but as iPXE comes up it uses the next-server send by your router instead of the proxy one. Run wireshark on your FOG server and you should see it in the DHCP packets broadcasted by your router (original firmware).

    Instead of flashing the router you could have also build your own iPXE binary with a customized script - I talked to Tom and we might add that at some point anyway, now that we know more people see this.

    Let me know if you want to know more about custom iPXE…