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

    Topics created by mark29

    • M

      Add pc to domain after deploying image

      Feature Request
      • • • mark29
      2
      0
      Votes
      2
      Posts
      294
      Views

      Tom ElliottT

      @mark29 The dynamic nature of images and systems FOG doesn’t track the IP address of systems, anymore. In really early versions it did track the IP address at least but hasn’t for quite some time.

      That said, I think what you’re asking for is possible but it would require a Snapin to do so, and even that would be ugly. (If it truly must be static, this would be the best route in the end if you’re requiring only using FOG to manage this I think.)

      You would create a Powershell scriptp that utilizes the Set-NetIPAddress statement and probably need a lookup to figure out which device needs to be using which IP address and all (that’s really the ugly part.)

      The best case, though, I think, is to utilize DHCP reservations, as this would not require any special programming or even a snapin for that matter (another kink that can potentially not work appropriately.)

      The DHCP server options of your AD controller, can be used to define specific IP’s in an automated way, rather than rely on a program to set the IP address.

    • M

      Unsolved PXE-E32: TFTP open timeout

      FOG Problems
      • • • mark29
      2
      0
      Votes
      2
      Posts
      2.6k
      Views

      george1421G

      @mark29 said in PXE-E32: TFTP open timeout:

      it screens PXE-E32: TFTP open timeout.

      This can be (most commonly) caused by either

      DHCP options for that subnet have dhcp options 66 set incorrectly. You have two or more dhcp servers on that subnet and both don’t have all of the setting needed to pxe boot. The tftp service is not running on your fog server.

      I would setup a witness computer on the same subnet as the pxe booting computer that witness computer will run wireshark, with a capture filter of port 67 or port 68 or use a display filter of BOOTP. Start wireshark and then pxe boot the target computer until you get the error, then stop the wireshark capture.

      Now review in wireshark the OFFER packet. This comes from the dhcp server to the client.

      Look to see if you only have one OFFER packet. You should because the pxe error is “Open timeout”. Look at the OFFER packet in the ethernet header verify that both the {next-server} field has the IP address of the FOG server, and the {boot-file} has the proper FOG boot loader. Now look at the DHCP options under option 66 and 67 they should match whats in the ethernet header.

      FWIW: I’ve seen soho routers that eventhough you properly configure them, they set themselves (the routers) as the pxe boot server and not what you put in dhcp option 66.

    • 1 / 1