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

Pxe timeout error after upgrade to 1.4.0 rc7

Scheduled Pinned Locked Moved Solved
General
2
5
1.6k
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.
  • S
    Smokinjoe68
    last edited by Apr 21, 2017, 7:17 PM

    After the upgrade to version 1.4.0 rc7 clients will no long pxe boot. TFTP open timeout error. Has anyone encountered this problem?

    G 1 Reply Last reply Apr 21, 2017, 7:33 PM Reply Quote 0
    • G
      george1421 Moderator @Smokinjoe68
      last edited by Apr 21, 2017, 7:33 PM

      @Smokinjoe68 what is the error message you get?

      Is the FOG server supplying the dhcp info to the target computers?

      If you have a clear screen shot of what the pxe client is not doing, it might give us a direction to move in.

      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!

      1 Reply Last reply Reply Quote 0
      • S
        Smokinjoe68
        last edited by Apr 21, 2017, 7:54 PM

        No. I have another server as my dhcp server. Here is a screenshot of the error:
        0_1492804429487_upload-a4482a02-214c-4882-8045-e2675a1f3f8b

        G 1 Reply Last reply Apr 21, 2017, 8:35 PM Reply Quote 0
        • G
          george1421 Moderator @Smokinjoe68
          last edited by george1421 Apr 21, 2017, 2:37 PM Apr 21, 2017, 8:35 PM

          @Smokinjoe68 Is your fog server and the pxe booting clients on the same subnet/vlan? If so lets grab a pcap of the pxe booting process.

          https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

          There is no need to hide the private IP address inside your network. There is no useful information there, I can’t connect to 192.168.x.x over the network to hack your computer. If this was a public IP address I would feel differently. But then you would have bigger issues than me trying to hack your network.

          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!

          1 Reply Last reply Reply Quote 0
          • S
            Smokinjoe68
            last edited by Apr 21, 2017, 9:04 PM

            Someone had made a change to the dhcp server and took option 066. Working now. Thanks

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

            193

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project