receving errors with PING

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

Guest

Everytime I try to use the PING utility at the command prompt in Win2k, I receive the following error:

The procedure entry point IcmpSendEcho2 could not be located in the dynamic link library ICMP.dll

I can surf the web, print and etc just fine. I've already tried uninstalling/reinstalling TCP/IP, but that didn't help.

Any suggestions?
 
Hi,

Check ICMP.DLL and the one in ..\winnt\system32 directory is 16k in size
dated
3/30/00 and the one in ..winnt\\system32\DLLchache directory and see if the
size
and date match.

If not, rename ICMP.DLL in winnt\system32 dir (after rebooting). Copy
backup of
ICMP.DLL from dllcache directory.

Note that some third party utilities will replace this file.

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Thread-Topic: receving errors with PING
thread-index: AcOX3HkXt9oSjGcjRJ2ujv86KdSpTg==
X-Tomcat-NG: microsoft.public.win2000.networking
From: =?Utf-8?B?U2Ft?= <[email protected]>
Subject: receving errors with PING
Date: Tue, 21 Oct 2003 07:06:07 -0700
Lines: 7
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.win2000.networking
NNTP-Posting-Host: TK2MSFTCMTY1 10.40.1.180
Path: cpmsftngxa06.phx.gbl!cpmsftngxa10.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.networking:41755
X-Tomcat-NG: microsoft.public.win2000.networking

Everytime I try to use the PING utility at the command prompt in Win2k, I
Click to expand...
receive the following error:

The procedure entry point IcmpSendEcho2 could not be located in the dynamic
link library ICMP.dll

I can surf the web, print and etc just fine. I've already tried
uninstalling/reinstalling TCP/IP, but that didn't help.

Any suggestions?
 
Back
Top