"TFTP...." followed by "PXE-E32: TFTP open timeout"
When being started, the PXE client comes up with the PXE copyright message and completes the DHCP phase, but then displays:
After a while, the following error message is displayed:
PXE-E32: TFTP open timeout
Depending on the PXE client's system setup boot device list configuration, the PC then either stops or tries to boot from the next boot device in the system setup boot device list.
The "PXE-E32" error indicates that the PXE did not get a reply from the TFTP server when sending a request to download its boot file. Possible causes for this problem are:
- There is no TFTP server
- The TFTP server is not running
- TFTP and DHCP/BOOTP services are running on different machines, but the next-server (066) option was not specified
Make sure that a TFTP server is set up and running. When the TFTP service is running on a different machine than the DHCP or BOOTP service, you need to add option 066 (next-server) to the DHCP/BOOTP server configuration, and set this option's value to the IP address or "resolvable hostname" of the TFTP server. When option 066 (next-server) is not defined, the PXE client assumes that the TFTP service is running on the same machine from which it received its DHCP/BOOTP configuration information.
Also have you tried the other suggestions posted in the forums on this alread?
I dont think we have a tftp server. There is not a tftp service running on the pxe rep that I am looking at. Is there just a way to disable it looking for one?
Your PXE Rep is the TFTP server, it will stream the file to the device, this is the LANDesk PXe service.
When it shows Boot Server IP, record the IP, then validate that the IP belongs to the LANDesk PXE server (in case its something else weird like having multiple PXE reps on the same subnet).
Then check the MTU timeout and other suggestions in the forum. I'm literally working on the same issue right now out at one of our sites.
I checked the ip address. It is booting from the right pxe server. We get this error at all of our sites. We have 8 pxe reps and sites I believe. It hasn't been too big of a deal, because it will continue on an let us choose our image to use and works just fine. I'm just trying to speed up the process. I checked the MTU timeout in the registry and there is not a setting there. From what the forum says, if there isn't a setting there, then it is set as default to 1500.
Is it the PXE boot that is really slow or the imaging?
I am not sure, but I was wondering if it continues, maybe its failing over to another PXE server???
When it loads the image, does it show the same IP as the boot IP?
If the imaging itself is just slow that can be tackled many different ways depending on how your imaging.
It's not that it is really that slow. It adds maybe 10 seconds to the load up of pxe. I am just tired of seeing the stupid PXE-E32: TFTP open timeout error. I am trying to get this imaging stuff to work the best it can with no errors.
The acctual imaging gets pretty slow sometimes. We have to often reboot the main server because imaging will get to where it takes over an hour to drop down an image compaired to around 30 minutes normally.
We actually use our PXE reps as stand alone preferred servers. So the PXE rep will also have a UNC share on it.
We then use DFS to manage what IP subnets will pull from what location.
This allows us to use a single UNC share path in our scripts such as \\ourdomain\LANDeskImages\xzy and DFS translates that based upon IP subnet assignement to go to whatever UNC path we specify.
SInce the Images are local to that subnet and site, we cut down on network bandwidth to download the image files.
That is how ours are set up as well. I really just want to get rid of this error..its frustrating me lol. That and I fear that my bosses are wanting to dump landesk so I am doing everything I can to make it work better so they keep it.
You don't write, which LANDesk version you use... in older versions 8.x, you've to change the file startrom.0 as described here: http://community.landesk.com/support/docs/DOC-2306 to get more performance and solve some other problems.
On which OS you've installed your PXE server(s) and your core?
Which LANDesk version you use?
We use Win Server 2008 R2 on core and pxe reps. We are running Landesk 9 service pack 2.
I am new here, but if this is still unanswered for you:
When I installed the PXE rep on my preferred server I had tried this, but I noticed after the fact that when I received the "PXE-E32" error the service was not started on the server for some reason, even though whenever it had been installed in other situations that was not an issue. then as soon as I started "LANDesk(R) PXE Service" and "LANDesk(R) PXE MTFTP Service" the service and tested TFTP:
c:\>tftp $IP GET x86pc\undi\provwin\startrom.0
Transfer successful: 25676 bytes in 1 second(s), 25676 bytes/s
I actually had to specify the service to start automatically as it was set to manual. It works beautifully now.