WinPE 2.0 and PXELinux Problem

[g3neration]

My current problem is as follows:

I've setup a test environment in VMware Workstation 6. This consists of two VM's, a Vista x64 box and the PXE client. On the Vista box, I've installed WAIK (WinPE2.0), MagikDHCP, and TFTPD32 with the TFTPD32 acting purely as a TFTP server. I have the DHCP server point to pxelinux.0 in c:\tftpboot. The relevant winpe files are in c:\tftpboot\boot, with bootmgr.exe in the root folder ( c:\tftpboot ). My pxelinux.cfg/default file is pretty simple and it is as follows:

LABEL linux

kernel kernel/vmlinuz

append vga=normal initrd=initrd/initrd.gz --

Label win

kernel boot/pxeboot.0

PROMPT 1

TIMEOUT 0

My problem is that after pxeboot.0 is loaded, it requests from the TFTP server bootmgr.exe but the TFTP server does not respond back. I've run a packet trace with wireshark to verify this. At first I thought it may be one of the options regarding TFTPD32, ie. PXE compatibility, Translate Unix file names, etc. But after playing around with all the combinations, its still unsuccesful. The packet trace shows that its asking for:

533 520.398712 192.168.80.254 0.0.0.0 TFTP Read Request, File: bootmgr.exe, Transfer type: octet, blksize=1456

I cant seem to narrow down this problem. Pxeboot.0 is transferred fine as shown from the packet capture.

429 517.599844 192.168.80.254 192.168.80.100 TFTP Read Request, File: boot/pxeboot.0, Transfer type: octet, tsize=0, blksize=1408

430 517.985751 192.168.80.100 192.168.80.254 TFTP Option Acknowledgement, tsize=25068

Any help would be great.

[zorphnog]

Do you have the base directory for tftpd32 set to C:\tftpboot?

[g3neration]

Do you have the base directory for tftpd32 set to C:\tftpboot?

Yep. Nothing seems to be working. At first I thought it might be a TFTPD32 issue as the DHCP server for it was giving me problems. Therefore I also installed WinAgents TFTP server but still the same issue.

[Jazkal]

Try putting bootmgr.exe in both folder:

c:\tftpboot and c:\tftpboot\boot

Our linux setup required us to do that. Can't tell you why, I'm the Windows guy, not linux.