On Fri, 2006-02-03 at 09:16 +0000, Peter Robinson wrote: > On 2/3/06, Nigel Metheringham <nigel.metheringham@xxxxxxxxxxxxxxxxxxxxxx> wrote: > > On Fri, 2006-02-03 at 13:08 +1300, Michael J Knox wrote: > > > I have a 82573E onboard NIC that refuses to obtain a DHCP IP. If its > > > statically asigned, I am ok. > > > > Try getting the port you are connected to set to (say) 100 MB FD with no > > autonegotiation, and see if that works better. Some network > > switches/NIC combos seem to take for ever to negotiate the link. Quite > > whose fault this is I don't know, although one network equipment > > manufacturer seems to be always involved. > > The higher end ones take ages to negotiate because they try and neg > Spanning Tree Protocol first so the port goes through a blocking, > discovery and then is finally into the forwarding stage. This normally > doesn't cause a problem with newer NICs but it use to be very painful > on older NICs with Netware as the netware drivers would time out. > > Not sure if this would be an issue but one other thing to look at is > to make sure your not running and extremely tight custom firewall that > blocks the dhcp response packets. Also does it work if you temporarily > set a static IP. > > Pete Is 12 hours long enough? I reboot into the XP partition and the link is up straight away with an IP address. Likewise with the debian etch install on a different box using the same motherboard. Michael -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
