Re: TFTP Open Timeout

[Kevin Landreth <kevin@xxxxxxxxxxxxxx>]

With your logs, I see that the actual requests are getting to the server. Is 
TFTP configured to be in a chroot?  Is the filename option in dhcpd.conf take 
this into account?  It's like its requesting pxelinux.0 but not finding it.

I did have a similar issue as chip, but it was after the RHE kernel was booting 
and it loaded the modules for the NIC.

I have a very similiar setup using all native RHEL
##########################################
[root@pxe ~]# cat /etc/redhat-release
Red Hat Enterprise Linux ES release 4 (Nahant Update 2)
[root@pxe ~]# rpm -q tftp-server tftp
tftp-server-0.39-1
tftp-0.39-1

dhcpd.conf
#########################################
deny unknown-clients;
not authoritative;
ddns-update-style ad-hoc;

option domain-name              "redhat.ev1servers.net";
option domain-name-servers      192.168.0.9, 192.168.0.10;
option subnet-mask              255.255.255.0;

allow bootp;
allow booting;

option ip-forwarding    false;  # No IP forwarding
option mask-supplier    false;  # Don't respond to ICMP Mask req

subnet 192.168.1.0 netmask 255.255.255.0 {
  option routers        192.168.1.1;
  option domain-name-servers 192.168.1.1;
}

group {
  next-server 192.168.1.1;              # name of the TFTP server
 filename "/rhel4_u2/pxe/pxelinux.bin";      # name of the bootloader


host pxe_bootp6 { hardware ethernet 00:c0:a8:fd:47:d5; fixed-address 192.168.1.6; }

- Kevin L.

Elizabeth.Brosch@xxxxxxxxxxx wrote:
> Thanks for the suggestion Chip but this didn't make any difference.
>
> I see traffic between my dhcpd/Kickstart server and client by displaying
> the output from tcpdump.
>
> I can't seem to get around this issue.  It appears it is some sort of
> timeout either with dhcp or tftp or possibly both.  
>
> Like I stated earlier, I have this new subnet that I am attempting to
> Kickstart with no luck.
>
> Thanks anyway.
>
>
> -----Original Message-----
> From: kickstart-list-bounces@xxxxxxxxxx
> [mailto:kickstart-list-bounces@xxxxxxxxxx]On Behalf Of Shabazian, Chip
> Sent: Tuesday, March 07, 2006 1:22 PM
> To: kevin@xxxxxxxxxxxxxx; Discussion list about Kickstart
> Subject: RE: TFTP Open Timeout
>
>
> We have seen this issue on some switches due to the time it takes for
> the NIC to negotiate.  What version are you using, and is portfast
> turned on at the switch?
>
> You can force the speed and duplex by appending the following to the
> kernel boot parameters:
>
> ksdevice=eth0 eth0_ethtool="autoneg=off speed=100 duplex=full" 
>
> Adjust as appropriate.
>
> -----Original Message-----
> From: kickstart-list-bounces@xxxxxxxxxx
> [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Kevin Landreth
> Sent: Tuesday, March 07, 2006 9:10 AM
> To: Discussion list about Kickstart
> Subject: Re: TFTP Open Timeout
>
> TFTP uses UDP, so my first assumption would be a firewall, due to the
> timeout 
> error.  However, I just noticed when you do a getent services tftp it
> reports 
> 69/tcp, which is wrong, its 69/udp
>
> - Kevin L.
>
> Elizabeth.Brosch@xxxxxxxxxxx wrote:
>
> > I am having problems with TFTP.  I receive PXE-E32: TFTP open timeout.
> >
> >
> >
> > I see the DHCP server issues
> >
> > DHCPDISCOVER
> >
> > then
> >
> > DHCPOFFER
> >
> > then
> >
> > DHCPREQUEST
> >
> > then
> >
> > DHCPACK
> >
> >
> >
> > Then on the client, you see TFTP attempting to start but it dies with 
> > timeout.
> >
> >
> >
> > I have been doing this for quite a while with no issues.  The only 
> > difference with my configuration now is we have a new subnet.  I had 
> > issues with DHCP but worked through it when I found the correct 
> > configuration for dhcpd.conf. 
> >
> >
> >
> > But now I get TFTP timeout.
> >
> >
> >
> > Has anyone encountered this that could share some information with me?
> >
> >
> >
> > Thanks in advance.
> >
> >
> >
> >
> >
> > Liz Brosch
> >
> > TSH System Services
> >
> > Philadelphia, PA  19104
> >
> > office:  (215) 386-0100 x1144
> >
> > cell:     (267) 784-9166
>
> ------------------------------------------------------------------------
>
> > _______________________________________________
> > Kickstart-list mailing list
> > Kickstart-list@xxxxxxxxxx
> > https://www.redhat.com/mailman/listinfo/kickstart-list
>
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/kickstart-list
>
> _______________________________________________
> Kickstart-list mailing list
> Kickstart-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/kickstart-list

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature