Can't ping Just One Address

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

Guest

I'm working on a laptop that has a strange problem. It's able to ping any of
the internal servers among other Internet-related sites, but it's not able to
ping this one thing with an address of 192.168.51.37. I can logon to other
computers and ping it fine. I'm positive that it's online and functioning
properly.

What could the problem be?
 
I'm working on a laptop that has a strange problem. It's able to ping any of
the internal servers among other Internet-related sites, but it's not able to
ping this one thing with an address of 192.168.51.37. I can logon to other
computers and ping it fine. I'm positive that it's online and functioning
properly.

What could the problem be?

Please start by providing the text of the "not able to ping". Is it an address
resolution, or connectivity, issue? What is this one "thing"? Could this thing
have a firewall blocking your pings?
 
This "one thing" is a NetIntegrator Mark I (file server) with firewall turned
off.

Asin,

OK, if it's a file server, what operating system (name, edition (if XP, is it
Home or Pro), and service pack level) does it run?

Please provide the text of the "not able to ping". Is it an address resolution,
or connectivity, issue?

Blocked pings generally have one cause - a misconfigured or overlooked firewall
on the server. What firewall did you turn off? Could you have a firewall
bundled with your antivirus protection? Please read this article:
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>

Check the laptop for LSP / Winsock corruption too.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
 
I have exactly the same Problem: On my notebook (Dell) with WinXP Prof i can
access alle computers on LAN and Internet proper. But from the LAN i can NOT
PING my notebook (timeout) and also i can not access the shares of my
notebook(error 53)! I disabled my XP-SP2-Firewall and i don't have any other
blocking software running (i'm quite shure...). I also tried the
Winsock-Fix-Tools, but no success.

What can cause this error???
 
Bingo!!! My Cisco VPN Client had it's internal firewall turned on. This
firewall also was turned on when the VPN software was not running!! Just
disabled it and it works!
Thanks much for you help!
 
Can you please tell me how I could go about disabling any such firewall?
I've heard of VPN having an internal firewall before but couldn't find
anything on how to disable it.
 
Sorry for the late reply. I will ask my supervisor the questions that you
asked me when he comes in today.

For now, I will try the LSP / Winsock fixes.

Thanks.
 
I use the Cisco Systems VPN Client (Version 4.6.00.0045).
To Disable the Firewall in the Cisco VPN Client disable the Firewall at:
"Options"->"Statefull Firewall (Always On)".

hope i could help u.
 
Unfortunately, not so much there. But thanks for the help. ;)

We're using Shiva VPN Client as our client software.
 
The Mark I is running Linux, he doesn't know which version.

I don't think that it's an address resolution issue as using both the server
name and the IP address fails. By fail, I mean that the ping times out.

Any other computer on the network is able to ping the Mark I with both the
server name and the IP address.
 
The Mark I is running Linux, he doesn't know which version.

I don't think that it's an address resolution issue as using both the server
name and the IP address fails. By fail, I mean that the ping times out.

Any other computer on the network is able to ping the Mark I with both the
server name and the IP address.

Asin,

OK, your having now provided some detail about "can't ping", I don't think it's
a name resolution problem either.

Your stating that other computers have no problem, but yours does, means we have
to ask what the difference is between the other computers and this one? You'll
have to provide some more clues to get this started.

Do you have a tech support staff that is responsible for the server? Why are
you the one researching the problem for the server?
 
Thanks for your help. :)

It's strange in that this computer is no different than the others that I've
worked on. They're all IBM ThinkPad T40s or T42s with factory fresh
installations on them. If not, they were rebuilt with the IBM Recovery
Program using the image on the hidden partition designed specifically to
return the laptop to a factory fresh state.

All the same software is installed on the laptops.

Actually, one of the fixes in the link that you gave me on LSP / Winsock
issues half-worked. WinsockFix allowed the laptop to ping the server's IP
address (192.168.51.37), but not the actual name of the server although it
works on other computers.

The reason that I'm the one researching this as opposed to my supervisors is
that this is considered to be a low-priority issue. Fitting, for a co-op
student (intern) such as myself.
 
Back
Top