ping not working (causes windows error)

J

Julie

When I try to ping my own machine, or another, from a
command prompt, I get the following Windows
error: "TCP/IP Ping Command has encountered a problem and
needs to close". I can then send error to Microsoft
(which gives me no input). I tried copying ping.exe from
another machine that works, but get same error, so I
think it must be a problem in another file, but don't
know enough about ping to figure out which--any ideas?

Thanks,
Julie
 
M

Michael Burk [MSFT]

Ping uses the following 6 DLLs: Kernel32, msvcrt, advapi32, iphlpapi,
user32, and ws2_32. The last one, ws2_32.dll is your Winsock dll. This is
most likely the one that could be replaced by a third party software. A
repair installation is your best bet to get back to a known good set of
DLLs, but you can manually verify and replace these if you are comfortable
with such things.

--
Michael Burk

Longhorn Shell
http://msdn.microsoft.com/longhorn
----===========================----

This posting is provided "AS IS" with no warranties, and confers no rights.
 
G

Guest

2 things:
1) Read your event logs then head over to www.eventid.net and search for a
solution if there is a relavent event being logged
2) Reinstall your TCP/IP protocols
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top