cancel
Showing results for 
Search instead for 
Did you mean: 

Constipated FTTC Help. IN dial up lane

Community Veteran
Posts: 1,817
Thanks: 11
Registered: 30-07-2007

Constipated FTTC Help. IN dial up lane

My FTTC has slowed to slower than tomato sauce moving from the bottom of the bottle to the opening.
I have rebooted buth router and modem. BT wholesale sped test is showing as normal 27 Mbps down and 6.35 Mbps up.
Trace routes are showing lots of time outs.  Each Trace Rt times out lots of times. IS the net just dire at present or is there an issue somewhere else. i.e with myself or PN.
I can no longer find the gateway checker on the PN site to advise which gateway I am attached to.
{edit} I have just found that I am on: gateway ptn-ag04.. also that in the last month my exchange has apparently had a major outage but no further details listed {edit}
All advise much appreciated as this is dire.
Podman
Tracing route to www.bbc.net.uk [212.58.244.70]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2     *        *        *     Request timed out.
 3    26 ms    26 ms    26 ms  lo0-central10.ptn-ag04.plus.net [195.166.128.193
]
 4    26 ms    25 ms    25 ms  link-a-central10.ptn-gw01.plus.net [212.159.2.14
0]
 5    25 ms    26 ms    40 ms  lts4.bt622-9.plus.net [212.159.0.116]
 6    26 ms    25 ms    26 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
 7     *        *        *     Request timed out.
 8     *        *        *     Request timed out.
 9    26 ms    26 ms    26 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10    27 ms    26 ms    26 ms  132.185.255.149
11    26 ms    25 ms    26 ms  bbc-vip115.telhc.bbc.co.uk [212.58.244.70]
Trace complete.

C:\Windows\system32>tracert www.argos.co.uk
Tracing route to e624.b.akamaiedge.net [2.21.210.168]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2     *        *        *     Request timed out.
 3    29 ms    27 ms    32 ms  lo0-central10.ptn-ag04.plus.net [195.166.128.193
]
 4    26 ms    26 ms    27 ms  link-a-central10.ptn-gw01.plus.net [212.159.2.14
0]
 5    26 ms    26 ms    26 ms  lts4.bt622-9.plus.net [212.159.0.116]
 6     *        *        *     Request timed out.
 7    26 ms    26 ms    25 ms  2.21.210.168
Trace complete.
C:\Windows\system32>tracert www.plus.net
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  192.168.0.1
 2     *        *        *     Request timed out.
 3   105 ms    86 ms    27 ms  lo0-central10.ptn-ag04.plus.net [195.166.128.193
]
 4    26 ms    26 ms    26 ms  link-a-central10.ptn-gw01.plus.net [212.159.2.14
0]
 5    36 ms    25 ms    25 ms  lts4.bt622-9.plus.net [212.159.0.116]
 6    26 ms    26 ms    25 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
 7    34 ms    34 ms    34 ms  gi5-1.peh-cr02.plus.net [84.93.232.61]
 8    34 ms    36 ms    33 ms  po5.peh-cr01.plus.net [84.93.232.16]
 9    34 ms    37 ms    34 ms  vlan2657.peh-elb01.plus.net [84.93.232.44]
10    37 ms    34 ms    37 ms  portal.plus.net [212.159.8.2]
Trace complete.
C:\Windows\system32>
9 REPLIES
Community Veteran
Posts: 1,817
Thanks: 11
Registered: 30-07-2007

Re: Constipated FTTC Help. IN dial up lane

Different pc linked directly to BT modem and I am still crawling along.

Tracerts and pings below. Any help or suggestions.
Tracing route to www.bbc.net.uk [212.58.244.70]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    *        *        *    Request timed out.
  3    25 ms    25 ms    25 ms  lo0-central10.ptw-ag01.plus.net [195.166.128.195
]
  4    25 ms    25 ms    25 ms  link-a-central10.ptw-gw01.plus.net [212.159.2.14
4]
  5    25 ms    25 ms    24 ms  ****.core.access.plus.net [212.*********]
  6    25 ms    26 ms    56 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    25 ms    25 ms    25 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10    28 ms    25 ms    25 ms  132.185.255.149
