/build/static/layout/Breadcrumb_cap_w.png

PXE boot fails on Dell Precision M3800 with Dell LAN7500 dongle

Hi,
What is the process to PXE the Dell Precision M3800? These machines have no Ethernet port and use a USB dongle from Dell or a Dell USB 3 dock for network
When attempting to PXE boot the dongle seems to be detected but not getting the bootfile from KBOX. The USB dock is not recognized at all.
Choosing the boot option for network see a Lan7500 (dongle I assume) but not receiving bootfile. If you have solved this, I would appreciate the steps to get there :)


0 Comments   [ + ] Show comments

Answers (2)

Posted by: Nico_K 9 years ago
Red Belt
0
Does the PXE boot is starting or it is this also an issue?
Then you should check the BIOS settings (NIC with PXE or similar)

If the PXE boot is starting (giving you the info it is searching for a server etc) and fails, you should verify that you are in the same subnet like the K2000 (or set the network config so the protocol routing is working correctly)

If the KBE is finally starting and cannot mount the K2000 you simply need to inject the driver into the KBE
https://support.software.dell.com/kb/SOL111719
The needed driver is part of the driver packs
Posted by: SMal.tmcc 9 years ago
Red Belt
0
You need to add the doc drivers to the KBE to get that nic to work.  Those dell dongles have been nothing but a problem here.  They are usb 3.0 so you need the usb 3.0 drivers in the kbe and have fun trying to find the drivers for the dongle to add to the KBE.  That particular dongle is designed for win 8.1 and has a built virtual CD that is injects the drivers into a windows 8.1 env when connected, but does not do that automatically in  winpe 5.0. I went thru a lot of testing with the dell tablets and found the cheap startech dongle works better.  I manged to harvest the drivers from the virtual CD and that still did not help.  The tablets would only UEFI boot so pxe was out for me.  But to get the dongle to work in the uefi boot env I had to let the winpe os start loading and unplug and replug the dongle so it would then add its drivers to the env.  If I was not fast enough to do the replug I had to type startnet.cmd at the prompt to get the startup script to reload after the dongle was finally discovered.  Best advice do not use the dongles for imaging, they work fine post but are a hassle to initialize during the winpe env

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