Loopback test with 127.0.0.1

[steve]

If you can't ping the loopback address - 127.0.0.1 - you
have a NIC card problem. Replace your NIC card and ping
yourself..it should work (unless you replaced it w/a
faulty NIC card).


>-----Original Message-----
> I can't ping any other computer's IP address on my home
>network so I tried to ping 127.0.0.1, this resulted in
>a "Request Timed Out" error. So I decided to reset the
>TCP/IP Protocol and successfully did that, but the ping
>127.0.0.1 command still gives me the "Request Timed Out"
>error. What should I do next?
>
>.
>

[Steve Winograd [MVP]]

In article >, "steve"
> wrote:
>>-----Original Message-----
>> I can't ping any other computer's IP address on my home
>>network so I tried to ping 127.0.0.1, this resulted in
>>a "Request Timed Out" error. So I decided to reset the
>>TCP/IP Protocol and successfully did that, but the ping
>>127.0.0.1 command still gives me the "Request Timed Out"
>>error. What should I do next?
>
>If you can't ping the loopback address - 127.0.0.1 - you
>have a NIC card problem. Replace your NIC card and ping
>yourself..it should work (unless you replaced it w/a
>faulty NIC card).

I don't think that we can conclude anything about the NIC card. The
127.0.0.1 IP address is internal to the TCP/IP stack, and it should be
pingable even on a computer that doesn't have a NIC card.

Failure to ping 127.0.0.1 is most likely caused by an improperly
configured firewall program.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com