none
OSD on PXE rebooting - TFTP problem RRS feed

  • Question

  • Hey all,

     

    Long term lurker - these forums have been very helpful. I believe I have a unique problem however!

     

    I've got SCCM on Win2k3 SP2 x64 with SQL 2005 SP2 x64, WDS & WSUS 3 x64 installed. DHCP is on a different server, but in the same scope as SCCM & client so no DHCP helper problems.

     

    I had OSD working for a while, and it was going great. Suddenly, it stopped working and after the PE background appears it'd hang for a few minutes then restart. So I turned on a command shell in PE to see what is going on, and I found this:


    Code Block
    <![LOG[Executing: X:\sms\bin\x64\smstftp.exe -i 10.0.2.200 get \SMSTemp\2007.10.18.15.56.40.0001.{548F11AC-C51C-44BC-98F2-1CA1BEA753B9}.boot.var X:\sms\data\variables.dat]LOG]!><time="15:56:36.921+000" date="10-18-2007" component="TSPxe" context="" type="0" thread="768" file="tspxe.cpp:177">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="15:56:36.921+000" date="10-18-2007" component="TSPxe" context="" type="0" thread="768" file="commandline.cpp:229">
    <![LOG[Set command line: "X:\sms\bin\x64\smstftp.exe" -i 10.0.2.200 get \SMSTemp\2007.10.18.15.56.40.0001.{548F11AC-C51C-44BC-98F2-1CA1BEA753B9}.boot.var X:\sms\data\variables.dat]LOG]!><time="15:56:36.921+000" date="10-18-2007" component="TSPxe" context="" type="0" thread="768" file="commandline.cpp:701">
    <![LOG[Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 10.0.2.200 get
    \SMSTemp\2007.10.18.15.56.40.0001.{548F11AC-C51C-44BC-98F2-1CA1BEA753B9}.boot.var X:\sms\data\variables.dat]LOG]!><time="15:56:36.921+000" date="10-18-2007" component="TSPxe" context="" type="1" thread="768" file="commandline.cpp:799">
    <![LOG[Process completed with exit code 1]LOG]!><time="15:56:36.953+000" date="10-18-2007" component="TSPxe" context="" type="1" thread="768" file="commandline.cpp:1071">
    <![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="15:56:36.953+000" date="10-18-2007" component="TSPxe" context="" type="0" thread="768" file="fwopen.cpp:146">
    <![LOG[Failed to downloaded pxe variable file. Code(0x00000001)]LOG]!><time="15:56:36.953+000" date="10-18-2007" component="TSPxe" context="" type="1" thread="768" file="tspxe.cpp:187">

     

     

    So, errr, TFTP is failing somehow. Using a command shell, I've got an IP and I can ping the SCCM server ok. Running the smstftp manually fails with a timeout. Running the same command on the SCCM server itself works, which means TFTPd is ok. Likewise running it from other servers in the segment also works.

     

    So what is stopping me from getting the PXE control file?? Does SCCM's WinPE have a firewall? I presume it must, given the statement "successfully removed firewall rule for tftp". How do I disable this, for testing if nothing else!

     

    Thanks!

    Thursday, December 13, 2007 3:10 PM

Answers

  • There's really not a way to extend the timeout for this that I know of, but there has been a related long-standing issue with PXE and switches that is due to a switch setting to avoid network loops called Spanning Tree Protocol (STP).

     

    Make sure that PortFast is enabled on the switch ports you're using or else the negotiation between the port and the client may cause the timeout.

     

    Here's a related article:  http://support.microsoft.com/kb/555477

     

    Monday, January 7, 2008 5:07 PM
  •  

    Ok, for reference this appears to be a NIC/switch issue.

     

    Using the command shell, I can see it never gets an IP address and stays in the 169.254 range. If I do an ipconfig /renew quickly after I see the network card appear in ipconfig then it gets an address and it works.

     

    I basically think my NIC is taking too long. Can I extend the timeout somehow?

    Thursday, December 13, 2007 9:25 PM

All replies

  •  

    Ok, for reference this appears to be a NIC/switch issue.

     

    Using the command shell, I can see it never gets an IP address and stays in the 169.254 range. If I do an ipconfig /renew quickly after I see the network card appear in ipconfig then it gets an address and it works.

     

    I basically think my NIC is taking too long. Can I extend the timeout somehow?

    Thursday, December 13, 2007 9:25 PM
  • There's really not a way to extend the timeout for this that I know of, but there has been a related long-standing issue with PXE and switches that is due to a switch setting to avoid network loops called Spanning Tree Protocol (STP).

     

    Make sure that PortFast is enabled on the switch ports you're using or else the negotiation between the port and the client may cause the timeout.

     

    Here's a related article:  http://support.microsoft.com/kb/555477

     

    Monday, January 7, 2008 5:07 PM
  • We ran into this same issue today:

     

    Failed to download pxe variable file. Code(0x00000001)

    PxeGetPxeData failed with 0x80004005

     

    Turning on "spanning-tree portfast enable" on the port where the Cisco switch solved this problem for us.  Even though it could PXE boot without an issue the Task Sequence just failed part of the way through with the errors above.

     

    Matthew Evans

    Kraft & Kennedy, Inc.

    360 Lexington Ave.

    New York, NY 10017

    Direct: 212.692.5608

    email: evans@kraftkennedy.com

     

    Monday, January 7, 2008 5:36 PM
  • I get this error on the same port with one machine (hp7800) but not another (hpd530). The 7800 consistently displays this same error in smsts.log but when I connect the 530 it drops down the winpe image..performs the rest of the build without issue.

     

    Thursday, March 6, 2008 3:54 PM
  • I didn't mention the machine either - it was a HP 7800. Also, the HP 8510p laptops have the same problem and they both have the Intel 82566 NIC in them.

     

    In the end, we plugged them into a different switch and they worked fine. On Microsoft Update, new drivers appeared for them on 19th Feb but we've not tired them yet. They may solve the problem.

     

    Enabling the command shell (F8) and doing "ipconfig /renew" after ipconfig first returns a private IP address will get it to work.

    Thursday, March 6, 2008 4:07 PM
  • Thanks for your advice. I will take a look at the new drivers. All the ones I have tried so far...I get issues when trying to add them to the winpe.wim. Message says look at the log but it does not say which log and have not had chance to investigate yet. Incidentally the winpe properties then show the drivers as having been added but the actual .wim image has not changed so this is misleading.

     

    Considering another machine works fine on the same port I am suspicious about the winpe not containing either the nic or sata msd driver. Will update with my findings....

     

    ps. trying to ping the sccm/pxe server from the 7800 always seems to return PING: transmit failed, error code 1231 when using f8 straight after winpe has downloaded.

    Thursday, March 6, 2008 4:22 PM
  • Update on investigation..

     

    Still getting same result, successfully injected drivers from intel site into winpe image for intel nic and also injected sata drivers from HP site.

     

    Am using a static ip for this machine so ipconfig /renew is not an option..

     

    smsts.log shows "failed to download pxe variable file" as the first error followed by "pxegetpxedata failed"

     

    Little bit stuck with this one. Considering a different model machine works on the same port I am assuming the issue is machine/model specific.

     

    Wondering where this pxe variable file may be downloaded to... 

     

    Friday, March 7, 2008 11:11 AM
  • I'm having the same thing, using a sccm (With PXE role) in a lab works fine

    On my production environment however, i don't have a pxe role, only WDS (Which i loaded the WIM file into)

    Now, on boots, it reports the same missing file in smsts.log (I have a valid IP)

    Wednesday, March 19, 2008 1:56 PM
  • I have enabled Portfast and able to solve this problem thanks for your finding...
    Friday, March 28, 2008 2:55 PM
  • My issue was the 82566 intel nic. No amount of drivers from hp or intel site has got this working. Has anyone managed to get a successful pxeboot using this onboard intel nic? I have seen several links detailing others with pxe issues caused by 82566. cheers

     

    Monday, April 14, 2008 12:00 PM
  •  

    Is there a way to make it work without configuring the network equipment ?

    I've heard that enabling PortFast can make problems on your network

     

    Or.

    Monday, April 14, 2008 2:51 PM
  • Enabling PortFast will not create any problems on ports that clients plug into.

     

    I was experiencing the same problem and enabling PortFast fixed the issue.

     

    Tuesday, May 20, 2008 9:23 PM
  •  KelvinHankinson wrote:
    My issue was the 82566 intel nic. No amount of drivers from hp or intel site has got this working. Has anyone managed to get a successful pxeboot using this onboard intel nic? I have seen several links detailing others with pxe issues caused by 82566. cheers

     



    Hello, I was having this same issue, but after banging my head against my desk for a few days, I finally got squared it away!

    Using SCCM I was able to x86 PXE boot all of my workstations (Dell Optiplex 745 desktops, Latitude D620 and D630 laptops) and install my x86 Windows XP image flawlessly.

    Once I started attempting to boot the Optiplex 755 workstations my PXE would reboot itself right before the task sequence initiated and my SMSTS.log would show "Failed to downloaded pxe variable file. Code(0x00000001)". Opening a Command Prompt during the WinPE session and running an IPCONFIG showed that my computer was not initializing the NIC driver or getting an IP address (not even an 169.x.x.x)

    What I discovered was that this is an issue with the Intel
    82566 NICs and the Optiplex 755s. I was able to correct the issue by going into BIOS and changing the SATA Opertaion from AHC1 to ATA. In addition, make sure that you have a x64 boot image available regardless of whether or not you are booting an x86 install because PXE will recognize the Optiplex 755 as an x64 architecture.

    After that, I went into my OSD Boot Images and added the Vista 32-bit Intel Driver (E1E6032.inf from Dell Package R162323.EXE) to my x86 and x64 Boot image. (Strange I know) This allowed WindowsPE to obtain an IP address and start the Task Sequence.

    Finally, just make sure that your Config Manager driver catalog has the XP x86 driver available (E1e5132.inf) for the actual install and you should be set!


    Tuesday, July 1, 2008 5:57 PM
  • Not had a chance to look back into this for some time but after testing today it would seem injecting the vista drivers for the 82566 nic into the x64 pxe environment (even though that is not the one specified in the TS) gets this working. I am booting a hp7800 and it would appear this also gets classed as x64 architecture.

     

    Always the hardest ones to fix...when the fix makes little sense.

    Thursday, July 31, 2008 2:55 PM
  • Hi, I've followed your instructions to the point, but still the darn thing won't work. I'm having exactly the same problem as you regarding the nic, I've added the Vista 32-bit driver to the x64 image, but somehow the nic is not initialised.

    I've been trying to get this solved for days, but now I'm banging my head against the desk og what's closest to me and any help would be much appreciated.

    Thanks,


    Wednesday, August 20, 2008 7:49 AM
  • I would suggest updating to SP1 and the updating both the X86 and x64 boot image. This will give you PE 2.1 and it has both NIC and storage drivers for the HP7800… no need to inject drivers into the bootimage yourself

     

    Michael

     

    Wednesday, August 20, 2008 9:08 AM
  • Hi, sorry not to inform you in my post, but the PC I'm having problems with is Dell Optiplex 755. SCCM has been updated to SP1 prior to my post. How will I know if I'm on WinPE 2.1? Will this be installed automatically with SP1?

    Thanks,
    Wednesday, August 20, 2008 9:23 AM
  • I’m not sure.. but if WAIK is 1.1 in your add remove programs the WinPE is 2.1..

    About the Opiplex 755. I remember one customer, who had to hit F8 to get the prompt, and the do an “ipconfig /renew”  for the PC to get  an IP, otherwise it would just get a 169… address.   I trued to inject different NIC’s into the Boot.wim but it didn’t help, so they decided I had something to do with the switch (newer heard back from them, so I can’t say if I actually was the switch or not)

     

    Michael Petersen

     

    Wednesday, August 20, 2008 9:48 AM
  • Thing is, I don't even get a 169.254.x.x address so there's no help renewing the ip as it seems the nic is not initialised.

    Wednesday, August 20, 2008 10:11 AM
  • One step closer to a solution...Multicore CPU must be disabled in BIOS. When I did that the nic got an IP
    Wednesday, August 20, 2008 11:22 AM
  • Hmm that's kind of strange!!

     

    Wednesday, August 20, 2008 11:26 AM
  • Ok, I'm on the brink of insanity now. I've tried everything, I've followed the instructions in this post to the point. I've even added the drivers to the winpe.wim file but all to no avail. The darn computer still reboots before initialising the task. Thing is, after typing ipconfig /all several times the nic gets an IP but then the task has timed out.

     

    The computer in question is a Dell Optiplex 755. The OS I'm trying to install is Windows XP SP3. The computer is on the same vlan as the SCCM server. I've managed to get it to run the task sequence once, but somehow it failed applying drivers and software after the OS had been installed.

     

    If someone have a boot image that works or even an example of a working task sequence I would really appeciate an input or even a copy of it.

     

    I have 62 Dell Optiplex 755 that needs to be installed so getting them to work with SCCM would be a real time-saver.

     

    Any input and advice would be much welcome.

     

    Thanks,

     

    Friday, August 22, 2008 10:48 AM
  • Can you remove the (to be built) machine from the database. Delete the existing advertisement. Restart wdsserver service. Create your test collection. import your computer information (name/mac address) by way of Computer association and add to test collection. Advertise your task sequence to the collection with a command prompt enabled boot image.

     

    F12 your test box. Hit F8 when you can..

     

    What happens? can you map to your sccm server? What does smsts.log say? Does the advertisement status show any activity?

    Friday, August 22, 2008 4:10 PM
  • Hi, I had the same problem today with a HP DC 7700 SFF, strange thing is though we have been able to build other DC 7700's from PXE with out any problem.

    After seeing the post suggesting plugging the computer into a different switch, I grabbed a small 5 port 100mb switch we had lying around, plugged it in to the computer and LAN, and it is now building fine.

    Weird problem.

    Sally.
    Wednesday, September 24, 2008 7:39 AM
  •  i have problem with optain ip address in WinPE and after that task sequence cannot start!!!!


    1. press f8

    in cmd enter

    2. ipconfig /renew

    when you obtain ip address

    to start task run:

    3. start X:\sms\bin\x64\tsbootshell.exe or  X:\sms\bin\386\tsbootshell.exe

    and your task will start!!
    Tuesday, March 10, 2009 1:40 PM
  • I'm getting a similar problem to most people in this post.

    I have a TS all set up (Boot Images on normal and PXE DP).  I have even added the drivers suggested in this post as well as others to the boot images.  Here is what happens:

    I load the WinPE files from PXE just fine, the Bare Metal Machine boots into WinPE, and then hangs for about 15 seconds before kicking back out and failing.  So when I try F8 and get the command prompt in WinPE and try to do ipconfig /renew, I get the following message:

    "An error occurred while releasing interface LoopBack Pseudo-Interface 1 : The system cannot fid the file specified.

    The operation failed as no adapter is in the state permissible for this operation."

    As far as I can tell, this is some sort of driver issue, perhaps I just don't have the correct ones in the boot image.
    I am trying to boot/OSD onto a Virtual Machine (created using VMware Infrastructure Client).

    Thanks for any input.
    Friday, June 12, 2009 10:00 PM
  • I'm having the exact same issue with the new Dell Vostro 230 desktops. These devices use a variant of the BroadCom 57xx NIC. I had to chase all over until I found a driver that would work with the SCCM TS.

     

    Jimm

    Thursday, June 17, 2010 3:11 PM
  • I'm having the exact same issue with the new Dell Vostro 230 desktops. These devices use a variant of the BroadCom 57xx NIC. I had to chase all over until I found a driver that would work with the SCCM TS.

     

    Jimm

    I meet the same problem when trying to deploy Win7 to Dell Vostro 230 Desktops. I try to ad the BroadCom driver but still don't successful. Can you give me the link to download the right driver for SCCM TS.

    Thanks.


    mrthaiit@live.com CMC SI
    Wednesday, December 1, 2010 10:45 AM
  • I had the same problem with an HP Elitebook but after I read the post of TimWavBB and a I added the nic target computer vista driver x86 and x32 on the boot image all works fine.
    Friday, December 3, 2010 1:18 PM
  • I am having a similar problem with a HP ProBook 6550b.

     

    I have tried it with all of the windows 7 and windows vista Intel 82577 Drivers added to my x86 Boot Image.

     

    PXE is not the issue here, it has to do with the driver not being properly utilized by the Boot Image.  When I go to the F8 section, the network card never properly receives drivers, causing Windows PE to reboot the computer.  I never get to the section to select a task sequence.

     

    I have been loading every possible driver I can find for this computer, rebuilt my boot image, reloaded PXE and WDS, tried this on different Distribution Points on different subnets, and I am still getting this exact same problem.

     

    This happens about once  a year, with the new releases from HP, but it has never taken me more than 30 minutes to get the drivers working in my boot image.

     

     

    I also tried the BIOS changes, which didn't work, and shouldn't work, since the Hard drive is visible with F8.

     

     

    EDIT:  I just used the drvload.exe command with the .inf for the driver that I have loaded into my x86 Boot Image, and it installed perfectly.  I was then able to renew my IP address and run the TSBootShell.exe and select my Task Sequence.

    What is my next step in trouble shooting why the Windows PE boot will not load this driver on its own?


    Eddie
    Tuesday, December 21, 2010 6:10 PM
  • Rebuilt my Boot Image from scratch and then added only the driver that I knew worked.  Removed all other distribution points from the other Boot Images.  Then I got the computer to the task sequence selection.

     

    Slowly added drivers to the boot image and kept updating it, until I found the Intel 82567LM-2 to be the the problem.


    Eddie
    Tuesday, December 21, 2010 9:49 PM
  • Sorry to bring this old post up again...

    Eddie,

    What driver seemed to work for you?

     

    Nick

    Thursday, April 14, 2011 5:29 PM
  • nickROD,

     

    I have found that we had issue with using a USB stick (with Windows 7) on the HP7800, but when we used the CD boot media it worked fine (the whole time I had the correct drivers already injected, but the USB stick made it appear that the NIC drivers were bad because it was giving me an ip address).  I have read that you need to update the BIOS on the HP7800 before you can use a USB stick to image the computer.  So create boot media (ISO) from you task sequence and burn a CD and then try to image that way (it worked for me).  When using a USB stick it would not give us an IP address, I will look into ugrading the BIOS tomorrow on the HP7800 to see if it helps us get around this issue)

    Wednesday, June 1, 2011 7:40 PM
  • you can download all the necessary driver from intel.

    make sure that you load XP and VISTA driver only on your boot image

    remove any other driver beside hard drive and ethernet driver.

    Thursday, June 9, 2011 8:01 AM
  • had the same error with VWware machine, i am using vSphere 5 and created a new Windows 7 32 bit client and have the folloing message if i press f8 and show ipconfig it get correct IP address from the DHCP server

    failed to download pxe variable file" as the first error followed by "pxegetpxedata failed

     

    The issue only appear on vSphere 5 VMware machine version 8 and i am using e1000 nic so i am sure i have the correct nic driver and get IP address from the DHCP sever

    I have enabled the Port Fast on the Cisco switch and uninstall the WDS PXE role for that site server and re-install the WDS role and PXE role still not fix the issue.

    I dont have any issue with other secondary site. Only this site server with virtual PC.

     

     

    Wednesday, January 25, 2012 1:15 AM
  • I'm having the exact same issue with the new Dell Vostro 230 desktops. These devices use a variant of the BroadCom 57xx NIC. I had to chase all over until I found a driver that would work with the SCCM TS.

     

    Jimm

    Hi Jimm,

     

    I'm facing the same problem with a Lenovo 9645, which uses a broadcom 57xx NIC. I've tried various drivers from version 12.x from Lenovo's website to 14.8.x from the broadcom website to no avail. can you please post the link to the driver that you used sucessfully or even the version number.

    Thanks.

    Ben.

    Monday, January 30, 2012 2:53 AM
  • I am experiencing a similar problem.  When I PXE boot, it seems that my NIC is not initializing fast enough to load and get an IP before WinPE "gives up" and does an immediate reboot.  I have no idea how to solve this.  

    My NIC (after a few seconds) gets an IP address from DHCP and is on the network fine.  I don't think there's a way to make it initialize faster.

    I even added a sleep for 20 seconds line to the winpeshl.ini.  It doesn't seem to have an effect.

    Tuesday, March 20, 2012 9:15 PM
  • Hi

    I do have a same problem. When I PXE boot, it seems that my NIC is not initializing and not taking the ip adress. If i am doing ipconfig/renew it gives an error  message as below.
    The operation failed as no adapter is in the state permissible for this operation

    Tuesday, August 21, 2012 12:22 PM
  • Hey There Jimm and Ben,

    I too am experiencing the same issues with this BroadCom 57xx NIC.  Can you please post the location of the NIC drivers that were successful in resolving this issue?  It would be greatly appreciated.  Thanks

    -Stanley

    Thursday, July 25, 2013 6:30 PM