Det skyldes sikkert at alle brugerne tilsammen pumper forbindelsen så hårdt,
at
pakkerne står på nakken af hinanden for at komme igennem.
Lidt ala myldertid i trafikken - bilerne kan ikke komme frem og holder
derfor helt stille.
Men jeg undrer mig lidt over dit packet loss. hvor tæt er forbindelsen på
støjgrænsen ?
Eivind
"Blacky" <mtl@dsr.kvl.dk> wrote in message
news:qvcfht0ktvj9indaaj3diqr52sjiofm9sc@4ax.com...
> Hej med jer
>
> Jeg sidder på en 2Mbit ADSL-forbindelse fra tdc, som vi deler mellem
> mange brugere.
>
> Nogen gange er pingtiderne ret lange:
> Faktisk så lange at der nogen gange er time-out.
>
> Hvad ligger en normal pingtid på, og hvad tror I at disse lange
> pingtider kan skyldes?
>
> Mvh
> blacky
>
> C:\>ping -t
www.dr.dk
>
> Pinging
www.dr.dk [129.142.20.35] with 32 bytes of data:
>
> Reply from 129.142.20.35: bytes=32 time=360ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=301ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=190ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=240ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=450ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=481ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=601ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=511ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=511ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=460ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=441ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=310ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=491ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=420ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=481ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=401ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=471ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=571ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=500ms TTL=119
> Request timed out.
> Reply from 129.142.20.35: bytes=32 time=371ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=410ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=491ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=390ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=421ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=331ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=390ms TTL=119
> Request timed out.
> Reply from 129.142.20.35: bytes=32 time=231ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=140ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=391ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=521ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=521ms TTL=119
> Request timed out.
> Reply from 129.142.20.35: bytes=32 time=521ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=381ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=360ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=371ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=500ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=331ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=561ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=400ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=431ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=270ms TTL=119
> Reply from 129.142.20.35: bytes=32 time=321ms TTL=119
>
> Ping statistics for 129.142.20.35:
> Packets: Sent = 45, Received = 42, Lost = 3 (6% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 140ms, Maximum = 601ms, Average = 383ms
> Control-C
> ^C
> C:\>