Dear Tru64 people,
I now believe I know what was happening with my tftp problem. We use TCP
wrappers at this site, so inetd was configured to invoke tftpd via
tcpd. So situation was:
(1) Name server is under siege from a rogue PC so is responding
sluggishly.
(2) tftp request comes in and is passed to tcpd which does a DNS lookup,
which may take several seconds.
(3) tftpd gets called and starts processing the request
(4) By this time tftp client has timed out so tftpd fails to read the
socket and produces the message
tftpd: read: Connection refused
I can't prove this theory without risking further unpleasantness, but
everything seems to fit. So I have changed inetd.conf to call tftpd
directly.
Bob Vickers
--
==============================================================
Bob Vickers R.Vickers_at_dcs.rhbnc.ac.uk
Dept of Computer Science, Royal Holloway, University of London
WWW: http://www.cs.rhbnc.ac.uk/home/bobv
Phone: +44 1784 443691
Received on Wed Dec 15 1999 - 10:23:57 NZDT