9 replies to this topic

[spsu]

Hello. Brand new install of server 2008 (x64). Pulled down latest version of tftpd32-service-edition.329 and installed. I have turned on logging and changed the tftp directory. The service runs for a few hours (happily passing out files) and then it just crashes. It will restart just fine, but eventually it crashes again, usually while transferring files.

Any thoughts?

thank you!

[Brito]

Yes, could be a bug while emulating 32 bit exe's at "WindowsOnWindows".

I would recommend asking the author for a x64 version in case no better solution is found to see if this bug goes away or try with XYNTservice to run the non-service version.

Don't know if there any x64 version of XYNTservice but it shouldn't hurt to try anyways to compare results.

What do you think?

[isthisuniqueenough]

That is unlikely, as I am running a 32 bit version of 2k8 and exactly the same thing is happening.

[Harry Q Bovik]

We're having the same problem in Win2000 Pro and WinXP Pro. For us it seems to be correlated with certain machines trying to PUT files, or perhaps with multiple machines trying to PUT files at nearly the same time. Does anyone know if there's an older version that doesn't have this problem?

[Leandro Paulin]

Hello,

I’ve being using TFTP32 (DHCP + TFTP server) for a while and it’s working great for PXE boot.

Now, I’m having a problem similar to the one described by spsu.

I’m using Windows Server 2008 Std x32 and I’m tying a different network structure (it’s still on a lab environment until now…) where I must use Windows DHCP Service + TFTP32 TFTP Server. Both are running in the same computer.

I’ve installed tftpd32-service-edition.329.

I’ve set the Windows DHCP options:
66 (Boot Server Host Name) = MyServerName
67 (Boot File Name) = pxelinux.0

Sometime this structure works just fine, but many times the tftp32 service just crashes.
Windows shows some information (maybe it’s useful…):

Faulting application tftpd32_svc.exe
version 3.29.0.0
time stamp 0x4938467f
faulting module tftpd32_svc.exe
version 3.29.0.0
time stamp 0x4938467f
exception code 0x40000015
fault offset 0x0000c284
process id 0x6b0
application start time 0x01c983081b7d361c

I’ve noticed that the application crashes when a client computer tries to access the server.

I’ve tried to use Windows Server 2003 and the problem still happens.

Does anyone knows how to fix it? Or what can I do to use Windows DHCP + TFTP32 TFTP?

Thanks for any help,

[Harry Q Bovik]

I’ve noticed that the application crashes when a client computer tries to access the server.

We switched to using TFTP32 as an application (minimized, in system tray) rather than as a service, and the crashes went away. Guess the service version isn't quite as stable as the original app. Don't know if that's useable for you, though.

[Leandro Paulin]

Hi,

For the app version to work there must have a logged user in the computer. As the computer is a server I can’t leave a user logged in all the time.

But I think I will try the app version just to check if the problem goes away.

Thanks,

[Alfred E]

Having the same issue with Server 2003:

Faulting application tftpd32_svc.exe, version 3.29.0.0, faulting module
tftpd32_svc.exe, version 3.29.0.0, fault address 0x0000c284.

Switched back to ver 3.27 to see if that helps.

[Leandro Paulin]

Hello,

Now I'm using the 3.28 service version and it didn't crash anymore.
So I'll stay with this version.

[andriusst]

Hi,

I've been using tftpd32 v3.26 for a while and decided to update. Tried 3.27, 3.28, 3.29 and v3.31 (which somehow turned out to be v3.32) but had random glitches and crashes and also seem to be slower when it comes to sending many small files (ie BartPE LAN boot). I'm sure this will improve with further releases so for the time being I'd suggest falling back to v3.26 if you can get hold of one (author seems to have suppressed it for some reason).

Regards,
Andrius