11    25 ms    25 ms    24 ms  bbc-vip115.telhc.bbc.co.uk [212.58.244.70]
Trace complete.
C:\Users\minipc>tracert www.amazon.co.uk
Tracing route to www.amazon.co.uk [178.236.7.220]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    *        *        *    Request timed out.
  3    34 ms    39 ms    32 ms  lo0-central10.ptw-ag01.plus.net [195.166.128.195
]
  4    25 ms    25 ms    25 ms  link-a-central10.ptw-gw01.plus.net [212.159.2.14
4]
  5    25 ms    25 ms    25 ms  ****.core.access.plus.net [212.********]
  6    *        *        *    Request timed out.
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.
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.
C:\Users\minipc>ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.246.91] with 32 bytes of data:
Reply from 212.58.246.91: bytes=32 time=25ms TTL=56
Reply from 212.58.246.91: bytes=32 time=26ms TTL=56
Reply from 212.58.246.91: bytes=32 time=25ms TTL=56
Reply from 212.58.246.91: bytes=32 time=25ms TTL=56
Ping statistics for 212.58.246.91:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 26ms, Average = 25ms
C:\Users\minipc>ping www.amazon.co.uk
Pinging www.amazon.co.uk [178.236.7.220] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 178.236.7.220:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\minipc>ping www.plus.net
Pinging portal.plus.net [212.159.8.2] with 32 bytes of data:
Reply from 212.159.8.2: bytes=32 time=36ms TTL=248
Reply from 212.159.8.2: bytes=32 time=34ms TTL=248
Reply from 212.159.8.2: bytes=32 time=34ms TTL=248
Reply from 212.159.8.2: bytes=32 time=33ms TTL=248
Ping statistics for 212.159.8.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 36ms, Average = 34ms
C:\Users\minipc>tracert www.plus.net
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    *        *        *    Request timed out.
  3    26 ms    26 ms    26 ms  lo0-central10.ptw-ag01.plus.net [195.166.128.195
]
  4    25 ms    25 ms    26 ms  link-a-central10.ptw-gw01.plus.net [212.159.2.14
4]
  5    25 ms    25 ms    25 ms  ****.core.access.plus.net [212.********]
  6    25 ms    25 ms    25 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
  7    32 ms    34 ms    36 ms  gi5-1.peh-cr02.plus.net [84.93.232.61]
  8    32 ms    32 ms    32 ms  po5.peh-cr01.plus.net [84.93.232.16]
  9    35 ms    33 ms    32 ms  vlan2657.peh-elb01.plus.net [84.93.232.44]
10    35 ms    32 ms    33 ms  portal.plus.net [212.159.8.2]
Trace complete.
nanotm
Pro
Posts: 5,682
Thanks: 111
Fixes: 1
Registered: 11-02-2013

Re: Constipated FTTC Help. IN dial up lane

can you do a test at BTW speed tester and use the further diagnostics options (you have to put in your phone number)
then post the results from that, it will show your line's ip profile which might help indicate a problem
just because your paranoid doesn't mean they aren't out to get you
Community Veteran
Posts: 6,313
Thanks: 86
Fixes: 3
Registered: 08-01-2008

Re: Constipated FTTC Help. IN dial up lane

What is 192.168.0.1?  Normally I'd assume it's your router but I don't know how that works on the direct connection to the modem.
I'd expect the second hop (immediately after the router when it's used) to be the gateway (mine always is) but yours appears to be the third hop so what is the second hop that always times out?
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.178.1
  2    27 ms    23 ms    26 ms  lo0-central10.ptn-ag02.plus.net [195.166.128.191]
  3    23 ms    22 ms    22 ms  link-a-central10.ptn-gw01.plus.net [212.159.2.132]
  4    22 ms    61 ms    28 ms  112.core.access.plus.net [212.159.0.112]
  5    22 ms    22 ms    22 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
  6    30 ms    31 ms    30 ms  gi5-1.peh-cr02.plus.net [84.93.232.61]
  7    30 ms    31 ms    30 ms  po5.peh-cr01.plus.net [84.93.232.16]
  8    34 ms    30 ms    32 ms  vlan2657.peh-elb01.plus.net [84.93.232.44]
  9    31 ms    30 ms    31 ms  portal.plus.net [212.159.8.2]

