I tried Jims suggestion
/etc/sysconfig/network-scripts/ifcfg-eth0
# VIA Technologies, Inc. VT6102
[Rhine-II]Device=eth0BOOTPROTO=noneHWADDR=00:17:31:d4:11c1ONBOOT=yesDHCP_HOSTNAME=localhost.localdomainNM_CONTROLLED=no
(I changed this
option)TYPE=EthernetUSECTL=noPEERDNS=yesIPV6INIT=noIPADDR=xxx.xxx.xxx.66NETMASK=255.255.255.224GATEWAY=xxx.xxx.xxx.65
DNS1=68.105.28.12 (I added these two DNS fields)
DNS2=68.105.29.12
Then I applied this
sudo /sbin/service network restart
When I restarted the network it saved all the information
but I still was not able to connect. I am going to try again here in a bit
Thanks,
Michael> Date: Mon, 1 Dec 2008 23:29:11 -0800> From: [EMAIL PROTECTED]> To:
kplug-newbie@kernel-panic.org> Subject: Re: Connecting with CentOS 5.2> >
Michael Lynch wrote:> > > > I jumped the gun a little and reloaded FED 9 (This
used to work Perfect on this machine)> > > > This provided me with some
interesting info> > > > When I loaded FED 9 back up I had the same problem no
connectivity> > So I tried the machine with a dynamic IP and of course it
worked> > So I took it back into the garage and tried a static IP with no
success> > What is interesting about this run is that as soon as I booted the
machine> > the security update alert popped up. So I tried to download the
security updates> > and an alert came up and said there was no network
connection> > This installation also would not hold any DNS information even
though I> > would save the IP information and activate the hardware> > once I
would reboot the machine any DNS settings would be lost> > > > I still
performed the test that Jim suggested and here are the results> > > > > >
/etc/resolv.conf> > > > #No nameservers found; try putting DNS Servers into
your> > #ifcg files in /etc/sysconfig/network-scripts like so:> > #> >
#DNS1=xxx.xxx.xxx.xxx> > #DNS2=xxx.xxx.xxx.xxx> > #SEARCH=lab.foo.com
bar.foo.com> > > > > > /etc/sysconfig/network-scripts/ifcfg-eth0> > > > # VIA
Technologies, Inc. VT6102 [Rhine-II]> > Device=eth0> > BOOTPROTO=none> >
HWADDR=00:17:31:d4:11c1> > ONBOOT=yes> > DHCP_HOSTNAME=localhost.localdomain> >
NM_CONTROLLED=yes> > TYPE=Ethernet> > USECTL=no> > PEERDNS=yes> > IPV6INIT=no>
> IPADDR=xxx.xxx.xxx.66> > NETMASK=255.255.255.224> > GATEWAY=xxx.xxx.xxx.65> >
> > For whatever reason this machine wont save DNS settings> > at least that is
how I interpret these results> > Any suggestions?> > There may be a problem
with static configuration under network manager.> It is _supposed_ to work, but
I am having problems getting NM to> cooperate on a F9 system. Maybe a similar
problem might have been> happening under Centos?> > If you edit (as root) and
change the NM_CONTROLLED line to say> NM_CONTROLLED=no> and then also fill in
(doublecheck) these fields> IPADDR=> NETMASK=> GATEWAY=> DNS1=> DNS2=> (no
indents or any whitespace)> with the cox-provided data> > Turning off NM should
allow the /old fashioned/ network script to work> as it always has in the
good-ole-days.> > Then try> sudo /sbin/service network restart> and see if you
can ping the nameserver (etc).> If all that works better, you probably want to
immediately confirm it> works the same after a reboot.> > Regards,> ..jim> > --
> KPLUG-Newbie@kernel-panic.org>
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie--
KPLUG-Newbie@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
