Using XP. I can ping other computers on my network, can ping external sites fine.

I have no firewall (and disabled xp's firewall). I have tried re-insalling nic. flushed dns. did "route -f" to flush my routing table of all gateway entries. In ICMP I have "allow incoming echo request" checked.

I have tried connecting my comp. directly to my cable modem (thinkig it was a prob with my router), I can ping the cable modem, but still cannot ping myself. Oh yea, i can ping localhost. I do have a webserver running, and it serves pages fine when I put in my ip.

I have a feelign its something wrong with my windows routing table - anyone run into this problem before? and how the f*ck do i fix it.

1/29/2006 5:36:53 PM

you may have inadvertantly removed your loopback interface

http://support.microsoft.com/default.aspx?scid=kb;en-us;839013

1/29/2006 5:57:20 PM

hmm good idea, but that didnt work. It added another adapter and gave it a 169.. ip like the MSFT support page claimed.
Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.25.129
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

I use DHCP - does this look right? I've never heard of having another adapter just for loopback, so not sure what it should look like. thx in advance scud.

at this point im thinking spyware, have not found anything yet.

[Edited on January 29, 2006 at 6:15 PM. Reason : spy]

1/29/2006 6:05:27 PM

eh yeah that may have been wrong article....provides an explicit virtual loopback for testing purposes.

A localhost ping shouldn't be broadcast on the network...a properly functioning tcp/ip stack should capture that ICMP message and route it to the loopback device rather than the NIC device. So I doubt it has anything to do with ICMP.

Pritn your routing tables and sohw them here.

1/29/2006 6:19:45 PM

I am back on my router - hence the 192 ips...

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x3 ...00 13 20 58 de fc ...... Intel(R) PRO/1000 PM Network Connection - Packet
Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.129 192.168.0.140 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.140 192.168.0.140 20
192.168.0.140 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.140 192.168.0.140 20
224.0.0.0 240.0.0.0 192.168.0.140 192.168.0.140 20
255.255.255.255 255.255.255.255 192.168.0.140 192.168.0.140 1
Default Gateway: 192.168.0.129
===========================================================================
Persistent Routes:
None

My ip is 192.168.0.140...

[Edited on January 29, 2006 at 6:29 PM. Reason : myip]

1/29/2006 6:25:40 PM

if you want to ping yourself, ping 127.0.0.1, it's going to be 0ms every time. if you want to ping it from some place else, goto dnsstuff.com

1/29/2006 7:23:02 PM

wish it was that easy. pings to my 192 (lan ip) timeout.

1/30/2006 9:43:48 AM

can you do a port scan? also, are you forwarding icmp requests from the router to your computer?

1/30/2006 10:29:37 AM

I can try a port scan -what will that give me tho? tell me if spyware/trojan is connected to one of my ports?

Dont think its a problem with my router fwding ICMP because I can ping other computers on my network just fine... I will double check tho.

1/30/2006 10:51:32 AM

That's some weird shit.

Can other PCs ping you?

1/30/2006 11:00:54 AM

the port scan will tell you if it's just pings thats its dropping of it's not letting you probe ports. do an nmap P0 scan and see if you see the webserver and whatever else is listening.

1/30/2006 11:07:52 AM

yea no kiddign, its really pissing me off.

No other computers cant ping me. i like to remote destop to this unpingable computer from my laptop downstairs - one day it just stopped working, and thats when i fig'd out i couldnt ping the mofo.

1/30/2006 11:08:07 AM

If pinging 127.0.0.1 doesn't work, it almost points to a problem in the protocol stack or to some other, obscure XP security setting.

Any other software installed that can interfere with network traffic such as Norton Internet Security?

Cisco VPN client? I seem to remember a bug where it would cause similar problems even if it wasn't running at the time.

1/30/2006 11:21:31 AM

I can ping localhost (127.0.0.1). Only other security software is windows spyware beta. I have windows firewall disabled.

I do have an ATT VPN client. I have had it installed for almost a year, computer has always pinged fine with it on there. I guess I could try to remove my vpn client and see what happens. My feeling though is, like you say, is that its some obscure xp setting I do not know about.

smoothcrim - Makes sense, thx. I'm at work now so cant try that out,ill try it tonight.

[Edited on January 30, 2006 at 11:38 AM. Reason : smoothcrim]

1/30/2006 11:35:14 AM

here is results from my P0 scan:
C:\Documents and Settings\ryan>nmap -v -P0 192.168.0.140

Starting Nmap 3.9999 ( http://www.insecure.org/nmap ) at 2006-01-31 17:14 Centra
l Standard Time
DNS resolution of 1 IPs took 0.03s. Mode: Async [#: 2, OK: 0, NX: 1, DR: 0, SF:
0, TR: 1, CN: 0]
Skipping SYN Stealth Scan against 192.168.0.140 because Windows does not support
scanning your own machine (localhost) this way.
Host 192.168.0.140 appears to be up ... good.
All 0 scanned ports on 192.168.0.140 are: unknown

Nmap finished: 1 IP address (1 host up) scanned in 0.079 seconds
Raw packets sent: 0 (0B) | Rcvd: 0 (0B)

Doesnt see my http sever up at port 81, although it is indeed up and working on 192.168.0.140:81.

Why does it look like i am not scanning any ports? I have tried a bunch of params, like -p 1-65535, with no success...always '0 scanned ports'

[Edited on January 31, 2006 at 6:24 PM. Reason : trying nmap 192.168.0.140 -v -sT -P0]

1/31/2006 6:20:37 PM

This is better - still doesnt see my http server on 81...any ideas?

C:\Documents and Settings\ryan> nmap 192.168.0.140 -v -sT

Starting Nmap 3.9999 ( http://www.insecure.org/nmap ) at 2006-01-31 17:22 Centra
l Standard Time
DNS resolution of 1 IPs took 0.02s. Mode: Async [#: 2, OK: 0, NX: 1, DR: 0, SF:
0, TR: 1, CN: 0]
Initiating Connect() Scan against 192.168.0.140 [1672 ports] at 17:22
Discovered open port 3389/tcp on 192.168.0.140
^C
C:\Documents and Settings\ryan> nmap 192.168.0.140 -v -sT -P0

Starting Nmap 3.9999 ( http://www.insecure.org/nmap ) at 2006-01-31 17:23 Centra
l Standard Time
DNS resolution of 1 IPs took 0.01s. Mode: Async [#: 2, OK: 0, NX: 1, DR: 0, SF:
0, TR: 1, CN: 0]
Initiating Connect() Scan against 192.168.0.140 [1672 ports] at 17:23
Discovered open port 3389/tcp on 192.168.0.140
Discovered open port 445/tcp on 192.168.0.140
Connect() Scan Timing: About 21.98% done; ETC: 17:25 (0:01:47 remaining)
Discovered open port 3306/tcp on 192.168.0.140
Discovered open port 139/tcp on 192.168.0.140
Discovered open port 135/tcp on 192.168.0.140
The Connect() Scan took 123.05s to scan 1672 total ports.
Host 192.168.0.140 appears to be up ... good.
Interesting ports on 192.168.0.140:
(The 1667 ports scanned but not shown below are in state: filtered)
PORT STATE SERVICE
135/tcp open msrpc
139/tcp open netbios-ssn
445/tcp open microsoft-ds
3306/tcp open mysql
3389/tcp open ms-term-serv

Nmap finished: 1 IP address (1 host up) scanned in 123.093 seconds

1/31/2006 6:26:19 PM

I put in a new NIC and same results. I just re-installed windows, problem fixed. FUcking ms.

2/4/2006 7:29:00 PM