Re: Can ping router!
- From: Dave Higton <davehigton@xxxxxxxxxxxxx>
- Date: Fri, 24 Aug 2007 21:11:07 +0100
In message <f3ed51174f.Brian@xxxxxxxxxxxxx>
Brian Howlett <news-spamtrap@xxxxxxxxxxxxxxxxxx> wrote:
On 23 Aug, Dave Higton wrote:
In message <bed8fc164f.Brian@xxxxxxxxxxxxx> Brian Howlett
<news-spamtrap@xxxxxxxxxxxxxxxxxx> wrote:
[snip]
I'm glad to hear you've finally got to the root of the problem. In
hindsight, there's a simple test to see if a network card is working
properly, which is to ping the card itself, using *ping 127.0.0.1
[snip]
I don't think that will tell you if the card itself is working.
127.0.0.1 is handled entirely in software - the IP stack. It doesn't
turn on a hardware loopback.
Aaargh! Of course, this only proves that the TCP/IP stack is set up
and working. I meant to say that pinging your own IP address, e.g.
192.168.0.11, will give a response which shows the NIC is working (or
not...)
No, that doesn't do anything different from 127.0.0.1 - again,
it's all handled in the IP stack.
Dave
.
- References:
- Can ping router!
- From: David
- Re: Can ping router!
- From: Brian Howlett
- Re: Can ping router!
- From: Dave Higton
- Re: Can ping router!
- From: Brian Howlett
- Can ping router!
- Prev by Date: Re: ShareFS - failures
- Next by Date: Re: ShareFS - failures
- Previous by thread: Re: Can ping router!
- Next by thread: ShareFS - failures
- Index(es):
Relevant Pages
|
|