TFTP timing out
Iíve just installed DRBL on a Test Server, with one client. When I boot the client it finds the DHCP and gets assigned itís IP, but then it cannot connect to the tftp:
PXE-32:TFTP open timeout
So Iíve got a few questions about tracking down the culprit:
1. The initial boot up text screen that shows the client obtaining its IP tells me the DHCP ID and GATEWAY ID point to eth0 on the server (eth1 is the one to the WAN). Should the Gateway be the same id as the DCHP id?
2. Should I be able to see the tftp on the Server when I type Ďnetstat Ėuí?
3. In the syslog I see:
Feb 25 12:29:33 DRBLServer dhcpd: DHCPREQUEST for 192.168.2.10 (192.168.2.1) from 00:13:d3:e9:88:04 via eth0
Feb 25 12:29:33 DRBLServer dhcpd: DHCPACK on 192.168.2.10 to 00:13:d3:e9:88:04 via eth0
Feb 25 12:29:33 DRBLServer dhcpd: Client 0:13:d3:e9:88:4 requests 1:2:3:5:6:b:c:d:f:10:11:12:2b:36:3c:43:80:81:82:83 :84:85:86:87 - PXEClient:Arch:00000:UNDI:002001 - no dhcp-client-id
Feb 25 12:29:33 DRBLServer dhcpd: DHCPDISCOVER from 00:13:d3:e9:88:04 via eth0
Feb 25 12:29:33 DRBLServer dhcpd: DHCPOFFER on 192.168.2.10 to 00:13:d3:e9:88:04 via eth0
4. The inetd.conf file contains:
tftp dgram udp wait root /usr/sbin/in.tftpd /usr/sbin/in.tftpd -s /tftpboot/nbi_img
but /tftpboot/nbi_img does not exist. Has someone gone wrong with the drblpush?
Any help would be greatly appreciated.
I don't know this information would suit for you or not.
because I don't know what's meaning about " DRBL"
usually : dhcpd service must define tftp server ip address. and define which file would client download.
exmaple: /etc/dhcpd.conf include following options.
next-server 192.168.0.254; <--- tftp server ip address
filename="pxelinux.0"; <-- client download filename and this file would be place /tftpboot
try to modify your tftpd config file
/usr/sbin/in.tftpd -v -t -s /tftpboot <-- define root directory that all.