Fibre help

Just wondering if anyone can point us in the right direction, Plusnet have been good at trying to sort this issue, but any help appreciated.

We had fibre installed in July and we got 38MB, and then when the 80/20 trial was available we got up to around 46MB.

I think our problem started when Plusnet changed the packages and made the 80/20 a permanent product, since then our service has been going downhill.

The speed seems to be fluctuating, from 45MB, down to 5.5MB on Plusnets own speed tester, we have had BT out numerous times, they seem to be picking up numerous minor niggling faults, cables in water in the cabinet, slight interference, but nothing major that they have told us about.

BT where out yesterday, he looked at the copper wire on the pole, do not know if he changed it, but he may have done, made some phone calls, and was told by his end that the best we could get was 25MB, this was based on us being 600mtrs from the cabinet, the BTW system says we should get 44MB, and we have had and held 44MB before.

When he left, we where synced at 42MB, now the strange thing is we always are, but hours after they leave our profile at BT always changes to 31.36MB, and today has been a nightmare, webpages taking several minutes to load, and our download has averaged around 13MB, we have had the router changed and two different Openreach modems, but all to no avail, this has been going on now for around five weeks.

I am at my wits end, and the only thing I can link it to is when Plusnet changed there tariffs, anyone any ideas what we could try?

Lisa

Plusnet Speed checks


Today 23:13 12354 kbps (1.54MB/s) 1646 kbps (206kB/s) Share
Today 22:47 11712 kbps (1.46MB/s) 582 kbps (72.8kB/s) Share
Today 21:59 5586 kbps (698kB/s) 810 kbps (101kB/s) Share
Today 21:59 6159 kbps (770kB/s) 539 kbps (67.4kB/s) Share
Today 08:55 13048 kbps (1.63MB/s) 612 kbps (76.5kB/s) Share
Today 08:15 11443 kbps (1.43MB/s) 1769 kbps (221kB/s) Share
Today 08:09 13464 kbps (1.68MB/s) 772 kbps (96.5kB/s) Share
Today 08:06 13224 kbps (1.65MB/s) 1745 kbps (218kB/s) Share
Today 08:04 13260 kbps (1.66MB/s) 1767 kbps (221kB/s) Share
Today 07:53 13525 kbps (1.69MB/s) 1762 kbps (220kB/s) Share
Today 07:49 13281 kbps (1.66MB/s) 604 kbps (75.5kB/s) Share
Yesterday 19:41 14680 kbps (1.84MB/s) 2480 kbps (310kB/s) Share
Yesterday 19:37 16801 kbps (2.1MB/s) 2287 kbps (286kB/s) Share
Yesterday 19:32 16865 kbps (2.11MB/s) 600 kbps (75kB/s) Share
Yesterday 09:03 28535 kbps (3.57MB/s) 8339 kbps (1.04MB/s) Share
Sunday 20:06 30095 kbps (3.76MB/s) 7375 kbps (922kB/s) Share
Saturday 17:38 28866 kbps (3.61MB/s) 7201 kbps (900kB/s) Share
Friday 18:32 28094 kbps (3.51MB/s) 8219 kbps (1.03MB/s) Share
Friday 18:16 36002 kbps (4.5MB/s) 1203 kbps (150kB/s) Share
Sep 17, 16:17 27399 kbps (3.42MB/s) 7648 kbps (956kB/s) Share
Sep 10, 14:23 37166 kbps (4.65MB/s) 5870 kbps (734kB/s) Share
Sep 9, 18:35 11276 kbps (1.41MB/s) 8473 kbps (1.06MB/s) Share
Sep 9, 00:20 40939 kbps (5.12MB/s) 8450 kbps (1.06MB/s) Share
Sep 8, 18:49 40949 kbps (5.12MB/s) 8109 kbps (1.01MB/s) Share
Sep 8, 18:10 37689 kbps (4.71MB/s) 8033 kbps (1MB/s) Share
Sep 7, 11:42 34114 kbps (4.26MB/s) 8909 kbps (1.11MB/s) Share
Sep 7, 11:29 37762 kbps (4.72MB/s) 8892 kbps (1.11MB/s) Share
Aug 31, 23:54 33574 kbps (4.2MB/s) 7668 kbps (959kB/s) Share
Aug 31, 13:44 36775 kbps (4.6MB/s) 7665 kbps (958kB/s) Share
Aug 31, 12:40 37375 kbps (4.67MB/s) 7697 kbps (962kB/s) Share

Speed tests on their own can't be relied upon as so many factors can affect them.

BT's IP Profile can't be 100% relied upon either as it only changes when a new PPP session is initiated, so can end up being stuck at either too high or too low a level.

