Michael Lynch wrote:
> I tried Jims suggestion
>..
> Then I applied this
> sudo /sbin/service network restart
>
> When I restarted the network it saved all the information
Perhaps you could elaborate what you mean by "it saved all the
information"? Perhaps that's your shorthand for confirming the following
stuff, but I'll do a bit of expounding anyway. :-)
My favorite diagnostic first-step is to look (and understand) the output
from these 3 commands
/sbin/ifconfig -a .. or /sbin/ifconfig eth0 (say)
/sbin/route -n
cat /etc/resolv.conf
- in the ifconfig output, the important parts are "inet addr", "mask"
and the occurrence of the flag "UP. The packet error counts are also
worth noticing.
The route output on my desktop looks like
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
> 192.168.9.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
> 0.0.0.0 192.168.9.1 0.0.0.0 UG 0 0 0 eth0
-the 192.168.122.0 ("vibr0") and the 169.254.0.0 lines are of no
interest. I just automatically ignore "vibr0" lines and 169.254
addresses .. pretend they aren't there.
-the 192.168.9.0 says my eth0-interface connects to my LAN
-the 0.0.0.0 says there is a "default route" to the rest of the world
(addresses outside my LAN) which can be accessed via a router at address
192.168.9.1 (which must be a valid IP in the LAN address space)
The output from cat /etc/resolv.conf should have at least one nameserver
line (max 3).
- if you don't have a nameserver, you cannot "resolve" names to IP
addresses.
---end of "first-step" exposition ("expoundation"?)---
> but I still was not able to connect. I am going to try again here in a bit
So, you might be a bit more precise about the meaning of "not able to
connect", too.
May I presume that pinging the nameserver did the same as the earlier
report (ie, some responses, and some lost pings) -- or is there some
different symptom?
The reason for pinging the nameserver is that it is a much simpler
(lower-level) test than trying to get a browser connected to some
website, for example.
If pinging the NS fails, then pinging the gateway (your X.X.X.65) would
be an even simpler test. If that fails, it really narrows things down!
Regards,
..jim
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
