Because it's not the ping functionality that's blocked but the application that executes the ping? The system ping.exe is not being blocked by ESET, but your application ping test application is.Now,Why the ping test cannot ping but CMD can when the ESET smart security is on?Am I missing something?
-- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
