Can't Ping My Own IP Address

  • Thread starter Thread starter Don
  • Start date Start date
D

Don

I'm running XP Pro with all the latest updates. I was running a VPN
client from my employer and when I disconnected the VPN, the client
crashed. Ever since then my Internet connectivity is VERY sporadic.
Applications like Firefox and Thunderbird will not talk to the net at
all getting a "connection refused by server" message. Outlook can
sometimes get out. IE is the only application that can get to the net
pretty consistently but even that is not 100%. Some pages won't come
up.

I've checked all hardware (D-Link router and cable modem) and
everything is fine. Another computer attached to the same router has
no problems (that's the machine I'm sending this from). That second
computer can ping it's own IP address with no problems and has no
trouble getting out to the Internet and this second machine can ping
the computer that is having the trouble.

I also tried connecting the VPN again and disconnecting it. It does
not successfully connect any more either and the disconnect does not
fix the problem. I also tried uninstalling and reinstalling the VPN -
Again with no effect.

I've tried running with the XP firewall disabled and enabled with no
change in the symptoms.

I can ping the other computer on my home network and I can ping both
127.0.0.1 and "localhost" on the problem machine with no problems.
The "good" computer can ping all of the above and it can ping the "bad"
computer. It can also ping it's own IP address just fine. Running the
XP network diagnostic on the "good" computer shows everything passing
with no errors.

The IP is set up as DHCP from my local router. I've released and
renewed the license several times using ipconfig and even forced it to
use a different IP address by changing the settings in my router. None
of that had any effect.

The DNS server is passed through my router to the ISP and appears to
work fine as the other computer on my home net has no problems
accessing the net.

The WINS settings are to enable LMHOSTS lookup and the NetBIOS is set
to the "default" setting.

I tried comparing the settings on the two machine that I have on my
local net. They are both running the same version of XP so they should
be pretty much identical but one works and the other does not. So far,
I think I've gone through all the dialog boxes there are and have not
found any differences in the setting on the two machines.
I ran the XP Network Diagnostic tool and it failed. The only part of
the test that failed is when it tries to ping it's own IP address. I
tried this manually and got the same results. I can't ping my own IP
address. The "good" machine on the local network works fine and can
ping anything including the machine that is having the problem.

I'm guessing that the VPN crash left my machine in some indeterminate
state but I've checked everything I can think of and nothing appears to
be wrong.

Help!
 
Don,

Try resetting the Winsock by going to Start, Run, type in

netsh winsock reset

Click OK. You should be prompted to restart the system to complete the
operation.

MowGreen [MVP 2003-2006]
===============
*-343-* FDNY
Never Forgotten
===============
 
Try running the support tool netdiag on your problem computer to see what it
reports. You can paste the results here in a reply if you want. The support
tools are on the install disk in the support/tools folder where you have to
run the setup program there. --- Steve
 
Steve,

Thanks for the response. Here's the output from the netdiag program:
.................................

Computer Name: MUNICH
DNS Host Name: munich
System info : Windows 2000 Professional (Build 2600)
Processor : x86 Family 15 Model 47 Stepping 0, AuthenticAMD
List of installed hotfixes :
Q147222


Netcard queries test . . . . . . . : Passed
[WARNING] The net card 'Nortel IPSECSHM Adapter' may not be working
because it has not received any packets.
[WARNING] The net card 'Nortel IPSECSHM Adapter - Packet Scheduler
Miniport' may not be working because it has not received any packets.
[WARNING] The net card '1394 Net Adapter' may not be working
because it has not received any packets.



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : munich.oc.cox.net
IP Address . . . . . . . . : 192.168.0.100
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.0.1
Dns Servers. . . . . . . . : 192.168.0.1


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.

Adapter : {891CDA73-E67C-439A-BA78-6777874638B1}

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : munich
IP Address . . . . . . . . : 0.0.0.0
Subnet Mask. . . . . . . . : 0.0.0.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . :

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Skipped
[WARNING] No gateways defined for this adapter.

NetBT name test. . . . . . : Passed
No names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed
Dns domain name is not specified.
Dns forest name is not specified.


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{277B2946-13E2-4A3B-B266-59098FEE1181}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00>
'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names
defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{277B2946-13E2-4A3B-B266-59098FEE1181}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{277B2946-13E2-4A3B-B266-59098FEE1181}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Skipped


