Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
TidIcmpClient.Ping emulation
#4
(10-30-2023, 05:26 PM)rlebeau Wrote:
(10-30-2023, 03:23 AM)Boba TC Wrote: About 4 seconds later I get 0[zero] (TReplyStatusTypes::rsTimeOut).

Did you verify with a packet sniffer, like Wireshark, that your ping request is actually being transmitted out to the network, and is being responded to?

Also, make sure you are running your code as an elevated user.  TIdIcmpClient uses a RAW socket, which requires admin rights.  The command-line ping does not require that.

Thank you, Remy, for the prompt reply. When I use a different target IP (f.i. 144.160.36.42 or 142.250.105.101 ) I get echo reply with params identical to those returned by the DOS ping. My RG does not block any of my outgoing packets. I suspect the OS does something different (I'll have to install the WireShark). Will keep posted.

(10-30-2023, 03:15 PM)fearcry Wrote:
(10-30-2023, 03:23 AM)Boba TC Wrote: About 4 seconds later I get 0[zero] (TReplyStatusTypes::rsTimeOut).
What do I miss to mimic the DOS ping behaviour? TIA

On the 1st Sight i would say your App is blocked by a System-Firewall (Windows Systems) or your Router.

Greetings

hi fearcry; I can't blame either firewall or my RG (see me reply to Remy). What else should I look at?
Reply


Messages In This Thread
TidIcmpClient.Ping emulation - by Boba TC - 10-30-2023, 03:23 AM
RE: TidIcmpClient.Ping emulation - by fearcry - 10-30-2023, 03:15 PM
RE: TidIcmpClient.Ping emulation - by rlebeau - 10-30-2023, 05:26 PM
RE: TidIcmpClient.Ping emulation - by Boba TC - 10-31-2023, 05:08 AM
RE: TidIcmpClient.Ping emulation - by rlebeau - 10-31-2023, 08:04 PM
RE: TidIcmpClient.Ping emulation - by fearcry - 11-03-2023, 03:15 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)