In comp.os.linux.networking Google Mike <(E-Mail Removed)>:
> I have resolved a problem on a locked up Ubuntu 5.04 network control
> panel. If you are experiencing this problem in Ubuntu or any form of
> GNOME-based Linux, you might want to consider this. This can also, to
> some small degree, show you how to manipulate your network control
> panel settings without the GUI.
> In my case, I determined that the problem was that it was trying to
> reach a DNS server and will wait there indefinitely if the one that
> your DHCP server uses is not available. In our environment, our DHCP
> server points to a DNS server that's no longer functional. Instead, we
> must put static addresses (for now) pointing to our DNS servers:
Wouldn't it be a better idea to get the one responsible for the
DHCP server to fix the broken setup?
Anyway you can configure dhcpclient not to overwrite resolv.conf
(PEERDNS=no) on RH and alike n ifcg-<device> or you need to make
your changes on every reboot.
[..]
--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo
(E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 152: My pony-tail hit the on/off switch on the
power strip.