• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Tags
    3. dhcp
    Log in to post
    • All categories
    • G

      DHCP failed: no configuration method succeeded - after automatic reboot

      General Problems
      • fog 1.5.10 dhcp dhcp server ipxe dhcp ipxe • • gabrielzeit
      7
      0
      Votes
      7
      Posts
      1.0k
      Views

      G

      @george1421 Yes it is. Both, the fog server and the host device, are in VirtualBox - and i get the error message.
      But tbh if the problem doesn’t show up when deploying the whole system in my network, i can live with the error occurring in VB.

      If it’s true that this only happens in VB and not on the actual network (and then Toms solution works), then this issue is resolved for me.

    • P

      Unsolved error DHCP

      FOG Problems
      • dhcp • • pacodijou
      3
      0
      Votes
      3
      Posts
      638
      Views

      Tom ElliottT

      @pacodijou You likely need to rethink how FOG operates.

      The fact that you got into FOS itself (which is where you’re at) at least shows DHCP is working and passing the Options 66/67 appropriately, but it’s failing to get access to the fog server.

      Based on what I can see, the DHCP items are working properly, assuming 192.168.75.10 is the fog server since that’s also where it’s trying to connect to look for access directly to the fog server.

      Do you access the fog server at url:
      http://192.168.75.10/fog/index.php?

    • A

      Enabling DHCP after install

      General Problems
      • dhcp • • ayoward
      4
      0
      Votes
      4
      Posts
      780
      Views

      A

      @Sebastian-Roth Sorted. Many thanks for your help!!

    • B

      Solved Client tries to pull bootfile from DHCP server

      Linux Problems
      • ubuntu dhcp tftp tftpboot dhcp.conf • • Base2Nathan
      6
      0
      Votes
      6
      Posts
      1.2k
      Views

      S

      @Base2Nathan Good to hear you figured it out. You might wonder why the config George suggested doesn’t use option tftp-server-... and option bootfile-name at all. There are two places in DHCP packets where PXE boot information can be placed. One is DHCP options as you have used them. But there is also next-server and filename what are fields within the DHCP header information. Take a closer look at the wireshark dump…

    • M

      Solved Trouble with DHCP after loading undionly.kpxe (xcp-ng)

      FOG Problems
      • dhcp boot error • • magikmw
      9
      0
      Votes
      9
      Posts
      1.2k
      Views

      S

      @magikmw Glad to see you found and fixed this. It’s good to know you really know your way around in that network stuff. It’s very hard for us to diagnose and help out with that kind of things.

    • mecsrM

      HP EliteDesk 800 G4 - Failed to get an IP via DHCP!

      Hardware Compatibility
      • hp elitedesk 800 g4 dhcp ipxe dhcp • • mecsr
      11
      0
      Votes
      11
      Posts
      3.0k
      Views

      george1421G

      @mecsr Great. I’m glad you have it working.

      Just as a word of warning, don’t advanced past the 4.15.2 version of the kernel until you update FOG, and even then stick with 4.15.2 until the developers can dig into why 4.17.0 is acting slow.

    • M

      Solved FOG initial images boots but cannot subsequently locate DHCP server

      FOG Problems
      • fog 1.5.3 dhcp • • MrPatrick
      5
      0
      Votes
      5
      Posts
      1.4k
      Views

      M

      Hi, yeah I’d understood what you were getting at. I’ve tested with a dumb switch in line at the client end and it worked first time.

      Many thanks for your help.

    • S

      Solved Yet another PXE-M0F error topic!

      FOG Problems
      • dhcp pxe-m0f centos 7 wireshark • • Sven-Ervin
      14
      0
      Votes
      14
      Posts
      4.4k
      Views

      S

      Hi once again!

      Our problem, as it stands today, is solved. We ended up trying to install the FOG server on the same subnet with the host machines, which worked. After that we tried putting the machine back on the subnet where all our VMs are located. That broke it. Later the network admin realized that during his configuration he accidentally left a space after the IP on option 66. After that was fixed things stated working out.

      So in the end what I was chasing was a typo.

      A big thanks to @george1421 for being as helpful as You could during the troubleshooting process.

      I am now happily deploying my Windows 10 images. 🙂

    • F

      Acer travelmate b usb to ethernet

      FOG Problems
      • usb-to-ethernet acer dhcp • • fox134
      14
      0
      Votes
      14
      Posts
      2.3k
      Views

      george1421G

      @fox134 Well lets hope you don’t have an ipxe.exe in there…

      The client gets its booting information from (the) dhcp responsible for assigning an ip address to the target computer. So if you want the target computer to use a different boot file then you might update dhcp options 67.

      Now with that said, from your OP you say that FOG is giving out the IP addresses on a dedicated imaging network. So if you want to change the boot file, you will need to edit the dhcp config file on your FOG server.

      To see what you config file looks like, you can review this example: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Example_1

      You will see for arch 7 and 9 it calls out ipxe.efi. You can replace that with maybe snponly.efi or any of the other efi files. Then you must restart your dns server. On ubuntu you would issue the command sudo systemctl restart isc-dhcp-server to restart the service.

    • C

      Solved Issues With DHCP and PXE Booting on an Isolated Network

      FOG Problems
      • pxe ubuntu 16.04 windows 7 intel atom dhcp • • cdutko
      14
      0
      Votes
      14
      Posts
      4.8k
      Views

      C

      @george1421 You are an absolute legend George. It works now and I was able to PXE boot from my client PC and upload it to the Hosts screen. I can view it on the network and everything is working correctly.

      Thank you so much!

    • S

      Unsolved macOS update broke iPXE

      Mac Problems
      • mac dhcp fog • • sysadminatelier
      23
      0
      Votes
      23
      Posts
      10.2k
      Views

      S

      Just cross-linking this here: https://forums.fogproject.org/topic/10615/ipxe-booting-possibly-broken-on-os-x-sierra-update

    • K

      Unsolved FOG Client causes unwanted Shutdown of any Windows Host straight after booting

      FOG Problems
      • fog client windows 10 windows dhcp dhcp client shutdown • • kouzinger
      7
      0
      Votes
      7
      Posts
      2.6k
      Views

      J

      @Tom-Elliott from the logs: 10/7/2016 10:32 AM PowerManagement On demand shutdown requested. An on-demand shutdown is always queued and not being cleared. We need a clear on-demand tasks button.

    • R

      Solved Configuring existing ISC-DHCP Server to work with FOG v1.2.0

      Linux Problems
      • dhcp • • ramblingbiped
      12
      0
      Votes
      12
      Posts
      8.6k
      Views

      Wayne WorkmanW

      @Sebastian-Roth said:

      @Wayne-Workman I like the “Related_to_xyz” naming. Would suite other things as well I guess. Might wanna add this to the Knowledge Base which is linked on the main wiki page!?

      Done.

    • arnaudrigoleA

      Solved Impossible to boot on PXE......

      FOG Problems
      • pxe fog debian 8 dhcp 66 & 67 • • arnaudrigole
      41
      0
      Votes
      41
      Posts
      27.6k
      Views

      Wayne WorkmanW

      @Sebastian-Roth said in Impossible to boot on PXE......:

      Wireshark filter bootp && tftp is great for this

      This has been in the wiki for some time, here:
      https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP

    • S

      Unable to Register Optiplex 780

      FOG Problems
      • dhcp proxydhcp optiplex 780 register • • SBrady
      13
      0
      Votes
      13
      Posts
      5.6k
      Views

      Wayne WorkmanW

      We have some Lenovos that are weird.

      Pull the power cable and patch cable, hit the power button a few times, plug everything back up and auto-magically those weird ones start working…

    • 1 / 1