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

Tftp connection timed out 4c126092

Scheduled Pinned Locked Moved Unsolved
FOG Problems
2
6
819
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.
  • T
    TectonicLeader
    last edited by TectonicLeader Apr 1, 2024, 12:06 PM Apr 1, 2024, 6:04 PM

    I am trying to learn how to setup a fog server and create my girst image. When I try to connect to the server I am getting this then booting to my OS. Display Picture

    1 Reply Last reply Reply Quote 0
    • T
      TectonicLeader
      last edited by Apr 1, 2024, 7:15 PM

      I am using a Netgear router R6700v3 and 2 non standardized computers for the server and client. I can see the tftp when checking from Windows 10 on the client computer but it times out while trying to boot to it.

      G 1 Reply Last reply Apr 1, 2024, 8:58 PM Reply Quote 0
      • G
        george1421 Moderator @TectonicLeader
        last edited by Apr 1, 2024, 8:58 PM

        @TectonicLeader Many soho routers will point to themselves as the boot server, even if they have the facilities to set dhcp option 66 and 67.

        If you have no option other than to use your netgear router as your dhcp server, then I recommend you install dnsmasq onto your fog server. It takes about 10 minutes to do and will solve your soho router issue. https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

        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!

        T 1 Reply Last reply Apr 2, 2024, 3:12 PM Reply Quote 0
        • T
          TectonicLeader @george1421
          last edited by Apr 2, 2024, 3:12 PM

          @george1421 well it certainly changed the end result but still no success. New Display Image

          G 1 Reply Last reply Apr 2, 2024, 4:42 PM Reply Quote 0
          • G
            george1421 Moderator @TectonicLeader
            last edited by Apr 2, 2024, 4:42 PM

            @TectonicLeader Very good you are making progress. On the plus side dnsmasq and pxe booting is working perfectly.

            I have to ask you did you change the IP address of the fog server since fog was installed. The default.ipxe file has a hard coded IP address in it. Your picture shows it picked up default.ipxe from .3, but then default.ipxe called a .2 IP address. If you did change the IP address of the fog server after the install you can fix the configuration by hand. I was sure I had a tutorial on this, but I can’t seem to find it right now.

            1. In the FOG Web UI goto FOG Configuration->FOG Settings and press the expand all button. Search for the old IP address and replace it with the current IP address.
            2. Still in the FOG Web UI goto Storage Management and pick the default node (it should be the master node). Change the IP address in there to the proper one.
            3. Log into the fog server’s linux console, and switch user to the root user so you can edit a hidden file (if your fog server has a linux desktop you can use gedit from the linux desktop too). Edit a hidden file /opt/fog/.fogsettings note the dot at the beginning of a file makes it hidden in the linux world. Correct the IP address listed in the config file.
            4. Lastly rerun the fog installer to fix all of the other bits where the IP address is hard coded.
            5. Inspect the content of the /tftpboot/default.ipxe file to ensure the IP address has been corrected. (this is the point where your error exists).
            6. If everything looks good, try pxe booting again.

            On a side note, pxe booting from net3 might be a problem in some of the fog code (not specifically this issue). Typically the fog code only looks for the first two network interfaces to boot. But since you got as far as loading default.ipxe using net3 might be OK.

            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!

            T 1 Reply Last reply Apr 3, 2024, 3:29 PM Reply Quote 0
            • T
              TectonicLeader @george1421
              last edited by Apr 3, 2024, 3:29 PM

              @george1421 That did the trick. Now I need to dig into why its failing to capture an image. I’ll make a different post for that though if I need to.

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

              153

              Online

              12.1k

              Users

              17.3k

              Topics

              155.3k

              Posts
              Copyright © 2012-2024 FOG Project