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

    Optiplex 960. Intermittent DHCP issues during PXE boot. No DHCP offers received.

    Scheduled Pinned Locked Moved
    FOG Problems
    4
    6
    5.1k
    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.
    • C
      Christian Nichols
      last edited by

      I have FOG running in a virtualbox on my workstation and has been working great for the last 7 months until we received a new batch of Optiplex 960’s we are putting in a few labs. The issue is when booting to network PXE-E51 No DHCP or proxyDHCP offers were received. This is an intermittent problem… sometimes works… sometimes don’t… some not at all. These computers were refurbished and have different versions of the Intel Boot Agent but its still intermittent (even if they have the same version).

      Our setup:
      [LIST]
      []FOG is running on Ubuntu 10.04 LTS
      [
      ]Windows 2008 r2 as our DNS/DHCP/Domain server.
      []I’ve set options 066 and 067 correctly.
      [
      ]Went into DHCP Scope properties > Advanced and checked “Both” under Assign IP addresses dynamically to client of.
      [*]Switches connect the buildings together. I haven’t messed with the switches (we probably have close to 2 dozen switches total on our network).
      [/LIST]
      AFAIK, this is only affecting the Optiplex 960’s.
      Has anyone else had issues with this Dell model? Any tips or advice?

      [B]NOTE:[/B] Plugged an Optiplex 960 directly into the wall ethernet port and got the No DHCP offers received. Then restart it but this time plugged the ethernet into our KVM/Ethernet Switch combo that is connected to the SAME wall port and it worked perfectly.
      This is a weird issue. Advise please.

      1 Reply Last reply Reply Quote 0
      • C
        Christian Nichols
        last edited by

        bump

        1 Reply Last reply Reply Quote 0
        • K
          Kevin
          last edited by

          Especially with a new batch of hardware that’s causing problems, have you updated the BIOS on them, also, have you tried a different kernel? 3.6.9 seemed to work with our Dell’s really well.

          "The quieter you become, the more you are able to hear"

          New to FOG? Check the [URL='http://www.fogproject.org/wiki/index.php/FOGUserGuide']Wiki[/…

          1 Reply Last reply Reply Quote 0
          • B
            BryceZ
            last edited by

            Christian, this sounds to me like it might be a switch configuration issue; if you’re using Cisco switches check to see if PortFast is enabled.

            1 Reply Last reply Reply Quote 0
            • J
              jdorst
              last edited by

              Just had this same issue where I wasn’t getting an IP on PXE boot. Turns out it was an issue with the BIOS update. The newest right now is A18, but I had to go all the way back down to A04 (Intel Boot Agent 1.3.27) to be able to pick up a PXE IP. I also tested others in between with no success. A04 was the highest that would actually grab the address.

              Here is a link to the BIOS. Give it a shot.
              [url]http://www.dell.com/support/drivers/us/en/555/DriverDetails/Product/optiplex-960?driverId=1NTXN&fileId=2731108670[/url]

              Hope this helps!

              1 Reply Last reply Reply Quote 0
              • J
                jdorst
                last edited by

                Another possibility is that if you are using HP ProCurve switches, the Spanning Tree protocol could be causing the delays which will cause pxe to timeout. I am not sure why reverting to an older bios will help this, but maybe they simply have a longer timeout period.

                TRY turning spanning tree OFF for the switch that the system you are wanting PXE boot is connected to and see if that helps. If it does, then this could be an option for when you need to reimage a room. It is probably best to ensure Spanning Tree is re-enabled when finished to ensure there is some protection from network loops.

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

                218

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project