DC list test . . . . . . . . . . . : Skipped


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Skipped


LDAP test. . . . . . . . . . . . . : Skipped


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped
The IPSec service is not started.
Service status is: Stopped
Service startup is: Disabled


The command completed successfully


[Note: the Nortel VPN mentioned in the above is NOT the VPN that
crashed and caused all this. I have 2 VPN clients on this system that
are run at different times. Also note that the output says this
machine is Windows 2000 but it's actually XP.]
 
Do you have two physical network adapters in that computer because the
results show that it might and if so it shows one adapter with no IP address
or subnet address? If that is the case try disabling the adapter called
Adapter : {891CDA73-E67C-439A-BA78-6777874638B1 to see if anything improves
or go to Device manager and uninstall it and reboot the computer. Another
thing worth trying would be to use netsh to reset tcp/ip [netsh int ip reset
c:\resetlog.txt] as described in the KB article below. You might also try
reinstalling your drivers for your network adapters. Also I noticed you only
have one security update installed. That probably is not your problem but
you should be taking steps to keep current with critical security updates at
Windows Updates and if you went there I bet it would show that several are
missing. First though I would also try a System Restore if you have a
System Restore point before this all happened. Use
programs/accessories/system tools - System Restore to start the System
Restore wizard.--- Steve

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


Don said:
Steve,

Thanks for the response. Here's the output from the netdiag program:
................................

Computer Name: MUNICH
DNS Host Name: munich
System info : Windows 2000 Professional (Build 2600)
Processor : x86 Family 15 Model 47 Stepping 0, AuthenticAMD
List of installed hotfixes :
Q147222


Netcard queries test . . . . . . . : Passed
[WARNING] The net card 'Nortel IPSECSHM Adapter' may not be working
because it has not received any packets.
[WARNING] The net card 'Nortel IPSECSHM Adapter - Packet Scheduler
Miniport' may not be working because it has not received any packets.
[WARNING] The net card '1394 Net Adapter' may not be working
because it has not received any packets.



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : munich.oc.cox.net
IP Address . . . . . . . . : 192.168.0.100
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.0.1
Dns Servers. . . . . . . . : 192.168.0.1


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.

Adapter : {891CDA73-E67C-439A-BA78-6777874638B1}

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : munich
IP Address . . . . . . . . : 0.0.0.0
Subnet Mask. . . . . . . . : 0.0.0.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . :

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Skipped
[WARNING] No gateways defined for this adapter.

NetBT name test. . . . . . : Passed
No names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed
Dns domain name is not specified.
Dns forest name is not specified.


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{277B2946-13E2-4A3B-B266-59098FEE1181}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00>
'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names
defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{277B2946-13E2-4A3B-B266-59098FEE1181}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{277B2946-13E2-4A3B-B266-59098FEE1181}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Skipped


DC list test . . . . . . . . . . . : Skipped


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Skipped


LDAP test. . . . . . . . . . . . . : Skipped


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped
The IPSec service is not started.
Service status is: Stopped
Service startup is: Disabled


The command completed successfully


[Note: the Nortel VPN mentioned in the above is NOT the VPN that
crashed and caused all this. I have 2 VPN clients on this system that
are run at different times. Also note that the output says this
machine is Windows 2000 but it's actually XP.]
Click to expand...
 
Steve, in response to your questions/comments:

1) I only have one NIC on this machine. The adapter you identified
says it is a Nortel adapter and the only thing that I have from Nortel
is a VPN client that my wife uses with her company.

2) I could not disable the Nortel adapter so I uninstalled it and it is
now gone. "ipconfig /all" does not show anything for this adapter any
more but the problem still persists.

3) I tried resetting the tcp/ip using netsh as you suggested but it
also did not solve the problem - even after a reboot.

4) I have downloaded and installed a new driver for my NIC since this
all started so the driver is up to date and newer than the original one
I was using. Rolling back to the old driver also made no difference
(which makes sense since I was running the older driver when all this
started).

5) Even though it says I only have 1 security update, this version of
XP was absolutely current as of 2 weeks ago (when the problem started).
I have kept it updated on a fairly regular basis. I've got SP2
already loaded so maybe there is only 1 update on top of SP2...?

