Can't Ping Gateway on Windows XP (Dell), IP setup looks OK

[bikingbill]

System: Dell Dimension 2400 XP SP2

The system is connected by a ethernet cable to a Netgear router. A Mac Laptop was used to verify the connection at the cable that goes into the PC.

Here's the situation. I lost connectivity on a uninstall of MacAfee and a Virus run with FP-PROT. Did all the fixes as suggested on:

http://www.online-tech-tips.com/computer-tips/winsock-fix/

(Reseting TCP/IP Stack (netsh), Resting Winsock catalog, XP_Winfix, XP TCIP Repair, uninstall/install hardware, uninstall/install protocols etc. etc.).

Even reinstalled Windows from a boot CD, reinstalled device drivers etc.

Network Connection Details are fine.

IP Address: 192.168.1.4 ... and the Router shows the Dell connected at this address.
Default Gateway and DHCP and DNS Server: 192.168.1.1 ... these are the correct values as assigned by router as verified on the Mac Laptop (connected to same router).

Hardware diagnostic on network card also ok.

PING to IP Address: Works
PING to Gateway Address: Timeout
PING to Mac: Timeout
PING to outside address (76.176.187.56): Timeout

All of these verified on Mac Laptop connected to same router and they work.

Running Network Diagnostics for XP on the Dell says:

"Error attmpting to validate Winsock base providers: 2
Not all base service provider entries could be found in the winsock catalog. A reset is needed."

Have done multiple passes with these tools. In normal and safe (with network) modes.

Is my only option to pull the docs off and nuke (reformat) the drive, install Windows etc.?

This is the GF's machine (men, don't ever do this) and all works except no internet connect.

Note: One week, about 40 hours into this and I used to (1999) be a CTO and now I remember why I'm not and why I'm not running Windows. Sorry.

 

[bikingbill]

Oh, I should mention that Activity shows 120 packers sent, 29 Received.

Thanks.

 

[Turkbear]

Hi,
maybe this will help ( seems to be a somewhat common issue at least based on Google hits)..

http://www.softpedia.com/get/Tweak/Network-Tweak/WinSockFix.shtml

To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[bikingbill]

No joy. In fact it took away the connect to the router. XP TCIP Repair will bring that back, but I'm still where I was.

 

[BadBigBen]

How to fix Winsock2 corruption issue - Causes

http://www.howtonetworking.com/Troubleshooting/winsock2corruption2.htm

Click NEXT PAGE for further info on fixing the corruption...

the following may be of use if the above does not help:

How to reset Internet Protocol (TCP/IP) in Windows XP

http://support.microsoft.com/kb/299357

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

How to ask a question, when posting them to a professional forum.

 

[bikingbill]

It passes the "netdiag /test:winsock" tests. I had done the reset previously.

 

[bikingbill]

TCP/IP reset as suggested. No joy.

Well, at least now the router DOESN'T see the Dell. That's a change.

 

[BadBigBen]

Ok can you list an IPCONFIG /ALL from the afflicted PC?


Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

How to ask a question, when posting them to a professional forum.

 

[bikingbill]

Here's the text from a IPCONFIG/ALL (I restored connectivity to/from router ... still can't PING the Gateway).

Windows IP Configuration



Host Name . . . . . . . . . . . . : LEAHDELL

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection 4:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller

Physical Address. . . . . . . . . : 00-0D-56-68-99-26

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : fe80::20d:56ff:fe68:9926%4

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 192.168.1.1

fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

Lease Obtained. . . . . . . . . . : Sunday, April 26, 2009 12:50:17 PM

Lease Expires . . . . . . . . . . : Monday, April 27, 2009 12:50:17 PM



Tunnel adapter Teredo Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5

Default Gateway . . . . . . . . . :

NetBIOS over Tcpip. . . . . . . . : Disabled



Tunnel adapter Automatic Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-01-02

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.2%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled

Thank you for looking at this.

 

[BadBigBen]

Ok, I don't see anything out of the ordinary...

