/build/static/layout/Breadcrumb_cap_w.png

Troubles with iPXE and Dell 7060 and 5060 Computers - With Boot Manager Enabled

10/11/2018 1775 views
When attempting to image Dell Optiplex 7060 and 5060 systems, after selecting the KBE and inputing our imaging boot authentication password, we would get the message http://<k2000_IP_Address>/boot/pxe_login.php ... Connection timed out (http://ipxe.org/4c0a6092)
Could not boot: Connection timed out (http://ipxe.org/4c0a6092)
Could not boot: Connection timed out (http://ipxe.org/4c0a6092)

I attempted to supply a username and password for boot authentication and still received the same connection timed out issue.
Turning off the boot authentication username and password allowed us to image. We would like to turn the boot authentication back on at some point.

Has anyone else been having this issue or issues with the new Dell Optiplex 7060 and 5060 machines?

We are on K2000 v 6.0.425 and have been using iPXE with many other images since the beginning of September.
7 Comments   [ + ] Show comments

Comments

    • Channeler
    • 11 months ago
    • last edited 11 months ago
    Are you sure this only happens with these two devices?

    Are they on a different Subnet?

    If you plug another model to the same spot it will go fine?
    (This is to make sure a switch is not getting in the way).

    These are new models... maybe see if they are already using the Latest BIOS version from DELL, stock versions from Wave 0 are not my favorites...

    If it works fine for others, maybe these BIOS versions are not ready for iPXE Boot manager yet?

    iPXE is an open source protocol, it does not care about brands or models, it pushes the boot files and it's up to the computer to process it accordingly.

    https://en.wikipedia.org/wiki/IPXE

    If any other Device or VMs are fine, then iPXE, DHCP, and the KACE are fine too... iPXE is open source, it works fine for my "wood PC" (A 2012 AsROCK mobo, with an i5 2500K and one module of RAM, doesn't even have an HDD).

    I'll start with a BIOS update
    • When I plug a different model into the same spot, it will image fine. It does not matter which network jack I plug into. I have tried updating the BIOS and the same connection issue occurs. Other models like the Optiplex 5050 and 990 image fine, so I don't think it is iPXE or DHCP. I think that these new models are some how throwing something back during the connection process that either Kace is not catching or is causing the issue.
  • We don't have any 7060s but I can confirm the same experience on the 5060s. Don't know if there are different variants for the network card on this model but ours came with the Intel i219v.

    We have been having this issue since around July when we first rolled out this model at one of our campuses. I have gone through the process of updating the BIOS with each new version that was released between July and now. With the latest version it now shows the MAC address when doing a network boot but it has not fixed the issue and were still presented with the Connection timed out.

    I have also gone through the process of rebuilding the KBE with the specific drivers (original version from July as well as the latest from September but that did not resolve the problem. We also tested putting it on the same VLAN as the server to see if it was a network communication issue. Following that, I put in a support ticket and we went through the troubleshooting steps to ensure the unit was functioning correctly.

    We also have Latitude 7480s that only boot UEFI similar to the 5060s and those work with no issues. At this point it looks like an issue with the BIOS on this model. It was suggested to give Dell Solution a call to see if we can get something working for this model but I haven't had a chance to do that yet.
    • Our 5060 has the same Intel I219v running a driver version 12.17.8.9 from 12/27/2017. I have also tried updating the BIOS on the 5060 to the latest one (1.2.14) from September, but no luck. I tried a custom KBE, but no luck there as well.
        • Channeler
        • 11 months ago
        • last edited 11 months ago
        interesting input, we were about to purchase a couple 7060s.... I guess I'll wait...

        Maybe something related to the NIC card... You may not want to do it.. but, I would try a PCI nic card to see if that works..

        Or or... some kind of USB-A to Ethernet dongle...

        @RayanPersaud, What did DELL say about it?

        EDIT: Found this googling around, but unfortunately, we don't have cisco Switches.

        http://ipxe.org/err/040ee1

        Which states: * If connected to a Cisco switch make sure 'spanning-tree portfast' is enabled on the switch. Otherwise iPXE will fail establishing network connection.

        Might worth to try
  • Our environment is mostly switches and we did have our networking team double-check regarding spanning-tree portfast which we had this enabled from our previous imaging solution
  • I have been able to image the Optiplex 5060 with a USB KBE, but would to prefer that not be the default method for these models of machines. We have Juniper switches.
  • Have you made any progress on this? I am experiencing the same issue, USB KBE works for me as well, but not very desirable.
    I am suspecting it's related to Dell not having all the drivers correct for the model.
    • No further progress on this yet. Yes, the USB KBE works for me as well, but as you state, it is not very desirable. Kace support suggested turning on "spanning tree portfast" on our switches to see if this would resolve the issue. I am working with our network engineer on that. I have also downloaded the latest and greatest NIC, chipset, and BIOS drivers from Dell and put them in place, but it doesn't seem to work even after re-caching the drivers. ::Sigh::
  • I got mine working, I just want to make sure we are having the same issue. When you get up to the KBE (Boot environment where you get your GUI) does the command screen stop at that point, telling you it cannot connect? If so, does performing an 'ipconfig' yield an IP or no results?

    If the answer is no IP address, then here is what I had to do...

    Download and install the Windows 10 ADK version 1803. (1809 is not currently supported) https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install

    Download out newest PE10 driver pack from here:
    https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fsupport.quest.com%2fdownload-install-detail%2f6087400&c=E,1,koq_fG7dKwaB2G6mCiVSWTgACKgtiOH4cO8Rzlpe_TY125n59hycX2NTY3t2zYDgniu81EYcobq_nR3CY7UprS3aULv40hqhAwW-Otg4m8Q3&typo=1

    (export the PE10 driver pack into \\yourk2000IP\drivers) But first go into the KBE_windows_x64 and x86 and backup / delete any old drivers in there. Make sure to re-cache your drivers on the K2000 after they are in.

    Follow this guide to build your KBE with Media Manager or KBE Manipulator:
    https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fsupport.quest.com%2fkace-systems-deployment-appliance%2fkb%2f184391%2fhow-to-create-a-kbe-for-windows-10&c=E,1,ULt_YtPyxw1yG4c7UZJpB7Kq0L0G1DUESc6N6jvwv_Kr1TBzmoSfnUDARazkwPNnpmvenK3BT8lKLnyYjiddhxquAWO5T3KAgfbsqD7r_A,,&typo=1

    (Basically point the SDA at your install location for the ADK)

    Also had to use the driver feed to pull in the drivers for each device (I exclusively run scripted installs, so you may not need to do this step)

    Good-luck!
    • I am running into the "http://<k2000_IP_Address>/boot/pxe_login.php ... Connection timed out (http://ipxe.org/4c0a6092)" message after I select the KBE and enter the authentication password. I don't get to the GUI.
      • Channeler
      • 10 months ago
      • last edited 10 months ago
      that is not the issue, this is even before reaching Windows PE, but good instructions in regards how to properly build a KBE.

      The issue is that 5060 and 7060 BIOS, are unable to process the iPXE boot file fast enough when Boot Manager is enabled... other computers are working fine.

      Guys, this is not a driver's issue , 100% guaranteed.

      @AAnschuzts , Were you able to enable PortFast in your switches?

      Have you tried to contact DELL in regards this issue with these two models?

      Remember that iPXE (the protocol being used by KACE), is Open Source software, it is being used by several other solutions as well, DELL will now about it.
      • I don't think it is a driver issue. I don't think it is an iPXE issue because I am able to image other model machines and was able to when authentication was turned on. I have the ticket in with KACE about this. I am waiting on my network engineer to setup/enable spanning tree portfast so I can test to see if it will remedy the problem. I have not contacted Dell support yet.
  • Having this issue with some 5050's and 7050's. Same exact message a AAnschutz. Any Update to this issue?
    • I have been working with Kace support and Dell about my 5060 and 7060 imaging issues. I have installed the latest BIOS on the 7060. But I still get the same issue as above after enabling the boot manager authentication and specifying a password, or a username or a username and password. I am not having any issues with the 5050s here. They seem to be working fine for us.
      • The 5050's were fine up until the past 2 or 3 BIOS updates. Now we can only boot with them via USB.
        The 7050's were in our environment pre-SDA, so not sure if these ever would have worked
        Latitude 5580 and 5590's appear to be fine right now. I'm surprised there isn't more buzz about this online, this is pretty impactful.

All Answers

0

Are you sure it is not a network problem.

If it is working with other machines, try a different port.

Answered 10/11/2018 by: akmagnum
Red Belt

  • Imaging is working with other models. I have tried on different ports with the same connection time out issue.
0

We have had some issues it seems with the 7060's.  It was hit and mis.  I uploaded the nic drivers to the \\k2000ip\drivers\kbe_windows_x64\custom\7060\Network folder.  You can download them from the Dell website.  I had to recreate my KBE environment that we use to the latest version for our Win10 v1809.  Once I completed this, the issue stopped.  

Answered 07/10/2019 by: kjfaucheux@lpssonline.com
Senior White Belt

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.