You really need to unlock, or obtain a spare modem & unlock it to be able to see your connection stats & also identify exactly how often the connection resyncs (possibly detecting a time of day/weather changes pattern).

Plusnet's own logs don't always pick up on how often a connection resyncs as many of the "on the fly" resyncs are too quick to be detected & they don't force a new PPP session.

DLM sees them though & clobbers your connection speeds in response.

If, & only if, your connection is genuinely stable with lowish error counts can you push this back as a potential routing, capacity or profiling problem.

I suspect though that your connection is exhibiting the symptoms of an intermittent fault that is not detected via various BT line tests, or it could simply be that Plusnet's line profile needs adjusting.

What is your current line speed as reported by Plusnet, & have they detected many disconnections?

I experienced the intermittent faults issues & it took 11 months to resolve (once we eventually got over the hurdle of both Plusnet & BT claiming my connection was physically perfect & was "performing within acceptable limits").

mybroadbandspeed is the most unreliable tester there is - especially for those on fibre!

In reply to a post by jelv:

mybroadbandspeed is the most unreliable tester there is - especially for those on fibre!

BT speedtester

Download speedachieved during the test was - 18.61 Mbps
For your connection, the acceptable range of speedsis 12 Mbps-31.36 Mbps .
Additional Information:
IP Profile for your line is - 31.36 Mbps

Web browsing is still nearly non existent, Plusnet still waiting for the fault report of BT

Look at my Speedtest below, that is what it should be like

L

In reply to a post by lisaj:

In reply to a post by jelv:

mybroadbandspeed is the most unreliable tester there is - especially for those on fibre!

BT speedtester

Download speedachieved during the test was - 18.61 Mbps
For your connection, the acceptable range of speedsis 12 Mbps-31.36 Mbps .
Additional Information:
IP Profile for your line is - 31.36 Mbps

Web browsing is still nearly non existent, Plusnet still waiting for the fault report of BT

Look at my Speedtest below, that is what it should be like

L

The BT test was done connected with a short cable to the TEST socket?

(edit, just noticed the poor speed logs.)

Edited by Apprentice (Wed 26-Sep-12 18:57:18)

In reply to a post by Apprentice:

In reply to a post by lisaj:

In reply to a post by jelv:

mybroadbandspeed is the most unreliable tester there is - especially for those on fibre!

BT speedtester

Download speedachieved during the test was - 18.61 Mbps
For your connection, the acceptable range of speedsis 12 Mbps-31.36 Mbps .
Additional Information:
IP Profile for your line is - 31.36 Mbps

Web browsing is still nearly non existent, Plusnet still waiting for the fault report of BT

Look at my Speedtest below, that is what it should be like

L

The BT test was done connected with a short cable to the TEST socket?

(edit, just noticed the poor speed logs.)

We have the brand new BT socket, installed a few weeks ago, the speed is all over the place all day long, constantly around 13MB on speedtest.net and even lower using the BT over 24MB beta test.

My main concern is web browsing is dam near impossible, websites are taking over a minute to load in some circumstances, others are just really lagging, Plusnet bless them have just quoted us the SLA as BT have still not reported on the problem, the kids at the moment trying to do there homework is a nightmare with the browsing speed.

The tests are being done with a short Ethernet cable to the router

Latest Namesco (BBMAX) speedtest

Download Speed: 9535 kbps (1191.9 KB/sec ) Upload Speed: 1694 kbps (211.8 KB/sec )
L

Edited by deleted (Wed 26-Sep-12 19:10:23)

Web browsing should not be impossible with an 18Meg throughput.

Have you tried tools like ping to see what packet loss is like?

ping -t www.plus.net in a command window and what do you see?

In reply to a post by MrSaffron:

Web browsing should not be impossible with an 18Meg throughput.

Have you tried tools like ping to see what packet loss is like?

ping -t www.plus.net in a command window and what do you see?

Constant 19/20 milliseconds

Lisa

In reply to a post by MrSaffron:

Web browsing should not be impossible with an 18Meg throughput.

Have you tried tools like ping to see what packet loss is like?

ping -t www.plus.net in a command window and what do you see?

tracert to BBC

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

tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.90]
over a maximum of 30 hops:

