Troubles with iPXE and Dell 7060 and 5060 Computers - With Boot Manager Enabled
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.
Answers (4)
I am slightly resurrecting this post because I continue to have this issue. I have just completed the upgrade for the SDA to 7.2.97. I was hoping that upgrading to the latest version would be something different for Dell Optiplex 5060 and 7060 machines with a boot manager password. But, I still get a pxelogin.php message after inputting the boot manage password. I can image Optiplex 5050 with no issues. I am using the same port. I am using a newer KBE I created in August for both. Any other ideas from the great Kace crowd would be helpful. Thanks.
Andy
Comments:
-
I'm sure it's their NIC, I don't have any of those handy, but I would be curious to test if an external NIC (USB to Etth), or Internal (PCI) NICs are able to complete the process.
Basically, same exact device, but with a known good PXE Capable Network Card.
(I mean the stock ones are PXE capable, but they seem to have troubles with iPXE's Boot Manager).
https://www.amazon.com/Intel-EXPI9301CTBLK-1000Mbps-PCI-Express-Network/dp/B00830H91M/ref=sr_1_4?crid=2KA0C0HJ79H1J&dchild=1&keywords=intel+network+card&qid=1600720750&sprefix=intel+netw%2Caps%2C234&sr=8-4
or
https://www.amazon.com/Intel-Gigabit-Network-Adapter-EXPI9301CTBLK/dp/B001CY0P7G/ref=sr_1_3?crid=2KA0C0HJ79H1J&dchild=1&keywords=intel+network+card&qid=1600720750&sprefix=intel+netw%2Caps%2C234&sr=8-3
I understand this by NO MEANS is a proper solution to the problem, it should narrow it down by a lot. - Channeler 6 months ago
Are you sure it is not a network problem.
If it is working with other machines, try a different port.
Comments:
-
Imaging is working with other models. I have tried on different ports with the same connection time out issue. - AAnschutz 2 years ago
I am also having the same issue.
With help from support, we were able to find that if I temporarily disable the "Enable Boot Manager Authentication,"
the Dell AIO 7060 will boot straight into the PXE Menu allowing for a scripted installation.
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.
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 - Channeler 2 years ago
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. - RyanPersaud 2 years ago
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 - Channeler 2 years ago
I am suspecting it's related to Dell not having all the drivers correct for the model. - SearchDocur 2 years ago
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! - SearchDocur 2 years ago
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 know about it. - Channeler 1 year ago
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. - robertsj 1 year ago
If you type a wrong password (on purpose), are you prompted for a password again, or Will it error out?
Have you tried attaching a USB2Eth adapter, plug the network cable to it, and re-create the issue?
(this is to rule out a possible firmware incompatibility issue with that particular built-in network card). (you will need an adapter capable of iPXE, Startech and DELL, they sell good ones).
If you move your affected device to the SDA subnet (same subnet), Are you able to replicate the issue?
e.g.
SDA IP: 192.168.46.5
Test Device IP: 192.168.46.6
This is to reduce the amount of hops in between the SDA and the affected device.
Also, it's been a year, I would say see if there's a newer BIOS version and apply it. - Channeler 1 year ago