Interesting. But would that prevent all traffic? I see the DHCP Request coming from the one laptop, and the other one is obviously up and running already. There's just never a DHCP Offer.
I'll take a look when I get a chance. On Thu, Aug 16, 2012 at 4:51 PM, Will McDonald <wmcdon...@gmail.com> wrote: > If you'd prefer to put the Cisco switch back in, check the spanning > tree config on the port the host was connected to and try switching it > to PortFast. > > > http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a00800b1500.shtml > > I've seen that cause lots of problems with DHCP where the client times > out before the switch port's fully up. > Cheers, > > Will. > > On 16 August 2012 21:32, Bai Shen <baishen.li...@gmail.com> wrote: > > Turns out it was the Cisco switch. I replaced it with a Linksys > unmanaged > > one and it came right up. > > > > > > On Thu, Aug 16, 2012 at 2:59 PM, Bai Shen <baishen.li...@gmail.com> > wrote: > >> > >> I have two Dell laptops that I'm testing Cobbler on. When I boot into > >> linux, I can get an ip from the dhcp server running on the cobbler box. > >> However, it never seems to respond to the PXE request for an ip. > >> > >> Is there something I can look at or setting to change? I'm not sure why > >> it will provide an ip under linux but not for a PXE boot. > >> > >> Thanks. > > > > > > > > _______________________________________________ > > cobbler mailing list > > cobbler@lists.fedorahosted.org > > https://lists.fedorahosted.org/mailman/listinfo/cobbler > > > _______________________________________________ > cobbler mailing list > cobbler@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/cobbler >
_______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler