Re: Rapishare ar IPT? [ZoomX @ 2009-07-12 10:50:09]

Tema: Re: Rapishare ar IPT?
Autorius: ZoomX
Data: 2009-07-12 10:50:09
True. Čia naujas bajeriukas , kad neapsikente
trukinėjančiu ryšiu jiems už "servisa" pinigus mokėtumėte.
"ReM" <no@delfi.lt> wrote in message 
news:h32o1i$oh2$1@trimpas.omnitel.net...
> Čia toks rapidos ribojimas tiems, kas siunčiasi dykai...
>
> "blah" <blah@blah.bl> wrote in message 
> news:h306dg$ra0$1@trimpas.omnitel.net...
>> kelis vakarus (diena viskas normaliai) pastebejau, kad siuncia bangomis 
>> t.y. siuncia, siuncia ir keliom sekundem uzsistabdo, tada vel siuncia ir 
>> vel uzsistabdo, tai cia IPT kazka buria ar rapidshare vakare apsikrauna 
>> ir pats kazka riboja ? papinginus matosi, kad cia neatsitiktiniai 
>> sutrikimai (7geri, 4blogi, 7geri, 4blogi ir t.t.)?
>>
>> Reply from 195.122.131.22: bytes=32 time=40ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=253ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=560ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=528ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=544ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=39ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=167ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=546ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=513ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=529ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=39ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=39ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=40ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=129ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=532ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=548ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=517ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=49ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=39ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=40ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=48ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=525ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=516ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=533ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=331ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=41ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=41ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=39ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=42ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=40ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=175ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=530ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=497ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=513ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=39ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=39ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=46ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=46ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=40ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=272ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=553ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=206ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=440ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=43ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=41ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=39ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=38ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=61ms TTL=52
>> Reply from 195.122.131.22: bytes=32 time=179ms TTL=52
>>
>> Ping statistics for 195.122.131.22:
>>    Packets: Sent = 66, Received = 66, Lost = 0 (0% loss),
>> Approximate round trip times in milli-seconds:
>>    Minimum = 38ms, Maximum = 560ms, Average = 186ms
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus 
>> signature database 4224 (20090708) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus 
> signature database 4224 (20090708) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>