1 112 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 14 ms 13 ms 14 ms lo0-central10.pcl-ag02.plus.net [195.166.128.183
]
3 13 ms 12 ms 19 ms link10-central10.pcl-gw02.plus.net [84.93.249.50
]
4 13 ms 13 ms 12 ms xe-0-2-0.pcl-cr02.plus.net [212.159.1.2]
5 13 ms 14 ms 13 ms ae1.ptw-cr02.plus.net [195.166.129.2]
6 13 ms 13 ms 12 ms ae2.ptw-cr01.plus.net [195.166.129.4]
7 13 ms 13 ms 13 ms kingston-gw.thdo.bbc.co.uk [212.58.239.6]
8 * * * Request timed out.
9 14 ms 14 ms 15 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
10 17 ms 17 ms 14 ms 132.185.255.165
11 14 ms 13 ms 14 ms bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]

Trace complete.

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

tracert www.evertonfc.com

Tracing route to rb-efc-main-200663015.eu-west-1.elb.amazonaws.com [54.247.174.1
84]
over a maximum of 30 hops:

1 132 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 16 ms 17 ms 13 ms lo0-central10.pcl-ag02.plus.net [195.166.128.183
]
3 13 ms 13 ms 13 ms link8-central10.pcl-gw02.plus.net [84.93.249.46]

4 13 ms 13 ms 12 ms xe-0-2-0.pcl-cr02.plus.net [212.159.1.2]
5 13 ms 12 ms 13 ms ae2.pcl-cr01.plus.net [195.166.129.6]
6 13 ms 12 ms 13 ms xe-11-2-0.edge3.London2.Level3.net [212.187.201.
213]
7 19 ms 13 ms 16 ms ae-0-11.edge4.London2.Level3.net [4.69.200.126]

8 13 ms 13 ms 13 ms ae-3-3.ebr1.London1.Level3.net [4.69.141.189]
9 36 ms 24 ms 24 ms ae-1-8.bar1.Dublin1.Level3.net [4.69.153.230]
10 25 ms 24 ms 24 ms 213.242.106.86
11 26 ms 25 ms 25 ms 178.236.0.128
12 25 ms 26 ms 26 ms 178.236.0.125
13 27 ms 28 ms 36 ms ec2-79-125-0-132.eu-west-1.compute.amazonaws.com
[79.125.0.132]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

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

ping -t www.evertonfc.com

Pinging rb-efc-main-200663015.eu-west-1.elb.amazonaws.com [46.137.177.216] with
32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

>ping -t www.aol.co.uk

Pinging portal.aol.eu.aol.akadns.net [205.188.18.209] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

>ping -t www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.246.94] with 32 bytes of data:
Reply from 212.58.246.94: bytes=32 time=30ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=13ms TTL=54
Reply from 212.58.246.94: bytes=32 time=13ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54
Reply from 212.58.246.94: bytes=32 time=14ms TTL=54

Edited by deleted (Wed 26-Sep-12 22:54:59)

In reply to a post by lisaj:

1 112 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]

Takes a long time to get a response from the 1st hop.

In reply to a post by lisaj:

When he left, we where synced at 42MB, now the strange thing is we always are, but hours after they leave our profile at BT always changes to 31.36MB

This part is likely to be a consequence of the way the cabinet's DLM system works.

When the BT engineer changes things, he'll get the operations centre to reset your line - which will reset DLM back to its original "go as fast as you can, and monitor for errors" setting.

DLM will monitor, and (presumably, in your case) actually detect a high error rate. It will then switch profiles to turn on interleaving and (as a consequence) the forward-error-correction process.

This, in turn, steals some of your bandwidth to transfer the extra parity information that allows the forward-error-correction process to work. It gives you a more stable connection, at the expense of raw speed. Worst case I've seen is that this overhead consumes around 23% of your original throughput.

If errors continue, then DLM can reduce your profile further, limiting the speed as well as turning interleaving on.

Ordinarily, DLM will make the first change around 48 hours after being reset. It can act faster than this (when slowing things down) if it detects too many errors. On the other hand it is *very* slow the other way around: If things are fixed, it can take from 3 weeks upwards to get the profile raised again.

I always think it is a bit of a swizz. The BT engineer can leave the property with the modem appearing to run far faster than it will be in 2 days - while the consumer can see the speed immediately, he *can't* see the error rate, so he thinks it is fixed. Meanwhile, when things go wrong in 48 hours, it's going to take days to get an engineer back again.

In reply to a post by lisaj:

Constant 19/20 milliseconds

Have you tried setting up a TBB "quality meter" from here?

