[ ... ] >> Is there anything else I must do to get rid of the packet filters? Or >> could the DHCP failure have a different cause? > It turns out that the host doesn't get the address properly when booting > with the network installation CD (no, I wasn't going to re-install, I > just wanted to test a different DHCP client. Really. I'm not a Windows > user, after all), which I think rules out any client config problems. > > In other words, there must be a problem with the hardware, the server, > or the routing on the network, but what might cause this kind of > behaviour? Is there any way a broken network card or similar could give > results like this? (I'll try replacing some of the hardware tomorrow, I > guess.) > > Note that I've also tried removing the host's "fixed-address" entry from > the server config, so that an IP-address would be assigned from the > dynamic pool, but I got exactly the same result when I did. I've now tested a bit more, and it turns out that everything works just fine if the host is connected to our other switch (we have two "main" ones that are linked together.) In other words, it looks like the DHCP response is lost somehow in or between the switches. I'm pretty sure that the switch is the problem, and not the cables etc. as I've swapped around everything a lot. Also, if I move the connection back after the network is started, all communication with other hosts appear to work just fine, and 'ping -f' to the DHCP server reports 0% packet loss, so it's just the DHCP response that goes astray; everything else is transferred correctly, as far as I can tell.
Can anyone explain this? - Toralf _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
