• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    PXE issue and FOG

    Scheduled Pinned Locked Moved Solved
    General Problems
    2
    5
    741
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jemerson93
      last edited by

      Fog has been working fine until today. Currently receiving an issue stating tftp://192.168.1.25/default.ipxe…Error 0x3d126001 (http://ipxe.org/3d126001)
      Chainloading failed, hit ‘s’ for the iPXE shell; reboot in 10 seconds

      I’ve been troubleshooting this for about an hour and stuck on the resolution.

      1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator
        last edited by

        192.168.1.25 is your fog server?

        Is this a ubuntu based system? If so please check the apache error log for guidance.

        Error 0x3d126001 is in the iPXE tftp module but I don’t think your issue is with tftp, because iPXE is already running to do the chainload function.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        J 1 Reply Last reply Reply Quote 0
        • J
          jemerson93 @george1421
          last edited by

          @george1421 No, that was the strange part. The fog server is 192.168.1.155. Also this is running on Ubuntu.

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @jemerson93
            last edited by george1421

            @jemerson93 Did the fog server ever change its IP address? And/or what device is 192.168.1.25? I can see what is going on, but I need to know the actors first.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            J 1 Reply Last reply Reply Quote 0
            • J
              jemerson93 @george1421
              last edited by

              @george1421 George, thank you. The issue has actually been resolved. For some reason, checking what was using .1.25 did not cross my mind. As soon as I did a scan of our network, I found that someone had booted up our old imaging server which was located at 1.25. Once I turned it back off, Fog returned back to normal.

              Issue has been resolved!

              1 Reply Last reply Reply Quote 1
              • 1 / 1
              • First post
                Last post

              269

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project