• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Tags
    3. ipxe tftp boot
    Log in to post
    • All categories
    • K

      PXE-E23: Client recieved tftp error from server

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems tftp error ipxe tftp boot
      13
      0 Votes
      13 Posts
      18k Views
      K

      @george1421 thank you for all the help yet again 🙂

      seems to be all working as my router for the dhcp server and the fog server as the pxe server.

      PS. i have to say it is a really nice project/community to flow in like this with people willing to help thnx appreciated.

    • S

      chainloading error with latest undionly.kpxe

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems ipxe tftp boot
      5
      0 Votes
      5 Posts
      2k Views
      S

      Ok, thanks @URfog that put me on the right track. My fog web server is not a storage node. I added it to the list of storage nodes with a max clients of 0 and I can boot normally now.

    • JJ FullmerJ

      Is this a thing? Adding Option 003 and Option 012 on windows dhcp fog server reservation options

      Watching Ignoring Scheduled Pinned Locked Moved General ipxe tftp boot dhcp options option 66 option 67 windows dhcp
      12
      0 Votes
      12 Posts
      6k Views
      MRCURM

      @Arrowhead-IT It’s definitely worked for test VM’s that are used for image testing, but it’s also a more general comment for ESXi in general. Worth checking your server guests to ensure they’re all on vmxnet3.

    • F

      pxe doesn't boot to menu

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems ipxe tftp boot
      9
      0 Votes
      9 Posts
      4k Views
      Wayne WorkmanW

      @fjarken said:

      Ah yes I have STP setup on my network, I came back to this thread again, cause I found a conflicting IP with my fog server…which I think was the root cause. A switch on my network had been configured with the same IP.

      I’ll be sure to start asking this… seems its a more common problem than what one would think.

      Gotta love happy endings.

    • 1 / 1