In reply to a post by MrSaffron:

Check the router stats and from a DOS command prompt run

ping -t www.thinkbroadband.com

Do you get a constant stream of replies or are some timing out. Press CTRL C and ping will finish and give you some statistics.

Pinging www.thinkbroadband.com [80.249.99.130] with 32 bytes of data:
Request timed out.
Reply from 80.249.99.130: bytes=32 time=3220ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 80.249.99.130: bytes=32 time=1534ms TTL=56
Reply from 80.249.99.130: bytes=32 time=1636ms TTL=56
Reply from 80.249.99.130: bytes=32 time=1623ms TTL=56
Reply from 80.249.99.130: bytes=32 time=1986ms TTL=56
Reply from 80.249.99.130: bytes=32 time=3205ms TTL=56
Request timed out.
Reply from 80.249.99.130: bytes=32 time=3588ms TTL=56
Request timed out.
Request timed out.
Reply from 80.249.99.130: bytes=32 time=3493ms TTL=56
Request timed out.

CTRL C just closed the dos prompt

It is a serious struggle just to load this page to reply to your post

In reply to a post by flippery:

What exchange are you connected to

Flax Bourton or Backwell not sure how do I find that out?

Ok try ping -t 62.3.86.42

This is I think your Zen gateway and if the packet loss is showing up there then it may be a DSL issue, or backhaul issue.

If it was me I'd also give the router a good old reboot

In reply to a post by MrSaffron:

Ok try ping -t 62.3.86.42

This is I think your Zen gateway and if the packet loss is showing up there then it may be a DSL issue, or backhaul issue.

If it was me I'd also give the router a good old reboot

I'm now on the laptop plugged directly into the router

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

C:\Users\helan>ping -t 62.3.86.42

