1 2 Previous Next 15 Replies Latest reply on Nov 12, 2009 8:34 AM by Joe11701

    PXE failure




      I am trying to capture an image i've created with WinPE, I believe that i've gone through the proper steps, but when i PXE boot and get the menu (F8) select WinPE, the image doesn't download, i recieve a TFPT download failure message.


      Could somwone walk me through the steps to get this running?

      The consultant that assisted in the install had it working.


      thanks in advance.

        • 1. Re: PXE failure
          phoffmann SupportEmployee

          Do this thread help you?


          PXE Boot fails with TFTP timeout error:

          - http://community.landesk.com/support/docs/DOC-1230


          - Paul Hoffmann

          LANDesk EMEA Technical Lead

          • 2. Re: PXE failure



            Both the PXE Rep and the target are on the same network, wired in, (actually right next to each other.)


            I'm not getting any further clarity than what's on the screen on the target pc.


            is there a log on the PXE rep i can check?

            • 3. Re: PXE failure
              phoffmann SupportEmployee

              Not really, is the sad truth (you can imagine the fun we have because of it).


              The "fun" part about PXE is that the server can only see requests and send stuff, and the client is in so low a level of functionality (remember, you're effectively booting on the network card), so client-side troubleshooting (where you'd really get the most out of it) is in effect impossible.


              Now - ONE thing you can try, is to find out whether it's the NIC/Firmware ('cos it's that which holds the PXE-ROM)  that's causing you trouble. See if you can get ahold of a nice, vanilla 3COM or Intel NIC (something basic without fancy stuff, a Pro/100 would be ideal) and shove that into the desktop you're trying to PXE boot. This will be a one-stop check to see whether you're having network-issues of some sort, or whether the hardware you've got is acting up.


              If it works with the "basic PCI NIC" you'll need to check to upgrade the Firmware of the NIC you're actually using (I'm guessing that'd be the LOM - LAN on Motherboard?) -- which first of all should get a BIOS update (BIOS updates contain NIC-Firmware updates) to see if that helps you along .


              - Paul Hoffmann

              LANDesk EMEA Technical Lead

              • 4. Re: PXE failure



                I've dug a little deeper into the wherewithall of the PXE rep, and found that the image (LDVPE1.img) is NOT installed on my pc (the PXE rep)


                of course it failed.... aint nothing bein' transferred.


                i removed the PXE rep and i'm now redeploying it to see if the image file has been sent over.

                • 5. Re: PXE failure
                  phoffmann SupportEmployee

                  Nice find. I'll confess though, that's the first time I hear of that particular variant ... odd.


                  *crosses fingers for your next attempt*


                  ... push come to shove, you should be able to copy them across manually - but I don't see how they could fail in the normal script except for something like space issues ... rather peculiar.


                  Certainly good groundwork on your part - that should hopefully allow you to have it up and running soon!


                  - Paul Hoffmann

                  LANDesk EMEA Technical Lead

                  • 6. Re: PXE failure

                    Further study....


                    none of the files that should have been copied are on the pc.


                    i'm attaching the log file from the deployment of the PXE rep for your edification.


                    Here's the content of the log file....


                    "NYLSPDSKTOP023","OK",1605,0:00:01,11/5/2009 8:50:57 AM,11/5/2009 8:50:58 AM,"MsiExec.exe /q /X{F238CE99-6614-4072-9D20-1D2FA7ED951A}"
                    "NYLSPDSKTOP023","OK",0,0:00:20,11/5/2009 8:50:58 AM,11/5/2009 8:51:18 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\ldvpe1.img, C:\Program Files\LANDesk\LDClient\ldvpe1.img, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:05,11/5/2009 8:51:18 AM,11/5/2009 8:51:23 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\ldlinux.img, C:\Program Files\LANDesk\LDClient\ldlinux.img, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:23 AM,11/5/2009 8:51:23 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\files\bootmenu.1, C:\Program Files\LANDesk\LDClient\bootmenu.1, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:23 AM,11/5/2009 8:51:23 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\files\bstrap.0, C:\Program Files\LANDesk\LDClient\bstrap.0, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:24 AM,11/5/2009 8:51:24 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\files\dosundi.1, C:\Program Files\LANDesk\LDClient\dosundi.1, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:24 AM,11/5/2009 8:51:24 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\bootmenu.0, C:\Program Files\LANDesk\LDClient\bootmenu.0, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:01,11/5/2009 8:51:24 AM,11/5/2009 8:51:25 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\dosundi.0, C:\Program Files\LANDesk\LDClient\dosundi.0, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:25 AM,11/5/2009 8:51:25 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\bzImage, C:\Program Files\LANDesk\LDClient\bzImage, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:01,11/5/2009 8:51:25 AM,11/5/2009 8:51:26 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\pxelinux.0, C:\Program Files\LANDesk\LDClient\pxelinux.0, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:26 AM,11/5/2009 8:51:26 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\default.boot, C:\Program Files\LANDesk\LDClient\default.boot, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:27 AM,11/5/2009 8:51:27 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\default.menu, C:\Program Files\LANDesk\LDClient\default.menu, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:27 AM,11/5/2009 8:51:27 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\ntdetect.com, C:\Program Files\LANDesk\LDClient\ntdetect.com, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:01,11/5/2009 8:51:27 AM,11/5/2009 8:51:28 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\ntldr, C:\Program Files\LANDesk\LDClient\ntldr, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:28 AM,11/5/2009 8:51:28 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\startrom.0, C:\Program Files\LANDesk\LDClient\startrom.0, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:28 AM,11/5/2009 8:51:28 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\winnt_pxe.sif, C:\Program Files\LANDesk\LDClient\winnt_pxe.sif, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:28 AM,11/5/2009 8:51:28 AM,"C:\Program Files\LANDesk\ManagementSuite\landesk\vboot\winnt_pxemenu.sif, C:\Program Files\LANDesk\LDClient\winnt_pxemenu.sif, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:01,11/5/2009 8:51:28 AM,11/5/2009 8:51:29 AM,"\\\ldlogon\provisioning\windows\prov_winnt.sif, C:\Program Files\LANDesk\LDClient\prov_winnt.sif, TOREMOTE"
                    "NYLSPDSKTOP023","OK",0,0:00:00,11/5/2009 8:51:29 AM,11/5/2009 8:51:29 AM,"\\\ldlogon\provisioning\linux\linuxpe.default.cfg, C:\Program Files\LANDesk\LDClient\linuxpe.default.cfg, TOREMOTE"
                    "NYLSPDSKTOP023","OK",229392385,0:00:35,11/5/2009 8:51:29 AM,11/5/2009 8:52:04 AM,"<qt/>C:\Program Files\LANDesk\LDClient\sdclient.exe<qt/> /p="" /msi /N /An /Ac /g="{F238CE99-6614-4072-9D20-1D2FA7ED951A}""
                    "NYLSPDSKTOP023","OK",0,0:00:16,11/5/2009 8:52:04 AM,11/5/2009 8:52:20 AM,"<qt/>C:\Program Files\LANDesk\LDClient\LDISCN32.EXE<qt/> /NTT= /S="" /F /SYNC /NOUI"
                    ; "Job Complete","1 Done","0 Failed","0 Off","0 Unknown"

                    • 7. Re: PXE failure
                      phoffmann SupportEmployee

                      Now that's odd ... especially since all of the entries in the log are an "OK" (usually indicating that nothing went wrong) ... what kind of device are you trying to install this on?


                      And - just to sanity check yourself - do you have a lab-machine (ideally a virtual host) that you can run this script against ...?


                      Since all was "OK" I don't think the problem was in copying the files off of the Core ... quite odd...


                      - Paul Hoffmann

                      LANDesk EMEA Technical Lead

                      • 8. Re: PXE failure

                        the PXE rep is an HP desltop with plenty of disk space.... yes it is quite odd.


                        I'll copy them manually and wee what happens....

                        • 9. Re: PXE failure

                          The PXE boot still happens, but the file still doesn't download.....


                          i'm going to try a different PXE rep. not sure why this is happening.

                          • 10. Re: PXE failure



                            I think the pc that i designated as a PXE rep is somehow corrupt, i'm going to try to use a different pc on the same subnet.

                            • 11. Re: PXE failure
                              Jared Barneck SupportEmployee

                              Looks to me like PXE is working but TFTP or MTFTP isn't working...which means you may be right...could be something on that machine.


                              However, it could be something on your image, in which case all machines will see the issue and you have to figure it out.

                              • 12. Re: PXE failure

                                Don't think so, the consultant who helped install got the OS Deployment stuff to work fine. We removed the PXE rep from the pc he was using.


                                I went through the process of removing the LANDesk agent on the pc i'm using, and then i put it back on. that's why this pc is not a good candidate for PXE rep.

                                • 13. Re: PXE failure

                                  I'm going to use a differerent pc for a PXE rep.


                                  thanks for all the advice!

                                  • 14. Re: PXE failure
                                    phoffmann SupportEmployee

                                    Worth trying - could be that the box is just "gone strange" for lack of a better term really.


                                    Apologies on the delay in responding, but I'm on the road quite a bit and don't get to catch up as much here as I'd like most of the time.

                                    1 2 Previous Next