The company I work for has an application that was developed in house that uses the ping command. Here is a description of the problem as written by company product support:
"For some time now we have been plagued with problems using SNMP devices on certain loads.
The Traps, GETs, SETs, and MIB walk all work fine.
The problem is with the "Ping" command issued by the application periodically to each SNMP network element (NE) to verify its presence on the network.
As soon as the application begins operations, it attempts to "Ping" each NE, and it continues to do so once each minute (user adjustable) forevermore.
On most installations (post Windows XP), this results in a "Socket Initialization Error" (this is what we see in the debug window)."
All computers that are running the application can successfully ping targets from the command line. But the ping initiated from the application fails. The application is currently working on one Windows 2008 Server and one Windows 7 64-bit PC but we cannot find a difference between these installations and the ones where the application does not work. The problem occurs in both 32 and 64 bit versions of Windows 7. I have disabled Windows Firewall and removed Symantec Endpoint Protection from a test PC but the results have not changed. I have also tried disabling IPv6.
I am at a complete loss. Any ideas?