but I did notice that IPv6 is enabled, deinstall TCP/IPv6, in XP it can cause problems with older router hardware, and is at this point of time not very widely spread in the world, and in a home network not at all needed...

see if deinstalling it makes a difference...



Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

How to ask a question, when posting them to a professional forum.

 

[bikingbill]

Uninstalled the IPv6. No change.

New IPCONFIG /ALL


Windows IP Configuration

Host Name . . . . . . . . . . . . : LEAHDELL
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 4:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller
Physical Address. . . . . . . . . : 00-0D-56-68-99-26
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Monday, April 27, 2009 10:34:24 AM
Lease Expires . . . . . . . . . . : Tuesday, April 28, 2009 10:34:24 AM

PING to 192.168.1.1 Fails
PING to 76,176.187.56 Fails
PING to 192.168.1.2 Succeeds.

 

[bikingbill]

Here's the report from the Network Diagnostics in Explorer: (Note: Running the fix does not fix the problem)

WinSock Diagnostic

WinSock status

info All base service provider entries are present in the Winsock catalog.
info The Winsock Service provider chains are valid.
error Provider entry MSAFD Tcpip [TCP/IP] could not perform simple loopback communication. Error -1.
error Provider entry MSAFD Tcpip [UDP/IP] could not perform simple loopback communication. Error -1.
error Provider entry RSVP UDP Service Provider could not perform simple loopback communication. Error -1.
error Provider entry RSVP TCP Service Provider could not perform simple loopback communication. Error -1.
error A connectivity problem exists with an installed LSP.
info The user didn't approve the proposed automated repair attempt: Reset WinSock catalog
info Redirecting user to support call

 

[bikingbill]

Another bizarre clue.

The Dell on the LAN is sitting at 192.168.1.2

The Mac on the same LAN is sitting at 192.168.1.4

As I mentioned the Dell can't ping the gateway at 192.168.1.1. It also can't ping the Mac at 192.168.1.4

BUT

The Mac can ping the Dell at 192.168.1.2 and those packets show up in network status on the Dell as you would expect.

Macintosh-135:~ bvolk$ ping 192.168.1.2
PING 192.168.1.2 (192.168.1.2): 56 data bytes
64 bytes from 192.168.1.2: icmp_seq=0 ttl=128 time=1.559 ms
64 bytes from 192.168.1.2: icmp_seq=1 ttl=128 time=1.647 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=128 time=1.610 ms
64 bytes from 192.168.1.2: icmp_seq=3 ttl=128 time=1.661 ms
64 bytes from 192.168.1.2: icmp_seq=4 ttl=128 time=1.704 ms

WTF?

 

[BadBigBen]

what firewall is installed and have you checked it?

if the above leads to naught, then I am afraid you may be heading towards a repair install...

I hope someone else may have more things to try before the repair install...


Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

How to ask a question, when posting them to a professional forum.

 

[bikingbill]

Windows Firewall was on, turned it off.

Ping to 192.168.1.1 (gateway) still fails.

Comodo firewall is installed but not protecting anything (settings). Should I uninstall it?

 

[anationalacrobat]

Nuke the site from orbit, it's the only way to be sure. Copy everything off to a thumb drive, reformat the disk, curse it soundly to scare away any lingering bits, format again for good measure, reinstall the OS.

 

[bikingbill]

What's the best software for preserving the apps and settings if I launch the nukes?

 

[BadBigBen]

Comodo firewall is installed but not protecting anything (settings). Should I uninstall it?

it is worth a try...

Nuke only when the REPAIR (Cluster Bombing) does not work... ;-)



Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

How to ask a question, when posting them to a professional forum.

 

[bikingbill]

Uninstall of Comodo didn't change anything.

The Mac can ping the Dell on the LAN. The router sees the Dell. The Dell sees the router. The Dell has 'proper' IP CONFIG, the Dell CAN'T ping the Gateway.

It seems so close and yet ... no joy.

Off to Costco to buy a USB drive since my Firewire stuff won't work on the Dell.

Buller? Buller?

 

[tlcscousin]

If you have a spare ethernet card install it and see if you then can get normal connectivity.