My router is 192.168.178.1, the second hop shows my gateway is ptn-ag02
All the rest of your time-outs are consistent with what I get.
Call me 'w23'
At any given moment in the universe many things happen. Coincidence is a matter of how close these events are in space, time and relationship.
Opinions expressed in forum posts are those of the poster, others may have different views.
Community Veteran
Posts: 1,817
Thanks: 11
Registered: 30-07-2007

Re: Constipated FTTC Help. IN dial up lane

It shows all is well.

FAQ
Results Image not loaded

1. Best Effort Test:  -provides background information.
Download Speed
25.38 Mbps

0 Mbps 29.82 Mbps
Max Achievable Speed
Download speedachieved during the test was - 25.38 Mbps
For your connection, the acceptable range of speedsis 16 Mbps-29.82 Mbps .
Additional Information:
IP Profile for your line is - 29.82 Mbps
2. Upstream Test:  -provides background information.
Upload Speed
5.39 Mbps

0 Mbps 20 Mbps
Max Achievable Speed
Upload speed achieved during the test was - 5.39Mbps
Additional Information:
Upstream Rate IP profile on your line is - 20 Mbps
Community Veteran
Posts: 1,817
Thanks: 11
Registered: 30-07-2007

Re: Constipated FTTC Help. IN dial up lane

Here are my stats first with the router in line then direct connection to bt fttc modem. Both wired.
theses are my pings and trace rts connected via router then modem and the direct to modem.
Wired to router.
C:\Users\Alan>ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.244.71] with 32 bytes of data:
Reply from 212.58.244.71: bytes=32 time=25ms TTL=54
Reply from 212.58.244.71: bytes=32 time=24ms TTL=54
Reply from 212.58.244.71: bytes=32 time=25ms TTL=54
Reply from 212.58.244.71: bytes=32 time=25ms TTL=54
Ping statistics for 212.58.244.71:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 24ms, Maximum = 25ms, Average = 24ms
C:\Users\Alan>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.244.71]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    *        *        *    Request timed out.
  3    26 ms    25 ms    35 ms  lo0-central10.pcl-ag01.plus.net [195.166.128.182
]
  4    25 ms    24 ms    24 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.16
2]
  5    24 ms    24 ms    24 ms  194.core.access.plus.net [212.159.0.194]
  6    26 ms    34 ms    43 ms  ae1.ptw-cr02.plus.net [195.166.129.2]
  7    24 ms    24 ms    24 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  8    24 ms    40 ms    24 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    25 ms    24 ms    27 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
12    25 ms    28 ms    25 ms  132.185.255.149
13    24 ms    24 ms    25 ms  bbc-vip116.telhc.bbc.co.uk [212.58.244.71]
Trace complete.
C:\Users\Alan>ping www.bt.com
Pinging www.bt.com [62.239.237.2] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 62.239.237.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Alan>traceet www.bt.com
'traceet' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Alan>tracert www.bt.com
Tracing route to www.bt.com [62.239.237.2]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    *        *        *    Request timed out.
  3    26 ms    26 ms    24 ms  lo0-central10.pcl-ag01.plus.net [195.166.128.182
]
  4    24 ms    24 ms    25 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.16
