pinging 127.0.0.1

SICMF · Post by **SICMF** » Tue Apr 30, 2002 3:44 pm

i pinged 127.0.0.1 and received 4 request timed out. What does this mean or better yet what do i do?

MikeyMan · Post by **MikeyMan** » Tue Apr 30, 2002 3:58 pm

If you have a NIC, it's not responding to pings. Is your setup ethernet or USB? If you have a NIC, what type is it, and is physical device and the software installed properly?

SICMF · Post by **SICMF** » Tue Apr 30, 2002 4:27 pm

i have ethernet setup with a Realtek rtl8139/810x fast ethernet nic and a belkin router.

USSZulu · Post by **USSZulu** » Tue Apr 30, 2002 4:57 pm

Im also not sure about this, but wont a software firewall instructed not to return pings also make the NIC not respond to pings?

- Me

SICMF · Post by **SICMF** » Tue Apr 30, 2002 5:03 pm

that was it i disable my norton and tried it worked great THanks guys.

SICMF · Post by **SICMF** » Mon Sep 02, 2002 4:20 am

Hey Hybrid you get that fixed yet?

Mohan-san · Post by **Mohan-san** » Mon Sep 02, 2002 5:39 am

Errrrrrrr....Is this guy talking to himself?

YARDofSTUF · Post by **YARDofSTUF** » Mon Sep 02, 2002 7:22 am

yes it seems his problem is affecting is mentallity, someone must help him... and fast!

Mohan-san · Post by **Mohan-san** » Mon Sep 02, 2002 3:11 pm

Some people on these forums actually make me feel sane...

Robot Army · Post by **Robot Army** » Mon Sep 02, 2002 8:14 pm

firewall set to block synapses?

Just kidding.. "Let he without sin, etc"

Bouncer · Post by **Bouncer** » Wed Sep 04, 2002 8:41 pm

as an FYI:

127.0.0.1 is internal loopback. You're not really pinging your ethernet port, you're pinging the ICMP port on your own ethernet stack.

The difference will help explain why Norton kills it.

It flows like this.. you initiate the ping at the application layer.

That ping transmits through the Norton proxy.

It then goes to the IP layer and comes back.

This time Nortons blocks it at the proxy point, because it sees it as a foreign ping to a local address.

Norton kills the packet.

Eventually the time out value on the ping application program expires and that triggers the ICMP echo failure message you see.

Regards,
-Bouncer-

cyberskye · Post by **cyberskye** » Thu Sep 05, 2002 1:31 am

besides what big b said - if you keep pinging yourself at 127.0.0.1 you get hairy palms and evetually go blind.

Try pinging 127.0.0.2 but make sure you buy her an expensive dinner first. Worx4me

onnyxs · Post by **onnyxs** » Sat Sep 07, 2002 5:37 pm

Disable any firewall you have going and try pinging again. If you get the same results replace your NIC card.

SICMF · Post by **SICMF** » Sat Sep 07, 2002 5:41 pm

Thankx for the replys but, This post was brought up from the basement, It was my first post. It has been resloved. Thankx.

onnyxs · Post by **onnyxs** » Sat Sep 07, 2002 5:45 pm

How did you fix problem??????????

SICMF · Post by **SICMF** » Sat Sep 07, 2002 5:51 pm

Originally posted by onnyxs
How did you fix problem??????????

I shut my firewall off. LOL. Since then i don't use a software firewall at all, Just NAT, through my router. BTW where did you pick up your copy of Linux? Website? Thinking of putting it in one of my rigs and check it out. Heard some good stuff about it.

SG Broadband Community

pinging 127.0.0.1

pinging 127.0.0.1

setup

Not sure...

you got it