6) I tried a system restore before I updated the NIC driver and it said
that there were no changes in any files since several known good points
in time. I even checked all the way back to the last complete Windows
update I did and there were no changes in any of the system files. BTW
it's a real pain in the neck that the system restore reboots the
machine and then tells you there is nothing to do! That's just stupid
in my book.

7) It's getting late (past midnight) so I've got to get some sleep...
I'll read the article you posted tomorrow and try some more.

Thanks for all your help so far!
 
it would seem to me that the network adapter may be hooped, you may want to
try to get an identical adapter and see if the problem persists.
 
Jon,

The NIC on this machine is on the motherboard. I tried to install
another PCI NIC card that I had laying around but it was an old style
PCI card and would not fit in the new machine. I'll try to borrow a
NIC from work today.


Don
 
if you can access cmos, make sure the NIC is turned on. If, somehow, it got
switched off it would behave like it is dead

Jon
 
I have a few more data points that might be clues as to what is going
on here...

In the process of running the netdiag program outlined above, I was
faced with trying to post the results of the utility (since they were
rather verbose). In order to move this data from the "bad" machine to
my "good" machine I could not use a floppy since the "bad" machine does
not have a floppy drive.

What I wound up doing was creating a shared folder on the "good"
machine and mapping it on the "bad" machine and that worked. I am able
to map network drives that exist on the "good" machine onto the "bad"
one. The reverse does not work though. I cannot create a shared
folder on the "bad" machine and map it on the "good" one. When I try
to map a folder this way, the "good" machine sees the "bad" machine's
name as part of my local network but it cannot see anything inside the
machine.

The second point I wanted to make is that I noticed that there is a
difference between the two machines if I open the "Network Connections"
dialog box from the Start/Settings menu. On my "good" machine and on
my office machine, there is only one bold heading in this box labeled
"LAN or High Speed Internet". On my "bad" machine, there is an
additional heading labeled "Internet Gateway". This heading has one
entry under it which reads "Internet Connection" with type "Internet
Gateway", status "Connected", and name "Internet Connection".

Trying to bring up the properties window on this connection results in
a dialog box that does not have any useful information in it. Right
clicking on it and asking for it's status brings up a dialog box that
indicates that the connection is good and working fine and there is
constant send and receive traffic on the interface (not a large amount
but the counters do constantly increment). There is a "disable" button
on this form but pressing it does not appear to do anything - The
status display stays the same even though it takes about 30 seconds for
it to come back from the button press.


Don
 
Jon,

The NIC is on and working fine. As I just posted above, I can map a
network drive on my "good" machine onto the "bad" one and transfer
files between the machines. I can also access the administrator's
console on my router on both machines.


Don
 
Steve,

The article you referred to above describes how to use the ICS to
enable and disable the internet connection but it does not describe how
to remove the ICS feature.

I have played around with this and when I hit the "disable" button on
the gateway, it causes the router to release it's IP address and
effectively cuts off the internet connection. Similarly, "enable"
causes the router to renew it's IP address and everything works again.

The bad computer is configured for DHCP and that works. I've done it
manually using the ipconfig command.

No other computer on my system should be using the bad computer as a
gateway. If it's set up that way, that may be my problem but I still
don't know how to remove the gateway.

Thanks,


Don
 
I performed all of the actions described in both of the articles you
sent above and I can't get the Internet Gateway to go away. Every time
I reboot the machine, the gateway is gone for about 60 seconds and then
suddenly reappears in the Network Connections window. I've even set
the registry to the value recommended in the second article even though
the article said the values should be either 2 or 3 and mine was 4 when
I started (I set it to the recommended value of 3).

Right now the ICS service is NOT running on my bad machine but the
Internet Gateway feature still appears.

Just as a datapoint, my good machine has the Firewall/ICS service
running by default and it's not having any problems so this service by
itself does not appear to be the cause of the problem.

Any other ideas?

I've arranged to borrow a NIC card from work tomorrow and I'll try to
install it tomorrow night and see what effect that has on all this.


Don
 
Hi Don.

I am pretty much out of ideas on your problem beyond doing a upgrade/repair
install. What I would suggest is that you also try posting in the
Microsoft.public.windowsxp.network_web newsgroup to see if anyone over there
can help out further. --- Steve
 
Back
Top