----- Original Message -----
From: Darren Eckhoff <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 17, 1999 9:25 AM
Subject: Re: [expert] Net uncreachable
> Here's the procedure I usually go though to make sure the network settings
> are correct:
>
> 1) Run the command "netstat -in" to see what interfaces are available. You
> should see the network card (ex. eth0), and the loopback (lo). From
this
> list you can also see if any packets are being received (RX-OK) and
> transmitted (TX-OK). You will also see if you are having network
errors
> and dropped packets. If your network interface does not show up on
this
> list, then the OS is not seeing it for whatever reason.
>
> 2) Run the command "ifconfig eth0" (if you interface is eth0 from the
above
> list). This will tell you a variety of information, most importantly
is
> the IP address (inet addr), broadcast (Bcast), and netmask (Mask).
MAKE
> SURE ALL OF THESE SETTINGS ARE CORRECT!!! Also, make sure you see the
> labels "UP BROADCAST RUNNING MULTICAST" in this list. If not, your
> card may be disabled. Try running "ifconfig eth0 up" in that case,
then
> check it again.
All are correct. ifconfig eth0 up was run, no joy. Tried that last night.
>
> 3) If the IP info is correct, make sure you can ping your own IP address
from
> the above list (ex. ping 192.0.0.1). You should see responses back
from
> the ping. This will tell you if the network card is responding to ping
> requests (a good hardware check). If the card does not ping, then you
> probably have a bad network card.
The nic was fine 2 days ago, nothing has changed inside the computer since.
I doubt I can get the ping of my own IP to work, but will try when I get
back to the office.
>
> 4) Run the command "netstat -r". This will show you the routing table.
> Depending on your network you may or may not have a lot of entries in
the
> table, but the one you would be most interested in is the "default"
destination.
> This should point to your router. If this is not set, or not set to
the
> proper device, you will not be able to communicate outside your
network.
> If this is correct, make sure you can ping the router. If not, you
could
> have a cable problem, or your network jack is not connected properly.
If
> you can ping the router, then the problem is not with your machine.
Call
> the network administrator!
I know it's not that problem. I cann't ping anything. I tried pinging the
linux machne on the table across the room (same network), and got network
unreachable. I cann't even ping my name server (although it is on another
network)
