• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. RAThomas
    3. Best
    R
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 11
    • Best 2
    • Controversial 0
    • Groups 0

    Best posts made by RAThomas

    • RE: UEFI is not booting with Windows DHCP

      @cjiwonder It may help if you tell us what model of PC you’re trying to boot. There may be a BIOS setup option that needs adjustment.

      For example, my Dell 3430s’ BIOS setup requires the following boot options:

      General -> Boot Sequence: Onboard NIC(IPV4) (checkmark to enable)
      General -> Boot Sequence: UEFI (checkmark to enable)
      AND “Onboard NIC(IPV4)” must be the first device in the boot sequence list

      But I must also have the following options in different menu set:

      System Configuration -> IntegratedNIC: Enable UEFI Network Stack
      System Configuration -> IntegratedNIC: Enabled w/PXE

      posted in FOG Problems
      R
      RAThomas
    • RE: UEFI is not booting with Windows DHCP

      @cjiwonder said in UEFI is not booting with Windows DHCP:

      @george1421 There is no error message, “>>Start PXE over IPv4” message and after a minute booting to HDD. Fog Server and PXE boot client are in the same VLAN but DHCP server is in a different VLAN. Tried with snponly.efi, intel.efi and pexe.efi but no luck. There is no issue with the DHCP IP release if I boot the PC in Windows, and there is no issue in booting with undionly.exe on the same PC. I am new to Wireshark, please guide me to run the capture filter. Thanks.

      I just remembered that I had pretty much the same problem recently.

      My problem was that the Ethernet link negotiation was taking too long on the Cisco 3850 switch I had the client connected to. The link negotiation took about 30 seconds and the IPXE wait for DHCP also took about 30 seconds, but always failed. This problem only happened for me when booting UEFI - worked fine booting BIOS / Legacy.

      The solution for my case was to add this to the client port configuration on my Cisco switch:

      spanning-tree portfast
      
      posted in FOG Problems
      R
      RAThomas
    • 1 / 1