Hi Vladimir!

> Saturday March 25 2006, Janis Kracht wrote to Vladimir Donskoy:

>>>>> Can you ping my system by "ping" utility?

>> No.. it times out.

>>> Please, ping 194.84.229.122 (or "vbd.marvelm.ru").
If the ping will
>>> negative, please make "traceroute" to it.

>> It dies around #12:

> Thank you!

Your welcome.. I know it can be a pain sometimes :(

>> traceroute to vbd.marvelm.ru (194.84.229.122), 30 hops max, 40 byte
>> packets 1  h69-11-189-81.69-11.unk.tds.net (69.11.189.81)  1.037 ms  0.604
>> ms  0.575 ms 2  wndsnyhed01-a1-0-320579.network.tds.net (69.11.189.97)
>> 6.255 ms  5.813 ms 5.939 ms
>> 3 nycmnyhed01-a0-0-1410032.network.tds.net (69.128.250.101)  56.735 ms
>> 57.145 ms  56.403 ms
>> 4 chcgildtcor02-p0-0.network.tds.net (64.50.239.6)  80.113 ms  80.550
>> ms 78.321 ms 5  chi-bb1-geth7-3-4-0.telia.net (213.248.84.41)  78.147 ms
>> 78.800 ms  81.094 ms 6  nyk-bb2-pos7-1-0.telia.net (213.248.80.74)  98.846
>> ms  99.259 ms  99.256 ms 7  kbn-bb2-pos1-3-0.telia.net (213.248.64.33)
>> 191.305 ms  191.675 ms  191.172 ms 8  s-bb2-link.telia.net
>> (213.248.65.165)  225.754 ms  200.049 ms  200.271 ms 9
>> s-b3-pos4-0.telia.net (213.248.66.10)  199.872 ms  199.559 ms  199.521 ms
>> 10  equant-106622-s-b3.c.telia.net (213.248.66.98)  196.170 ms  197.128 ms
>> 198.524 ms 11  moscow08-pos-0-0.ru.equant.net (57.86.128.82)  222.246 ms
>> 219.390 ms 219.299 ms
>> 12  Moscow18-GE0-0-0.RoSprint.net (193.232.88.3) 223.754 ms  223.625 ms
>> 225.446 ms
>> 13  * *

> Back trace:

> [dvb 09:36:41 ~]$traceroute 69.11.189.81
> traceroute to 69.11.189.81 (69.11.189.81), 64 hops max, 44 byte packets
> 1  router (194.84.229.97)  1.078 ms  0.921 ms  0.963 ms
> 2  Moscow18-S10-0-2-1.rosprint.net (195.151.255.18)  15.232 ms  15.111 ms
> 15.119 ms
> 3  Moscow08-G1-0.rosprint.net (193.232.88.8)  15.328 ms  17.894 ms  15.448 ms
> 4  bsto411-pos-7-0.se.equant.net (57.86.128.81)  38.390 ms  46.214 ms  50.518
> ms
> 5  s-b3-geth3-3.telia.net (213.248.66.97)  38.572 ms  43.516 ms  38.293 ms
> 6  s-bb2-pos7-1-0.telia.net (213.248.66.9)  38.899 ms  38.762 ms  38.644 ms
>7  kbn-bb2-pos0-0-0.telia.net (213.248.65.29)  50.371 ms  50.430 ms  50.254 ms
>8  nyk-bb2-link.telia.net (213.248.82.101)  132.425 ms  132.358 ms  132.677 ms
> 9  chi-bb1-pos7-0-0-0.telia.net (213.248.80.73)  150.811 ms  153.386 ms
> 153.569 ms
> 10  tds-103434-chi-bb1.c.telia.net (213.248.84.42)  156.645 ms  156.612 ms
> 156.807 ms
>11  wndsnyhed01-a1-0-101.network.tds.net (69.128.250.102)  229.646 ms  244.323
> ms  229.288 ms
> 12  * * *

> So, trouble in the my provider internal router (hop 3)... I will try ask him.

I hope they are able to help you with this.

> It's interesting that you have same problem at hops 11-12 (provider not
> transfer incoming requests).

Yes, that is.. though once you get to TDS.net, I guess it could be a
firewall kind of problem with the trace.

Take care,
Janis

--- BBBS/LiI v4.01 Flag-5