Newsgroups : Borland : borland.public.delphi.internet.winsock : 2006 Dec : Re: Delphi Indy 10 TIdIcmpClient

www.cryer.info
Managed Newsgroup Archive

Re: Delphi Indy 10 TIdIcmpClient

Subject:Re: Delphi Indy 10 TIdIcmpClient
Posted by:"Ryan" (nospam@nospam.nospam)
Date:Wed, 21 Feb 2007 16:06:01

I too am having the same problem using Indy 10.1.5.
Any calls to TIdICMPClient's TTL property (which I had to decend to use),
cause the ping to time out. This is despite the fact that if you look at the
packets using Ethereal, the pings return rapidly with 'TTL expired'. Yet by
using OnReply in aforementioned class I just get a timeout. I don't get it
at all.
So, I started using TIdTraceRoute. This comes back with hostname '' and ip
address = 0.0.0.0 for every hop, with FReplyStatus=rsTimeout.
What's going on!?
PS, I'm using windows 2003 server and delphi 2006.

<valdi@dk.is> wrote in message news:459ef7b2@newsgroups.borland.com...
> Does any one know of a solution for this problem?
> I this a know bug?
>
>
> <valdi@dk.is> wrote in message news:459475d7@newsgroups.borland.com...
>> Iīm not getting the information i needed from the TidTraceRoute
>>
>> this is what i get when i use the command promt trace route command
>>
>> C:\Documents and Settings\valdi>tracert mbl.is
>> Tracing route to mbl.is [193.4.96.21]
>> over a maximum of 30 hops:
>>
>>  1    <1 ms    <1 ms    <1 ms  dmz.basis.is [85.197.248.1]
>>  2    <1 ms    <1 ms    <1 ms  ipf-gw.basis.is [85.197.248.130]
>>  3     1 ms     1 ms     1 ms  basis-gw.ipf.is [85.197.255.137]
>>  4     1 ms     1 ms     1 ms  vl3-rtr1.tg.ipf.is [85.197.193.65]
>>  5     1 ms     1 ms     1 ms  rix-gw.islandssimi.is [193.4.59.13]
>>  6     2 ms     2 ms     2 ms  A024-V2009.metronet.is [193.4.253.131]
>>  7     2 ms     3 ms     3 ms  193.4.252.166
>>  8     2 ms     2 ms     3 ms  neumann.mbl.is [193.4.96.21]
>>
>> Trace complete.
>>
>> This is what i get with the indy trace route
>>
>> 0.0.0.0                             []
>> 0.0.0.0                             []
>> 0.0.0.0                             []
>> 0.0.0.0                             []
>> 0.0.0.0                             []
>> 0.0.0.0                             []
>> 0.0.0.0                             []
>> 193.4.96.21               [neumann.mbl.is]
>>
>> I need to get the first and second replay to identify the isp so i can
>> resolve the isp mail server witch in this case the isp is basis.is
>> then i try to gethostbyname mail.basis.is --> smtp.basis.is
>> if these are valid then i use them to send mail messages
>>
>> does any one have an idea why i get different trace in Indy
>> TidTraceRoute?
>> Does any one know of a better method of doing this?
>>
>>
>>
>> "Don Siders" <sidersd@att.net> wrote in message
>> news:4592b33e@newsgroups.borland.com...
>>>> Thank you for youīre input, i am now trying to use the TidTraceRoute
>>>> object
>>>> but when i call route.Trace i get a socket error #10013 access denied.
>>>> I donīt really under stand this problem because i donīt have a firewall
>>>> or virus protection
>>>> I tryed to run-->cmd-->tracert google.com
>>>> and there it works fine,, do i need administrative rights to call the
>>>> trace procedure ?
>>>
>>> For WinNT and Win2000... definitely.
>>>
>>> For WinXP, ICMP is tied to ICF(Internet Connetion Firewall).  ICMP
>>> requests /  responses are not enabled (by default) in Win XP and ICF.
>>> Changing ICF settings requires Local Administrator privileges.
>>>
>>> hth...

Replies:

none

In response to:

www.cryer.info
Managed Newsgroup Archive