It looks to me that the TFTP server is being blocked. The pc makes the request OK; the tftp server replies use this UDP port 516. Then the pc makes another request, but this time on port 2071, which is indicative that it cannot hear the reply from TFTP, and is searching. The TFTP server hears this request, attempts another connection, it now has 2 (on 33589 and 33589), and once again the pc can't hear those connections.
It is possible that UPD has been blocked, but I would expect to see an error from the pc to TFTP on the same connection (port) that instigated the message. Remember TFTP uses TCP to establish a connection, but UDP to send the file. Hope this helps, network problems can be a real pain I know, not a good way to spend the weekend. Dave -----Original Message----- From: chris bayley [mailto:[EMAIL PROTECTED] Sent: Saturday, 20 December 2003 10:50 a.m. To: [EMAIL PROTECTED] Subject: PXE boot / tftp woes I am trying to get a suit of worksations network booting LTSP via PXE/etherboot for the local school I have DHCP configured and they pick an ip ok, but something is amiss in the tftp transfer of the etherboot code I am using tftp-hpa. logs show: Dec 19 21:27:53 [in.tftpd] RRQ from 192.168.0.101 filename pxe/eb-5.0.9-eepro100.lzpxe Dec 19 21:27:53 [in.tftpd] RRQ from 192.168.0.101 filename pxe/eb-5.0.9-eepro100.lzpxe Dec 19 21:27:53 [in.tftpd] RRQ from 192.168.0.101 filename pxe/eb-5.0.9-eepro100.lzpxe etc. tcpdump shows: 10:41:25.112427 ruby.bootps > 192.168.0.101.bootpc: xid:0xc763a381 Y:192.168.0.101 S:ruby [|bootp] [tos 0x10] 10:41:25.114106 ruby.bootps > 192.168.0.101.bootpc: xid:0xc763a381 Y:192.168.0.101 S:ruby [|bootp] [tos 0x10] 10:41:25.114708 192.168.0.101.2070 > ruby.tftp: 49 RRQ "pxe/eb-5.0.9-eepro100.lzpxe" 10:41:25.117879 ruby.33589 > 192.168.0.101.2070: udp 516 (DF) 10:41:26.111075 ruby.33589 > 192.168.0.101.2070: udp 516 (DF) 10:41:28.111066 ruby.33589 > 192.168.0.101.2070: udp 516 (DF) 10:41:29.047190 192.168.0.101.2071 > ruby.tftp: 49 RRQ "pxe/eb-5.0.9-eepro100.lzpxe" 10:41:29.049351 ruby.33590 > 192.168.0.101.2071: udp 516 (DF) 10:41:30.041081 ruby.33590 > 192.168.0.101.2071: udp 516 (DF) 10:41:32.041072 ruby.33590 > 192.168.0.101.2071: udp 516 (DF) 10:41:32.111079 ruby.33589 > 192.168.0.101.2070: udp 516 (DF) 10:41:36.041062 ruby.33590 > 192.168.0.101.2071: udp 516 (DF) 10:41:36.957336 192.168.0.101.2072 > ruby.tftp: 49 RRQ "pxe/eb-5.0.9-eepro100.lzpxe" 10:41:36.959476 ruby.33591 > 192.168.0.101.2072: udp 516 (DF) The client eventually gives up and sulks in the corner. I know RRQ is a read request, what is DF ? The clients use LANDesk server agent II 0.99c which show up few troubles on google but none of the standard remidies have got me going yet. cheers, chris