0]
  5    24 ms    92 ms    26 ms  192.core.access.plus.net [212.159.0.192]
  6    25 ms    26 ms    24 ms  ae2.pcl-cr02.plus.net [195.166.129.7]
  7    24 ms    24 ms    24 ms  ae1.ptw-cr02.plus.net [195.166.129.2]
  8    26 ms    30 ms    31 ms  195.99.126.182
  9    28 ms    26 ms    27 ms  core2-te0-3-0-4.ealing.ukcore.bt.net [62.172.102
.22]
10    33 ms    33 ms    33 ms  core2-pos1-0.birmingham.ukcore.bt.net [62.172.10
3.85]
11    32 ms    31 ms    31 ms  iar1-gig5-5.birmingham.ukcore.bt.net [62.6.196.9
8]
12    33 ms    34 ms    34 ms  62.172.57.218
13    *        *        *    Request timed out.
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.
C:\Users\Alan>ping www.plus.net
Pinging portal.plus.net [212.159.9.2] with 32 bytes of data:
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Reply from 212.159.9.2: bytes=32 time=32ms TTL=248
Reply from 212.159.9.2: bytes=32 time=33ms TTL=248
Ping statistics for 212.159.9.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 33ms, Average = 32ms
C:\Users\Alan>tracert www.plus.net
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    *        *        *    Request timed out.
  3    25 ms    24 ms    24 ms  lo0-central10.pcl-ag01.plus.net [195.166.128.182
]
  4    24 ms    27 ms    25 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.16
0]
  5    60 ms    23 ms    24 ms  192.core.access.plus.net [212.159.0.192]
  6    24 ms    25 ms    25 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  7    25 ms    24 ms    25 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
  8    32 ms    32 ms    32 ms  gi5-1.peh-cr02.plus.net [84.93.232.61]
  9    32 ms    33 ms    37 ms  po5.peh-cr01.plus.net [84.93.232.16]
10    35 ms    33 ms    36 ms  vlan2657.peh-elb01.plus.net [84.93.232.44]
11    33 ms    36 ms    32 ms  portal.plus.net [212.159.8.2]
Trace complete.
Direct to modem
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Users\Alan>ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.244.71] with 32 bytes of data:
Reply from 212.58.244.71: bytes=32 time=25ms TTL=56
Reply from 212.58.244.71: bytes=32 time=25ms TTL=56
Reply from 212.58.244.71: bytes=32 time=25ms TTL=56
Reply from 212.58.244.71: bytes=32 time=25ms TTL=56
Ping statistics for 212.58.244.71:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 25ms, Average = 25ms
C:\Users\Alan>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.244.71]
over a maximum of 30 hops:
  1    25 ms    26 ms    25 ms  lo0-central10.ptw-ag03.plus.net [195.166.128.197
]
  2    25 ms    25 ms    25 ms  link-b-central10.ptw-gw02.plus.net [212.159.2.15
4]
  3    28 ms    26 ms    25 ms  246.core.access.plus.net [212.159.0.246]
  4    28 ms    25 ms    25 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  5    25 ms    44 ms    25 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  6    *        *        *    Request timed out.
  7    *        *        *    Request timed out.
  8    26 ms    25 ms    25 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
  9    26 ms    28 ms    25 ms  132.185.255.149