This keeps a ping running all the time, which allows you to see if your line is suffering from packet loss. It can also tell you when a disconnection happens (if between 4AM and 8AM, there's a good chance that DLM changed the profile), and lets you see if latency changes (again, can be because DLM changed profile).

From my last comment, you might especially find it useful to see behaviour next time an engineer comes to fix things - and especially to see what happens in the 48 hours after they go!

For example, my first line had errors in the first 48 hours, showing around 5% packet loss. DLM intervened by adding interleaving - and I saw a disconnection, an increase in latency, and a decrease in packet loss. My line was reset, and went through an identical process the second time.

I'd post a link, but the historical data for the BQM meters seems to have disappeared, and I can't get the graphs any more.

But the tbb BQM is only designed for fixed IP addresses, not dynamic which PN ones are unless you've paid for fixed. (Maybe that's how you lost your old graphs?)

In reply to a post by WWWombat:

In reply to a post by lisaj:

Constant 19/20 milliseconds

Have you tried setting up a TBB "quality meter" from here?

This keeps a ping running all the time, which allows you to see if your line is suffering from packet loss. It can also tell you when a disconnection happens (if between 4AM and 8AM, there's a good chance that DLM changed the profile), and lets you see if latency changes (again, can be because DLM changed profile).

From my last comment, you might especially find it useful to see behaviour next time an engineer comes to fix things - and especially to see what happens in the 48 hours after they go!

For example, my first line had errors in the first 48 hours, showing around 5% packet loss. DLM intervened by adding interleaving - and I saw a disconnection, an increase in latency, and a decrease in packet loss. My line was reset, and went through an identical process the second time.

I'd post a link, but the historical data for the BQM meters seems to have disappeared, and I can't get the graphs any more.

Post edited to hide my embarrassment lol
Lisa

Edited by deleted (Thu 27-Sep-12 09:51:21)

Total red means your router is not responding to pings.

You probably need to log into the router and enable respond to Internet WAN ping/icmp

In reply to a post by MrSaffron:

Total red means your router is not responding to pings.

You probably need to log into the router and enable respond to Internet WAN ping/icmp

Whoops, just changed it in the router

Thanks Andrew

Lisa

That just means the router is giving priority to routing traffic and not responding to ICMP traffic on its local interface.

Nothing to panic about on its own, only an issue if we see pings varying further down the line.

Well, is it a thomson/technicolor device?

Ours is a technicolor router

L

Yes, the first hop enormous ping was a feature from the good old Speedtouch days. Glad to see it's still present now they're called Technicolor.

Presumably, you've tried rebooting modem and router?

In reply to a post by BatBoy:

Yes, the first hop enormous ping was a feature from the good old Speedtouch days. Glad to see it's still present now they're called Technicolor.

Presumably, you've tried rebooting modem and router?

I have, despite Plusnet advising us not too, no change at all

Currently just the same, very slow browsing speed, and still at around 13MB

Lisa

Have you changed the DNS on the PC to Google or OpenDNS?

In reply to a post by BatBoy:

Have you changed the DNS on the PC to Google or OpenDNS?

No, it just has the standard Plusnet DNS on it

Lisa

My Broadband Ping

Do you want to try changing the DNS? If so, I suggest you do it on the PC just as a test http://use.opendns.com/

When you say very slow browsing speed, can you expand on what you mean.

Why?

Because a download speed test of 13 Mbps is more than enough to give a very good web browsing experience. So is the issue that web pages take ages to appear, or that large files you download are slow to arrive?

For example on my slow 6 Meg link a complete refresh of http://www.bbc.co.uk/news/ is 4 to 5 seconds. How slow/fast on your connection?

In reply to a post by MrSaffron:

When you say very slow browsing speed, can you expand on what you mean.

Why?

Because a download speed test of 13 Mbps is more than enough to give a very good web browsing experience. So is the issue that web pages take ages to appear, or that large files you download are slow to arrive?

For example on my slow 6 Meg link a complete refresh of http://www.bbc.co.uk/news/ is 4 to 5 seconds. How slow/fast on your connection?

I clicked on that link, and part of the page appeared with 4-5 seconds, but for the waiting for www.bbc.co.uk to go away and for all the pictures to load was around 40 seconds, this is after batboys suggestion of using opendns and after flushing the DNS

lisa

If you just changed DNS servers on the router and have the standard Plusnet servers on the PC that won't have made any difference.

For changing the DNS servers on the router to have any effect you need to have the PC configured to use the router as the DNS server.

I always set the DNS servers on the PC and never use the router as a DNS server.

If you bring up the command prompt and type ipconfig /all then press enter you should see the primary DNS server in use

e.g. part of cmd prompt result

Windows IP Configuration

        Host Name . . . . . . . . . . . . : xxxxxxxx
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller
        Physical Address. . . . . . . . . : xxxxxxxxxxxxxxxxx
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : xxxxxxxxxxx
        Subnet Mask . . . . . . . . . . . : xxxxxxxxxxxxx
        Default Gateway . . . . . . . . . : xxxxxxxxxxx
        DHCP Server . . . . . . . . . . . : xxxxxxxxxxx
        DNS Servers . . . . . . . . . . . : 212.159.13.49
                                            156.154.70.1
                                            208.67.222.222

Edit > for me the primary DNS in use 212.159.13.49 is Plusnet

Edited by Apprentice (Thu 27-Sep-12 15:29:26)

In reply to a post by Apprentice:

If you bring up the command prompt and type ipconfig /all then press enter you should see the primary DNS server in use

e.g. part of cmd prompt result

Windows IP Configuration

        Host Name . . . . . . . . . . . . : xxxxxxxx
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Broadcast
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller
        Physical Address. . . . . . . . . : xxxxxxxxxxxxxxxxx
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : xxxxxxxxxxx
        Subnet Mask . . . . . . . . . . . : xxxxxxxxxxxxx
        Default Gateway . . . . . . . . . : xxxxxxxxxxx
        DHCP Server . . . . . . . . . . . : xxxxxxxxxxx
        DNS Servers . . . . . . . . . . . : 212.159.13.49
                                            156.154.70.1
                                            208.67.222.222

Edit > for me the primary DNS in use 212.159.13.49 is Plusnet

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

Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : VIA Rhine II Compatible Fast Ethernet Adapter
Physical Address. . . . . . . . . : xxxxxxxxxxxxxx
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : XXXXXXXXXXXXXXXX(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.64(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 27 September 2012 08:41:38
Lease Expires . . . . . . . . . . : 28 September 2012 11:56:22
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : XXXXXXXXXX
DHCPv6 Client DUID. . . . . . . . :XXXXXXXXXXXX

DNS Servers . . . . . . . . . . . : 208.67.222.222 < I know these are OpenDNS
208.67.220.220
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{6E79A6E4-9E0E-4F97-89B6-CF5F96530DAC}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : XXXXXXXXXXXX(Preferred)
Link-local IPv6 Address . . . . . : XXXXXXXXXXXXXXXXX(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.lan:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

I would suggest trying disabling ipv6

http://windows7themes.net/disable-ipv6-windows-7.html and follow the section titled
Disable IPv6 for LAN adapter & interfaces

Then check again, just in case the issue is ipv6 introducing an issue. Have seen oddities very occassionally when ipv6 is enabled.

I'd avoid using OpenDNS as a primary resolver and stick to using our DNS servers whilst you try troubleshooting the problem. It's one less variable to consider.

One thing I've not seen asked is whether or not you're using a wired or wireless connection? (although I'd have expected the extended ping test to have highlighted a problem if wireless connectivity was a factor).

Rgds,

In reply to a post by bpullen:

I'd avoid using OpenDNS as a primary resolver and stick to using our DNS servers whilst you try troubleshooting the problem. It's one less variable to consider.

One thing I've not seen asked is whether or not you're using a wired or wireless connection? (although I'd have expected the extended ping test to have highlighted a problem if wireless connectivity was a factor).

Rgds,

Hi, thanks for the reply, It is a wired Ethernet connection, and I have just flushed DNS and reverted to the Plusnet Ones

L

I'd say it's Plusnets creepy throttling system gone crazy again.

Explain?

if it was ip profile mismatch then speedtests would show it, and the web page performance sounds a lot worse than you would expect for test results we have seen.

If the traffic management, again would expect the http based testers to be showing the poor performance you get from web page loads also.

In the past, I seem to remember Plusnet throttling their system so that speedtests were unaffected.

Probably because most testers use HTTP and they do little to no throttling of that

PN FTTC throttling is P2P and external FTP 8pm to 10pm only.

24 hours worth of DATA

My Broadband Ping

Lisa

That looks fine TBH. If you can provide me with a support ticket reference then I'll take a look next week if you like and see if I can offer any other suggestions?

Rgds,

Just out of pure interest, what does;
http://mcslhr.visualware.com/myspeed/myspeed_line_ca...
make of your line ?

Download speedachieved during the test was - 0.84 Mbps
For your connection, the acceptable range of speedsis 12 Mbps-31.36 Mbps .
Additional Information:
IP Profile for your line is - 31.36 Mbps

Upload speed achieved during the test was - 0Mbps
Additional Information:
Upstream Rate IP profile on your line is - 20 Mbps

What joy!!!

Lisa

Do you have a ticket reference you can provide me with?

If not I'd suggest raising a fault at http://faults.plus.net and then if you can provide me with the ticket numvber I'd happily look into it.

Chris