Comment 5 for bug 1246236

Nobody has reported seeing this for a while. I looked at the code and it has a whole second timeout per packet. You would think that this is more than enough over a LAN segment.

I also discovered that the tftp client can set its own timeouts (http://tools.ietf.org/html/rfc2349). Given that you see it working from one client and not another, I am suspicious although there's nothing in the tcpdump that shows a timeout option getting set.

Are you still seeing this problem?