self ping fails

[Guest]

XP laptop ("badcomputer") has the following symptoms:

Badcomputer CAN'T ping its own IP address
Badcomputer CAN ping 127.0.0.1
Badcomputer CAN ping the gateway IP
Badcomputer CAN ping other computers (IPs) on the network ("goodcomputers")
Goodcomputers CAN ping each other (IPs) Goodcomputers CAN'T ping Badcomputer
(IP)


Background:

Badcomputer went wrong after Norton was used to remove "6 Trojans" which
were all in PCODEC folder and all part of the same problem I suppose.

Behaviour is identical whether connected to my wireless home network or
neighbour's unsecured wireless network or via an ethernet cable or using a
plug in wireless card (although I have replaced drivers for all relevant
hardware). I get an excellent connection in all permutations, but neither IE
nor Firefox can be persuaded to use the "excellent connection".

Have run network wizard several times.

Have tried setting IP addresses manually to no avail.

Have run several regfix programmes and not found anything seriously amiss.

Have tried switchig off firewalls to no avail.

Have tried swearing at Badcomputer to no avail.

Any suggestions gratefully received.

Mike

 

[AJR]

Mike - 127.0.0.1 is "bad computer" loopback address and indicates TCP/IP ok.
You do not indicate whether or not "bad computer" functions ok within the
network or accessing the internet..
If "A" (bad computer) OK before use of "B" (Norton's) - I would suspect "B".

 

[Chuck]

XP laptop ("badcomputer") has the following symptoms:

Badcomputer CAN'T ping its own IP address
Badcomputer CAN ping 127.0.0.1
Badcomputer CAN ping the gateway IP
Badcomputer CAN ping other computers (IPs) on the network ("goodcomputers")
Goodcomputers CAN ping each other (IPs) Goodcomputers CAN'T ping Badcomputer
(IP)


Background:

Badcomputer went wrong after Norton was used to remove "6 Trojans" which
were all in PCODEC folder and all part of the same problem I suppose.

Behaviour is identical whether connected to my wireless home network or
neighbour's unsecured wireless network or via an ethernet cable or using a
plug in wireless card (although I have replaced drivers for all relevant
hardware). I get an excellent connection in all permutations, but neither IE
nor Firefox can be persuaded to use the "excellent connection".

Have run network wizard several times.

Have tried setting IP addresses manually to no avail.

Have run several regfix programmes and not found anything seriously amiss.

Have tried switchig off firewalls to no avail.

Have tried swearing at Badcomputer to no avail.

Any suggestions gratefully received.

Mike

Mike,

Eliminating the obvious first, swearing at the computer won't work. I know from
experience. ;(

Asymmetrical ping would generally be a personal firewall problem - and
"switching off" (which?) firewalls isn't always productive.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

Having happened after you removed malware ("6 Trojans"), I'd bet LSP / Winsock
corruption though.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

 

[Guest]

Dear Chuck

Thanks very much for the response. Unfortunately though, I have followed all
the steps, at the link you kindly provided, to the letter but still have
exactly the same behaviour.

Best regards

Mike

For what it's worth, winsock catalog is:


Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1004
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\rsvpsp.dll
Catalog Entry ID: 1005
Version: 6
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkipx [IPX]
Provider ID: {11058240-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1012
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 2
Protocol: 1000
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX]
Provider ID: {11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1013
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 5
Protocol: 1256
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX] [Pseudo Stream]
Provider ID: {11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1014
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 1
Protocol: 1256
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II]
Provider ID: {11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1015
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 5
Protocol: 1257
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD nwlnkspx [SPX II] [Pseudo Stream]
Provider ID: {11058241-BE47-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1016
Version: 2
Address Family: 6
Max Address Length: 16
Min Address Length: 14
Socket Type: 1
Protocol: 1257
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS [\Device\NwlnkNb]
SEQPACKET 3
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1017
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -3
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS [\Device\NwlnkNb] DATAGRAM 3
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1018
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -3
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{3BBF674C-1113-41D3-B7DF-E12A5AB9EF53}] SEQPACKET 0
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1019
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{3BBF674C-1113-41D3-B7DF-E12A5AB9EF53}] DATAGRAM 0
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1020
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2147483648
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{FB458613-4778-4C16-92F4-0450C437C848}] SEQPACKET 1
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1021
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{FB458613-4778-4C16-92F4-0450C437C848}] DATAGRAM 1
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1022
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -1
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{74046427-157B-460E-8CF1-35C9520B9896}] SEQPACKET 2
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1023
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 5
Protocol: -2
Protocol Chain Length: 1

Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{74046427-157B-460E-8CF1-35C9520B9896}] DATAGRAM 2
Provider ID: {8D5F1830-C273-11CF-95C8-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1024
Version: 2
Address Family: 17
Max Address Length: 20
Min Address Length: 20
Socket Type: 2
Protocol: -2
Protocol Chain Length: 1

Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID: {22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID: {3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness (NLA) Namespace
Provider ID: {6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0


Name Space Provider Entry
------------------------------------------------------
Description: NWLink IPX/SPX/NetBIOS Compatible
Transport Protocol
Provider ID: {E02DAAF0-7E9F-11CF-AE5A-00AA00A7112B}
Name Space: 1
Active: 1
Version: 1

 

[Guest]

Dear AJR

Thanks for the response, but I *do* 'indicate whether or not "bad computer"
functions ok within the network or accessing the internet' (see below) it
doesn't do either any more.

I suspect you are right and Norton is to blame for trashing my friend's
computer. Unfortunately, he is far from home and has no discs with him and a
rebuild is out of the question. I think he is probably stuck without a
connection until he returns to the USA. I am advising him not to re-install
Norton.

Best regards

Mike

 

[Chuck]

Dear Chuck

Thanks very much for the response. Unfortunately though, I have followed all
the steps, at the link you kindly provided, to the letter but still have
exactly the same behaviour.

Best regards

Mike

For what it's worth, winsock catalog is:

<SNIP Winsock enumeration>

Mike,

What is the actual problem? Ping makes a good diagnostic, but maybe looking at
another symptom will tell us something.

And I see IPX/SPX (NwlnkNb) in the enumeration. Do you use IPX/SPX?
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

And did you use the Cerelli registry based fix (Step 8)?

 

[Guest]

Dear Chuck

you aked: "What is the actual problem?" Well the real problem is that I
can't connect to the internet using IE or Firefox and I can't connect to
shared resources on my network (although I don't actually need to share any
resources, but I take this as a sign that something is wrong). Actually, I
get an "excellent" connection which ever way I connect and which ever network
I connect to, but the computer refuses to use that connection to communicate
with the outside world.

As for IPX/SPX, I've unchecked this and all other superfluous protocols
since I last posted (using your blog as a guide) but this has not improved
matters in any way.

I did try step 8 (and all the other steps you recommended) but none of them
helped. I'm completely mystified.

Regards

Mike

 

[Chuck]

Dear Chuck

you aked: "What is the actual problem?" Well the real problem is that I
can't connect to the internet using IE or Firefox and I can't connect to
shared resources on my network (although I don't actually need to share any
resources, but I take this as a sign that something is wrong). Actually, I
get an "excellent" connection which ever way I connect and which ever network
I connect to, but the computer refuses to use that connection to communicate
with the outside world.

As for IPX/SPX, I've unchecked this and all other superfluous protocols
since I last posted (using your blog as a guide) but this has not improved
matters in any way.

I did try step 8 (and all the other steps you recommended) but none of them
helped. I'm completely mystified.

Regards

Mike

Mike,

Did you uncheck IPX/SPX? Or actually un install it? Before, or after, your
problems started? Before, or after, you ran the LSP / Winsock repairs?

The thing about LSP / Winsock problems is that we are constantly learning about
the problem. I'm currently looking for a way to actually translate the content
of the enumeration (such as what you provided) into an actual diagnosis.
Something more than "there's IPX / SPX - get rid of that"!.

As to your existing problems, let's look at them.

Have you looked at DNS and MTU, for the Internet symptoms?
<http://nitecruzr.blogspot.com/2006/05/identifying-dns-problem-in-your.html>
http://nitecruzr.blogspot.com/2006/05/identifying-dns-problem-in-your.html
<http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html>
http://nitecruzr.blogspot.com/2005/06/internet-connectivity-problems-caused.html

 

[Guest]

Chuck

Thanks for the tips I'll take a look and let you know.

As for the redundant protocols, I unchecked those (did *not* uninstall them)
after trying everything else.

(I should explain that this is not my laptop. It belongs to a very good
friend of ours here on a visit who normally resides in your neck of the
woods, but a bit further south - in San Deigo [don't worry I shan't send him
round to your place when he returns] but I don't know the full history of his
machine. If all else fails, he'll have to do a system rebuild when he gets
home, but he is rather desparate to get internet connectivity back before he
leaves us on the next stage of his journey round Europe.)

Best regards

Mike

 

[Guest]

MORE ......
Chuck

I've followed up the tips you sent.

I'm pretty certain this is not an MTU problem: I can't browse *any* internet
site, and this behaviour is the same regardless of which wireless adapator I
use or even if I use a LAN cable connection.

My DNS settings are identical on badcomputer and all the goodcomputers and
are automatically assigned.

Interestingly, I can ping 66.94.230.33 and I can ping www.yahoo.com - though
this resolves to 209.73.186.238 which I can also ping - and get replies in
every case. So I am somehow connected to the web, I just can't browse it
using IE or Firefox.

Mike

 

[Chuck]

MORE ......
Chuck

I've followed up the tips you sent.

I'm pretty certain this is not an MTU problem: I can't browse *any* internet
site, and this behaviour is the same regardless of which wireless adapator I
use or even if I use a LAN cable connection.

My DNS settings are identical on badcomputer and all the goodcomputers and
are automatically assigned.

Interestingly, I can ping 66.94.230.33 and I can ping www.yahoo.com - though
this resolves to 209.73.186.238 which I can also ping - and get replies in
every case. So I am somehow connected to the web, I just can't browse it
using IE or Firefox.

Mike

OK, Mike, I'm going to keep looking for a solution. What Norton product is
this? Look for antiworm documentation - that's gotten folks in the past.

 

[Guest]

Chuck

Thanks

Norton is v 9.05.15 BTW

"desparate" should of course be "desperate" (cf "separate") - I was in a
hurry. (I typed all my cmd lines correctly!) I think now, however, he is
more resigned than desperate.

Anyway, thanks once again for all your efforts.

Best regards

Mike

 

[Chuck]

Chuck

Thanks

Norton is v 9.05.15 BTW

"desparate" should of course be "desperate" (cf "separate") - I was in a
hurry. (I typed all my cmd lines correctly!) I think now, however, he is
more resigned than desperate.

Mike,

That's the version number, not the name. There are several Norton products.
Some contain an antiworm product, that can cause problems like yours. Now you
need to look at the documentation, for antiworm protection, and configure it
properly.

 

[Guest]

Mike,

That's the version number, not the name. There are several Norton products.
Some contain an antiworm product, that can cause problems like yours. Now you
need to look at the documentation, for antiworm protection, and configure it
properly.

Chuck

Sorry I mis-understood. The product is simply Norton Anti-Virus 2003. It
does have an anti-worm feature (under "email settings") but there are no
setttings for this other than on and off. I tried switching off, but this
had no effect. In any case, the computer was working fine until recently
with the anti-worm feature switched on.

Our guest has now left taking "badcomputer" with him, so there is nothing
more I can do for him. I am still utterly baffled as to how a computer can
ping the entire web and an entire LAN but fail to ping itself or browse
anything anywhere - even after every relevant software component has been
fixed or renewed. I am more determined than ever that I shall never let
Norton anywhere near a computer that I have anything to do with.

Thanks again for all your attempts to help.

Mike

 

[Chuck]

Chuck

Sorry I mis-understood. The product is simply Norton Anti-Virus 2003. It
does have an anti-worm feature (under "email settings") but there are no
setttings for this other than on and off. I tried switching off, but this
had no effect. In any case, the computer was working fine until recently
with the anti-worm feature switched on.

Our guest has now left taking "badcomputer" with him, so there is nothing
more I can do for him. I am still utterly baffled as to how a computer can
ping the entire web and an entire LAN but fail to ping itself or browse
anything anywhere - even after every relevant software component has been
fixed or renewed. I am more determined than ever that I shall never let
Norton anywhere near a computer that I have anything to do with.

Thanks again for all your attempts to help.

Mike

Mike,

Don't blame Norton, without knowing the problem. But thanks for the feedback.