Deployment Solution

 View Only
  • 1.  PXE-E32 TFTP Open Timeout Errors

    Posted Aug 06, 2014 09:09 AM

    Background:  Our company DHCP server is in another city.  DS/NS Altiris 7.5 are on another server in my city.  DHCP has been set correctly to point to the NS but when I run a PXE boot on a machine it gives me the E32 TFTP Open Timeout error.  Checked with the person hosting the DHCP server and all settings (DHCP 66 and 67) are set correctly.

      Ran WireShark on the NS server here and it shows it is receiving a BootP request and that it is coming from the correct client machine.  So I know the PXE server is receiving the request but I still get the same TFTP Open Timeout.

    Have tried Windows TFTP from my work computer and I can get to the PXE server and GET the BStrap.0 file d/l'd to my computer

    Checked all the settings I could find on the PXE server and they seem to be correct.

    Client computers are all Dells with PXE 2.1, all on the same subnet as the PXE server.

    Could the BStrap file be corrupted?  Is it not in the correct location? and also what is it the creates the BStrap file?

     

    Thanks in advance!
     



  • 2.  RE: PXE-E32 TFTP Open Timeout Errors

    Posted Aug 08, 2014 07:05 AM

    Are you sure the NS is the correct PXE server and that the PXE services are active on the NS?  Most of the time we configure site servers for PXE, especially when crossing a WAN, to avoid having to ship the WIM over the WAN.

    Since you said you can pull the .0 file, there are a couple of other options.

    1) are these BIOS systems or UEFI?  PROBABLY doesn't matter, but it's worth asking.

    2) if you pull a system onto the same subnet as the PXE server, and pull OUT the DHCP options, does it work?  It's possible DHCP is wrong (e.g. pointing to the wrong path or... something).

     

    It's a start.  Keep us posted!



  • 3.  RE: PXE-E32 TFTP Open Timeout Errors

    Posted Aug 08, 2014 09:02 AM

    Notification server is server A in Waco, Tx.  The same server houses the Task, Package, and NBS service.

    It is on subnet .251.  The lab where I am going to be doing all the imaging and any work needing PXE is also on the .251 subnet.  Tried working this before setting up the DHCP but it was a no go.

    DHCP server is in Dallas, Tx.  Set DHCP settings correctly (have reverified they are set correctly).  Still a no go.  DHCP options 67 and 68 set to ip address of the PXE server and the path BStrap\x64\BStrap.0

    Ran WireShark on the .251 subnet from the PXE server.  Verified it was receiving a BootP request from the correct ip address of the client machine through the DHCP server.  Showed both a DHCP Offer and a DHCP ACK.

    Current location of BStrap file is:

    D:\SIM\Altiris\Altiris Agent\Agents\Deployment\SBS\Images\BStrap\x64\BStrap.0  Which is where the system created it.  Not sure if, in DHCP, I need the complete path of:
     

    SIM\Altiris\Altiris Agent\Agents\Deployment\SBS\Images\BStrap\x64\BStrap.0  or the system path of

    BStrap\x64\BStrap.0 (this is the path I used in Windows TFTP and was able to successfully GET the file)

    Computers are all Dell running Legacy mode boot not UEFI.  PXE on systems all at least PXE 2

     



  • 4.  RE: PXE-E32 TFTP Open Timeout Errors

    Posted Aug 09, 2014 12:44 PM

    Are these UEFI boxes?  Legacy mode doesn't always work - we had all sorts of problems with that before.

    Are you able to test a computer on the same subnet OR potentially pulling out DHCP configurations and using an IP Helper?  I'd like to isolate the problem (DHCP vs PXE server) but while the DHCP and PXE both have to respond, it's hard to know what's actually wrong.

    See if you can isolate the issue to the PXE server or DHCP so we can focus on the right things.



  • 5.  RE: PXE-E32 TFTP Open Timeout Errors

    Posted Aug 11, 2014 04:04 PM

    Currently the PXE server and client machines are running off the same subnet (.251.xxx).  Removed settings i9n DHCP and when booting from PXE immediately received a No BootFile name error.  WireShark testing on PXE server recieved NO BootP requests.  Installed settings back in DHCP.  No get a mac addy, client addy, dhcp server addy, WireShark on PXE server is showing a BootP request from the client machine but no BStrap file is being sent back to machine.

    Tried Same Subnet - No DHCP

            Same Subnet - DHCP settings set

            Same Subnet - DHCP settings set, IP Helper Addy added in

    Still getting same results.  Check with a friend who is using PXE server (using FOG).  Checked his settings and only difference is that I show the BStrap path as BStrap\x64\BStrap.0 while his path shows BStrap.0.

    Am going to try DHCP option 67 as just BStrap.0 and copy the file to the same subdirectory level as the BStrap directory and check if this works.

    Also tried the above settings on a machine set to UEFI rather than Legacy but still received the same results.