7 replies to this topic

[Tecnet Solutions]

I have installed TFTPD32 V3.25 on a Microsoft Small Business Server R2 server. I wish to use TFTPD to provide the PING imaging software to PXE capable clients.

When a client computer boots using F12 I can see the TFTPD log allocate an IP address to the client and the client computer also displays the IP address. However no boot file is downloaded to the client (pxelinux.0) and the client receives a TFTP File Not Found message. The TFTPD32 server log displays a "File <pxelinux.0> : error 2 in system call CreateFile The system cannot find the file specified. [23/05 08:42:03.171] message.

I configured the TFTPD server per the PING website doco (http://ping.windowsd...g/download.html).

Can anyone shed light on why the TFTPD server is unable to find the specified boot file?

Attached Files

•  TFTPD32_Config.doc   49KB   2419 downloads

[d4vr0s]

Is the pxelinux.0 in the tftp root?

[Tecnet Solutions]

thanks for the info d4vr0s, as soon as the file was placed in the TFTPD32 directory it worked fine. I presume this therefore means the PING doco is incorrect as it advises the pxe files to be placed in a separate directory. Thanks again for the tip.

[d4vr0s]

Glad to be of help

[Anaxagoras1986]

I am having a similar problem. I tried putting the pxelinux.0 in the root of the TFTPD32 server directory but my clinet is still complaining about how it cannot find a large number of files. Does anyone have any siggestions?

Attached Files

•  Log.txt   5.1KB   1374 downloads

[tubalcain]

I noticed this to. I think that is the reason that I cannot connect to the SMB share, has anyone found a solution?

[tubalcain]

Ok, Happy New Year. I finally figured everything out and those errors in TFTPD32 are normal. I successfully installed Windows XP SP3 via PXE on a Dell Latitude C400 (no floppy or cd drive) using the steps outlined in http://www.lockstock...e-boot-windows/. If you previously screwed around too much with XP network and file permissions, I suggest you do a fresh install of XP on your host machine as a fresh starting point. I do think that the main thing to get right is the "IP pool starting address" in TFTPD32 which is never actually explained correctly in various tutorials. Example my "IP pool starting address" is 192.168.1.6, my "Server interfaces" IP is 192.168.1.4, I had set the size of pool to 10. DNS and subnet mask settings are self explanatory. After getting that right TFTPD32 on my host machine communicated flawlessly with my laptop and installed pretty fast too. The errors in TFTPD32 are pretty much the same, what they mean I have the slightest clue but that was the only thing I could think of that was holding me back. I hope this may be able to help someone in the future who is having problems.

[smokeAR]

I'm having a similar problem. I'm trying to repair a Cisco wireless access point that messed up during an update. The only way to repair this is through Tftp32. I read and did exactly as the guide says. I'm running Windows 2000 Server with a linksys switch. The file is in the same folder as tftp32 and it's shared. I see the dhcp hand out an ip address the I get the error 2 ... Has anyone worked with these Cisco devices before? Any help would be greatly appreciated