Pinging 62.3.86.42 with 32 bytes of data:
Reply from 62.3.86.42: bytes=32 time=182ms TTL=254
Reply from 62.3.86.42: bytes=32 time=123ms TTL=254
Reply from 62.3.86.42: bytes=32 time=160ms TTL=254
Reply from 62.3.86.42: bytes=32 time=131ms TTL=254
Reply from 62.3.86.42: bytes=32 time=158ms TTL=254
Reply from 62.3.86.42: bytes=32 time=132ms TTL=254
Reply from 62.3.86.42: bytes=32 time=51ms TTL=254
Reply from 62.3.86.42: bytes=32 time=232ms TTL=254
Reply from 62.3.86.42: bytes=32 time=171ms TTL=254
Reply from 62.3.86.42: bytes=32 time=186ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=53ms TTL=254
Reply from 62.3.86.42: bytes=32 time=104ms TTL=254
Reply from 62.3.86.42: bytes=32 time=104ms TTL=254
Reply from 62.3.86.42: bytes=32 time=147ms TTL=254
Reply from 62.3.86.42: bytes=32 time=119ms TTL=254
Reply from 62.3.86.42: bytes=32 time=59ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=102ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=199ms TTL=254
Reply from 62.3.86.42: bytes=32 time=195ms TTL=254
Reply from 62.3.86.42: bytes=32 time=101ms TTL=254
Reply from 62.3.86.42: bytes=32 time=190ms TTL=254
Reply from 62.3.86.42: bytes=32 time=139ms TTL=254
Reply from 62.3.86.42: bytes=32 time=123ms TTL=254
Reply from 62.3.86.42: bytes=32 time=183ms TTL=254
Reply from 62.3.86.42: bytes=32 time=64ms TTL=254
Reply from 62.3.86.42: bytes=32 time=260ms TTL=254
Reply from 62.3.86.42: bytes=32 time=120ms TTL=254
Reply from 62.3.86.42: bytes=32 time=73ms TTL=254
Reply from 62.3.86.42: bytes=32 time=227ms TTL=254
Reply from 62.3.86.42: bytes=32 time=85ms TTL=254
Reply from 62.3.86.42: bytes=32 time=182ms TTL=254
Reply from 62.3.86.42: bytes=32 time=150ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=95ms TTL=254
Reply from 62.3.86.42: bytes=32 time=211ms TTL=254
Reply from 62.3.86.42: bytes=32 time=196ms TTL=254
Reply from 62.3.86.42: bytes=32 time=129ms TTL=254
Reply from 62.3.86.42: bytes=32 time=103ms TTL=254
Reply from 62.3.86.42: bytes=32 time=80ms TTL=254
Reply from 62.3.86.42: bytes=32 time=135ms TTL=254
Reply from 62.3.86.42: bytes=32 time=58ms TTL=254
Reply from 62.3.86.42: bytes=32 time=127ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=117ms TTL=254
Reply from 62.3.86.42: bytes=32 time=211ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=177ms TTL=254
Reply from 62.3.86.42: bytes=32 time=153ms TTL=254
Reply from 62.3.86.42: bytes=32 time=188ms TTL=254
Reply from 62.3.86.42: bytes=32 time=253ms TTL=254
Reply from 62.3.86.42: bytes=32 time=204ms TTL=254
Reply from 62.3.86.42: bytes=32 time=111ms TTL=254
Reply from 62.3.86.42: bytes=32 time=140ms TTL=254
Reply from 62.3.86.42: bytes=32 time=51ms TTL=254
Reply from 62.3.86.42: bytes=32 time=214ms TTL=254
Reply from 62.3.86.42: bytes=32 time=99ms TTL=254
Reply from 62.3.86.42: bytes=32 time=128ms TTL=254
Reply from 62.3.86.42: bytes=32 time=156ms TTL=254
Reply from 62.3.86.42: bytes=32 time=122ms TTL=254
Reply from 62.3.86.42: bytes=32 time=251ms TTL=254
Reply from 62.3.86.42: bytes=32 time=101ms TTL=254
Reply from 62.3.86.42: bytes=32 time=144ms TTL=254
Reply from 62.3.86.42: bytes=32 time=53ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=150ms TTL=254
Reply from 62.3.86.42: bytes=32 time=272ms TTL=254
Reply from 62.3.86.42: bytes=32 time=51ms TTL=254
Reply from 62.3.86.42: bytes=32 time=51ms TTL=254
Reply from 62.3.86.42: bytes=32 time=122ms TTL=254
Reply from 62.3.86.42: bytes=32 time=223ms TTL=254
Reply from 62.3.86.42: bytes=32 time=51ms TTL=254
Reply from 62.3.86.42: bytes=32 time=51ms TTL=254
Reply from 62.3.86.42: bytes=32 time=226ms TTL=254
Reply from 62.3.86.42: bytes=32 time=53ms TTL=254
Reply from 62.3.86.42: bytes=32 time=151ms TTL=254
Reply from 62.3.86.42: bytes=32 time=163ms TTL=254
Reply from 62.3.86.42: bytes=32 time=54ms TTL=254
Reply from 62.3.86.42: bytes=32 time=80ms TTL=254
Reply from 62.3.86.42: bytes=32 time=62ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=57ms TTL=254
Reply from 62.3.86.42: bytes=32 time=77ms TTL=254
Reply from 62.3.86.42: bytes=32 time=201ms TTL=254
Reply from 62.3.86.42: bytes=32 time=80ms TTL=254
Reply from 62.3.86.42: bytes=32 time=55ms TTL=254
Reply from 62.3.86.42: bytes=32 time=55ms TTL=254
Reply from 62.3.86.42: bytes=32 time=63ms TTL=254
Reply from 62.3.86.42: bytes=32 time=149ms TTL=254
Reply from 62.3.86.42: bytes=32 time=88ms TTL=254
Reply from 62.3.86.42: bytes=32 time=157ms TTL=254
Reply from 62.3.86.42: bytes=32 time=170ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=139ms TTL=254
Reply from 62.3.86.42: bytes=32 time=250ms TTL=254
Reply from 62.3.86.42: bytes=32 time=57ms TTL=254
Reply from 62.3.86.42: bytes=32 time=51ms TTL=254
Reply from 62.3.86.42: bytes=32 time=102ms TTL=254
Reply from 62.3.86.42: bytes=32 time=170ms TTL=254
Reply from 62.3.86.42: bytes=32 time=199ms TTL=254
Reply from 62.3.86.42: bytes=32 time=178ms TTL=254
Reply from 62.3.86.42: bytes=32 time=191ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=95ms TTL=254
Reply from 62.3.86.42: bytes=32 time=52ms TTL=254
Reply from 62.3.86.42: bytes=32 time=93ms TTL=254
Reply from 62.3.86.42: bytes=32 time=217ms TTL=254
Reply from 62.3.86.42: bytes=32 time=162ms TTL=254
Reply from 62.3.86.42: bytes=32 time=188ms TTL=254
Reply from 62.3.86.42: bytes=32 time=51ms TTL=254
Reply from 62.3.86.42: bytes=32 time=83ms TTL=254

