Unable to ping my own IP address

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My host PC has the IP address 192.168.0.1 and my clent has 192.168.0.69. I can ping both addresses from the client but from the host i can only ping the client. I cannot ping my own IP address. Can anybody help please.
 
Check the cable, try switching the network adapters, try
a different port on the switch, remove and reinstall the
nic drivers and ip stack.

Dwaine
-----Original Message-----
My host PC has the IP address 192.168.0.1 and my clent
Click to expand...
has 192.168.0.69. I can ping both addresses from the
client but from the host i can only ping the client. I
cannot ping my own IP address. Can anybody help please.
 
My host PC has the IP address 192.168.0.1 and my clent has 192.168.0.69. I can ping both addresses from the client but from the host i can only ping the client. I cannot ping my own IP address. Can anybody help please.
Click to expand...

Failure to ping your own IP address is probably caused by a firewall
program that's misconfigured or has been incompletely un-installed.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
Me neither not able to ping own address (computer) so I called Comcast
just a few ago and he told me call Dell (my brand) cause Comcast has
no procedure for that, honest but he said he bets it something with the
firewall I haven't called yet cause its like 1 am in chicago il now, I
am running NIS2004, I have disable the security stuff from Microsoft
9security center) if anyone is out there that can help, i'm up for it
..t y Bad
 
Windows Firewall or ICF will block ICMP packets (the basis for ping) unless
you've opened the port to allow them through. You can do that in the
firewall configuration though be aware that while it will allow you to ping
your own PC, it will also allow someone to intiate a denial of service ping
attack on you (which is why it's disabled by default). I'd leave it
disabled unless you have have a reason to need to ping for troubleshooting
purposes. NIS2004 offers something that acts like a firewall to protect
against worms and it has essentially the same features as Windows Firewall
(and thus imposes a lot of the same restrictions). I wouldn't be at all
surprised if your problem is caused by a setting in NIS2004. Try pinging
after shutting it off completely.

You might try pinging 127.0.0.1 just to make sure your TCP/IP connection is
working. That's sort of like pinging your own PC but it's the loopback
address (so not exactly the same - but if it doesn't work, you can be sure
nothing else is going to work either).

And make sure you're pinging the right TCP/IP address for your machine. Run
ipconfig to make sure you have the correct address.

NIS2004 also can cause this problem with their worm blocker softw
 
Back
Top