If you ask me, it's this bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=151872 But having said that, if you change the port on your switch to enable portFast, I predict you'll be all set. That's what we had to do. PXE was getting an IP just fine -- it was Kickstart/Anaconda that was choking in this regard. Regards, Steve P.S. We were plugged into a Cisco Catalyst 4000(?). > -----Original Message----- > From: kickstart-list-bounces@xxxxxxxxxx > [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of > Robinson, Andrew W. > Sent: Monday, May 23, 2005 2:35 PM > To: 'Discussion list about Kickstart' > Subject: Network kickstart weirdness > > I think I have encountered this problem before, but cannot > remember the > solution. I am trying to perform a network kickstart on a Dell PE 2650 > server. The OS is RHEL 3 U4. No matter how I try this, the > client seems not > to recognize that the kickstart file is present. It always > asks for network > information. The system successfully obtained an address > through dhcp for > the pxe-boot, but then it cannot seem to get an address to start the > installation process. I am perplexed. I do not know if this > is a network > problem, a problem with the kickstart file, or maybe a problem with > anaconda. Can anyone suggest any clues that might enable me > to figure out > what is wrong? > > Thanks! > > Andrew Robinson > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list >