Ping statistics for 62.3.86.42:
Packets: Sent = 114, Received = 114, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 272ms, Average = 125ms
Control-C
^C
C:\Users\helan>

now on laptop after a reboot
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\helan>ping -t 62.3.86.42

Pinging 62.3.86.42 with 32 bytes of data:
Reply from 62.3.86.42: bytes=32 time=138ms TTL=254
Reply from 62.3.86.42: bytes=32 time=240ms TTL=254
Reply from 62.3.86.42: bytes=32 time=180ms TTL=254
Reply from 62.3.86.42: bytes=32 time=94ms TTL=254
Reply from 62.3.86.42: bytes=32 time=147ms TTL=254
Reply from 62.3.86.42: bytes=32 time=233ms TTL=254
Reply from 62.3.86.42: bytes=32 time=176ms TTL=254
Reply from 62.3.86.42: bytes=32 time=201ms TTL=254
Reply from 62.3.86.42: bytes=32 time=136ms TTL=254
Reply from 62.3.86.42: bytes=32 time=254ms TTL=254
Reply from 62.3.86.42: bytes=32 time=212ms TTL=254
Reply from 62.3.86.42: bytes=32 time=101ms TTL=254
Reply from 62.3.86.42: bytes=32 time=118ms TTL=254
Reply from 62.3.86.42: bytes=32 time=206ms TTL=254
Reply from 62.3.86.42: bytes=32 time=202ms TTL=254
Reply from 62.3.86.42: bytes=32 time=196ms TTL=254
Reply from 62.3.86.42: bytes=32 time=173ms TTL=254
Reply from 62.3.86.42: bytes=32 time=156ms TTL=254
Reply from 62.3.86.42: bytes=32 time=83ms TTL=254

Ping statistics for 62.3.86.42:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 254ms, Average = 170ms
Control-C
^C
C:\Users\helan>

Okay, I just spoken to Zen who made me do a quiet line test and they did some tests. Their end showed no problems and I didn't hear any crackling on my phone line doing the test but the Zen guy said when talking to me he could hear lots of static cracks and pops. His recommendation was to pull the phone line out for an hour and see how the internet/connection is.

The phone has been out for nearly an hour and I did a speed test on here
http://www.thinkbroadband.com/speedtest/results.html...

There was/is a warning about congestion but not sure if that means at the exchange or at this house (we have 8 things on the network - iphones/ipads/printer/2 pc's etc)

After a router reboot it seems to be back to normal now although my laptop has just come up saying "windows has detected an IP address conflict". Could that be the problem? Although the laptop is rarely on but maybe it's something else conflicting? The printer or something similar?

How do I rectify that problem? Not sure how to assign IP addresses to things. It might be getting a bit technical for me now LOL

And you are sure no one was downloading or uploading a lot of data at that time ?

In reply to a post by MrSaffron:

And you are sure no one was downloading or uploading a lot of data at that time ?

positive there was only me here at that time, well pat was here but fast asleep

In which case is a sign of exchange or backhaul congestion.

If was a dsl issue would expect the packet loss to be pretty constant.

If the exchange is just a bt wholesale one rather than one with zen backhaul them congestion is something that people hace been seeing on various providers and gets fixed after a few weeks

For IP.
Just switch off all machines including router.
Restart router and leave few minutes.
switch on machine one at a time and confirm internet connection, before switching on next

Or for one machine only
https://www.cs.cmu.edu/~help/networking/IP_renew.html

Edited by flippery (Sat 25-Oct-14 20:37:04)