10    25 ms    25 ms    25 ms  bbc-vip116.telhc.bbc.co.uk [212.58.244.71]
Trace complete.
C:\Users\Alan>ping www.bt.com
Pinging www.bt.com [62.239.237.2] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 62.239.237.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Alan>tracert www.bt.com
Tracing route to www.bt.com [62.239.237.2]
over a maximum of 30 hops:
  1    25 ms    27 ms    25 ms  lo0-central10.ptw-ag03.plus.net [195.166.128.197
]
  2    25 ms    25 ms    25 ms  link-a-central10.ptw-gw01.plus.net [212.159.2.15
2]
  3    25 ms    25 ms    25 ms  244.core.access.plus.net [212.159.0.244]
  4    25 ms    25 ms    26 ms  195.99.126.138
  5    26 ms    27 ms    26 ms  core1-te0-15-0-10.ealing.ukcore.bt.net [109.159.
254.206]
  6    30 ms    29 ms    29 ms  core1-pos1-0.birmingham.ukcore.bt.net [62.172.10
3.81]
  7    30 ms    29 ms    29 ms  iar1-gig5-4.birmingham.ukcore.bt.net [62.6.196.9
4]
  8    32 ms    32 ms    31 ms  62.172.57.218
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.
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.
C:\Users\Alan>ping www.plys.net
Pinging varnish-x3-lb.develooper.com [207.171.7.43] with 32 bytes of data:
Reply from 207.171.7.43: bytes=32 time=154ms TTL=55
Reply from 207.171.7.43: bytes=32 time=154ms TTL=55
Reply from 207.171.7.43: bytes=32 time=154ms TTL=55
Reply from 207.171.7.43: bytes=32 time=154ms TTL=55
Ping statistics for 207.171.7.43:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 154ms, Maximum = 154ms, Average = 154ms
C:\Users\Alan>tracert www.plus.net
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
  1    26 ms    26 ms    32 ms  lo0-central10.ptw-ag03.plus.net [195.166.128.197
]
  2    25 ms    25 ms    25 ms  link-a-central10.ptw-gw01.plus.net [212.159.2.15
2]
  3    25 ms    25 ms    25 ms  244.core.access.plus.net [212.159.0.244]
  4    25 ms    25 ms    25 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
  5    34 ms    33 ms    33 ms  gi5-1.peh-cr02.plus.net [84.93.232.61]
  6    32 ms    35 ms    33 ms  po5.peh-cr01.plus.net [84.93.232.16]
  7    33 ms    36 ms    36 ms  vlan2657.peh-elb01.plus.net [84.93.232.44]
  8    33 ms    33 ms    35 ms  portal.plus.net [212.159.8.2]
Trace complete.
C:\Users\>
nanotm
Pro
Posts: 5,682
Thanks: 111
Fixes: 1
Registered: 11-02-2013

Re: Constipated FTTC Help. IN dial up lane

http://community.plus.net/forum/index.php/topic,118511.msg1026244.html#msg1026244
I posted my reply to you in the other thread but its still pertinent to both so i'll just leave this as a link for you
just because your paranoid doesn't mean they aren't out to get you
Community Veteran
Posts: 6,313
Thanks: 86
Fixes: 3
Registered: 08-01-2008

Re: Constipated FTTC Help. IN dial up lane

The 'direct to modem' tracerts look quite normal, how's the performance when connected this way?
Still the mystery of the second hop when connected via the router.
Can you confirm that 192.168.0.1 is the address of your router (if not, what is it)?
Call me 'w23'
At any given moment in the universe many things happen. Coincidence is a matter of how close these events are in space, time and relationship.
Opinions expressed in forum posts are those of the poster, others may have different views.
Community Veteran
Posts: 1,817
Thanks: 11
Registered: 30-07-2007

Re: Constipated FTTC Help. IN dial up lane

192.168.0.1 is the routers internal address. The very poor speeds are the same via router and via direct modem pppoe connection.
nanotm
Pro
Posts: 5,682
Thanks: 111
Fixes: 1
Registered: 11-02-2013

Re: Constipated FTTC Help. IN dial up lane

its probably some kind of share service hop,
i'm sure you mentioned it before but what router are you using ?
theres a problem with some routers in that changing there default ip address from 192.168.1.254 can cause problems because it's actually using both .254 and .255 in the network address pool .... if you mess about with the static ip address on things like the homehub it certainly does cause problems like this especially noticeable when any of the NAT/DMZ/port forwarding stuff is used and I know for certain that a few other makes of router use the same chipset complete with the same flaws
so you could try changing back to the default ip address on the router if that is the case, particularly as its timeing out before leaving your internal network, that will at least fix the problems beign caused by your router, I suspect theres a dns cache reason behind it being so poor when direct connected unless your specifying the dns server to be used in the ppp setup and try using more than one service (like only plusnet then only google then a mix of +net  and google servers)
if you haven't tried it already then do so just remember ot run a dns cache flush on the pc each time you change the server if nothing else it will rule those things out as being the reason behind the problem even if it doesn't fix the issue 
just because your paranoid doesn't mean they aren't out to get you