Major Problems?

Started by Desaan, Apr 22, 2011, 03:15:37

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Technical Ben

Quote from: Steve on Apr 26, 2011, 18:49:06
Maybe a stupid and erroneous analogy, if you look at capacity, if you fill an empty pint milk bottle from another pint bottle and pour it fast you spill some -FTTC, pour it slowly no problem adslmax.

Or try racing down the M25 in your Lamborghini = problem when you meet a traffic jam!
Asdl = driving slowly, FTTC = driving fast. Not that there are any dangers with broadband, just traffic jams when the slow meets the fast.
I use to have a signature, then it all changed to chip and pin.

gyruss

As my connection is down to 1400 downsteam, and 300'ish up, did similar pings and tracert anyway.  Tried with both idnet and opendns.

C:\>ping www.idnet.com

Pinging www.idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=42ms TTL=59
Reply from 212.69.36.10: bytes=32 time=125ms TTL=59
Reply from 212.69.36.10: bytes=32 time=129ms TTL=59
Reply from 212.69.36.10: bytes=32 time=87ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 42ms, Maximum = 129ms, Average = 95ms

C:\>tracert www.idnet.com

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    42 ms    42 ms    41 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    41 ms    42 ms    50 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4   184 ms   186 ms   254 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    96 ms   146 ms    65 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   107 ms    44 ms    42 ms  www.idnet.net [212.69.36.10]

Trace complete.
Jase


cavillas

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.



C:\Windows\system32>tracert www.idnet.com

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  READYSHARE [192.168.0.1]
  2    25 ms    24 ms    23 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    25 ms    23 ms    24 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4    24 ms    24 ms    23 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    24 ms    25 ms    24 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    26 ms    24 ms    24 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Windows\system32>tracert www.idnet.com

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  READYSHARE [192.168.0.1]
  2    26 ms    23 ms    23 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    22 ms    24 ms    24 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4    24 ms    25 ms    23 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    24 ms    24 ms    24 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    24 ms    24 ms    24 ms  www.idnet.net [212.69.36.10]

Trace complete.

On ordiniary adsl and from Frinton on sea excange and over 2.8 mles away.
------
Alf :)

.Griff.

C:\>tracert www.idnet.com

Tracing route to www.idnet.com [212.69.36.10]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2    18 ms    18 ms    18 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    18 ms    18 ms    18 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4    37 ms   275 ms    26 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    19 ms    21 ms    19 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    24 ms    19 ms    19 ms  www.idnet.net [212.69.36.10]

Trace complete.

gyruss

spikes at the redbus gw2? or is this normal????
Jase


Steve

I expect will have low priority there. Was anything running on your first set?
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

nope. and pc had been on for 5 mins, so no background services doing their connect traffic.
Jase


Steve

Your router stats looked OK in October has your downstream sync reduced a lot? If not are you not suffering from congestion at your local Exchange/VP
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

gyruss

I'll have to check my routers stats tonight when i get home.   

My stats in october were ok.. i enjoyed a 6mb connection throughout the whole of the rest of winter, and the first months of this year.. then we get this sunny weather in the last week or so and bam, suddenly i'm losing sync.. and getting slow speeds again (see my signature graphic for evidence).

I've got routerstats lite on my pc at home so i'll run that later, and i'll do a 17070 quiet line test next time it drops out too.   


Netgear Router is still in the hall and connected to the filtered faceplate that bt assisted with last year.

No changes to any cabling, or pc's inside the house, and the hall is not a hot room either. 

Jase