ADSL 2+ IP Profile Stuck.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- ADSL 2+ IP Profile Stuck.
Re: ADSL 2+ IP Profile Stuck.
13-11-2014 7:02 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Cheers for submitting the wireshark captures, we'll have a look at those as soon as possible and get back to you on the open ticket
Regarding wireless, the sure-fire way to rule that out is to connect to the router directly over Ethernet so please give that a go if you haven't already.
Bear in mind too that using channel 1 isn't a sure fire way of ensuring there's no overlap with other networks. The best way to do this is to use a WiFi scanner app (installing one on your phone or tablet would be the easiest way) to see which frequencies and channels are being used around you so that you can make a informed choice as to how to configure the channel setting on your router.
We have a help page here in case it's of any use to you: http://www.plus.net/support/broadband/wireless_broadband/wireless_signal.shtml
I can see from Chris' replies we've ruled out every other possibility.
Re: ADSL 2+ IP Profile Stuck.
13-11-2014 8:03 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Date -> Packetloss % -> Min -> Max -> Samples
12th Nov, 2014 00:00 0.00 0.00 0.00 1
12th Nov, 2014 01:00 0.09 0.09 0.09 1
12th Nov, 2014 02:00 0.00 0.00 0.00 1
12th Nov, 2014 03:00 0.00 0.00 0.00 1
12th Nov, 2014 04:00 0.00 0.00 0.00 1
12th Nov, 2014 05:00 0.00 0.00 0.00 1
12th Nov, 2014 06:00 0.00 0.00 0.00 1
12th Nov, 2014 07:00 0.05 0.05 0.05 1
12th Nov, 2014 08:00 0.00 0.00 0.00 1
12th Nov, 2014 09:00 0.05 0.05 0.05 1
12th Nov, 2014 10:00 0.00 0.00 0.00 1
12th Nov, 2014 14:00 0.00 0.00 0.00 1
12th Nov, 2014 15:00 0.00 0.00 0.00 1
12th Nov, 2014 16:00 0.09 0.09 0.09 1
12th Nov, 2014 17:00 0.00 0.00 0.00 1
12th Nov, 2014 18:00 0.00 0.00 0.00 1
12th Nov, 2014 19:00 0.07 0.07 0.07 1
12th Nov, 2014 20:00 0.19 0.19 0.19 1
12th Nov, 2014 22:00 0.00 0.00 0.00 1
12th Nov, 2014 23:00 0.00 0.00 0.00 1
13th Nov, 2014 00:00 0.09 0.09 0.09 1
13th Nov, 2014 01:00 0.32 0.32 0.32 1
13th Nov, 2014 02:00 0.00 0.00 0.00 1
13th Nov, 2014 03:00 0.00 0.00 0.00 1
13th Nov, 2014 04:00 0.00 0.00 0.00 1
13th Nov, 2014 05:00 0.00 0.00 0.00 1
13th Nov, 2014 06:00 0.00 0.00 0.00 1
13th Nov, 2014 07:00 0.00 0.00 0.00 1
13th Nov, 2014 09:00 0.00 0.00 0.00 1
13th Nov, 2014 10:00 0.00 0.00 0.00 1
13th Nov, 2014 11:00 0.05 0.05 0.05 1
13th Nov, 2014 12:00 0.00 0.00 0.00 1
13th Nov, 2014 13:00 0.00 0.00 0.00 1
13th Nov, 2014 14:00 0.00 0.00 0.00 1
13th Nov, 2014 15:00 0.00 0.00 0.00 1
13th Nov, 2014 16:00 0.00 0.00 0.00 1
13th Nov, 2014 17:00 0.00 0.00 0.00 1
13th Nov, 2014 18:00 0.00 0.00 0.00 1
Trace in Pingpath to Google
Tracing route to google.com [74.125.230.70]
over a maximum of 30 hops:
1 3 ms 5 ms 5 ms home.hillisde.hillside.home [192.168.1.254]
2 18 ms 25 ms 34 ms lo0-central10.ptn-ag02.plus.net [195.166.128.191]
3 102 ms 39 ms 42 ms link-b-central10.ptn-gw02.plus.net [212.159.2.134]
4 21 ms 19 ms 16 ms xe-1-2-0.ptw-cr02.plus.net [212.159.0.114]
5 22 ms 17 ms 20 ms 72.14.223.32
6 18 ms 17 ms 25 ms 209.85.252.188
7 17 ms 17 ms 19 ms 72.14.238.21
8 17 ms 19 ms 18 ms lhr14s23-in-f6.1e100.net [74.125.230.70]
Trace complete.
Tracing route to lhr08s03-in-f3.1e100.net [173.194.41.131]
over a maximum of 30 hops:
0 solidus1983-gmc.hillside.home [192.168.1.105]
1 home.hillisde.hillside.home [192.168.1.254]
2 lo0-central10.ptn-ag02.plus.net [195.166.128.191]
3 link-a-central10.ptn-gw01.plus.net [212.159.2.132]
4 xe-1-2-0.ptw-cr01.plus.net [212.159.0.112]
5 * * *
Computing statistics for 100 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 solidus1983-gmc.hillside.home [192.168.1.105]
0/ 100 = 0% |
1 5ms 0/ 100 = 0% 0/ 100 = 0% home.hillisde.hillside.home [192.168.1.254]
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% lo0-central10.ptn-ag02.plus.net [195.166.128.191]
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% link-a-central10.ptn-gw01.plus.net [212.159.2.132]
0/ 100 = 0% |
4 21ms 0/ 100 = 0% 0/ 100 = 0% xe-1-2-0.ptw-cr01.plus.net [212.159.0.112]
Trace complete.
Tracing route to easo.ea.com [159.153.234.54]
over a maximum of 30 hops:
0 solidus1983-gmc.hillside.home [192.168.1.105]
1 home.hillisde.hillside.home [192.168.1.254]
2 lo0-central10.ptn-ag02.plus.net [195.166.128.191]
3 link-b-central10.ptn-gw02.plus.net [212.159.2.134]
4 xe-1-2-0.ptw-cr02.plus.net [212.159.0.114]
5 ae2.ptw-cr01.plus.net [195.166.129.4]
6 te-4-2.car5.London1.Level3.net [217.163.45.249]
7 * * *
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 solidus1983-gmc.hillside.home [192.168.1.105]
0/ 100 = 0% |
1 9ms 0/ 100 = 0% 0/ 100 = 0% home.hillisde.hillside.home [192.168.1.254]
0/ 100 = 0% |
2 29ms 0/ 100 = 0% 0/ 100 = 0% lo0-central10.ptn-ag02.plus.net [195.166.128.191]
0/ 100 = 0% |
3 27ms 0/ 100 = 0% 0/ 100 = 0% link-b-central10.ptn-gw02.plus.net [212.159.2.134]
0/ 100 = 0% |
4 28ms 0/ 100 = 0% 0/ 100 = 0% xe-1-2-0.ptw-cr02.plus.net [212.159.0.114]
0/ 100 = 0% |
5 26ms 0/ 100 = 0% 0/ 100 = 0% ae2.ptw-cr01.plus.net [195.166.129.4]
1/ 100 = 1% |
6 72ms 1/ 100 = 1% 0/ 100 = 0% te-4-2.car5.London1.Level3.net [217.163.45.249]
Trace complete.
1 1 ms 1 ms 2 ms home.hillisde.hillside.home [192.168.1.254]
2 19 ms 20 ms 18 ms lo0-central10.ptn-ag02.plus.net [195.166.128.191]
3 18 ms 19 ms 17 ms link-b-central10.ptn-gw02.plus.net [212.159.2.134]
4 17 ms 18 ms 18 ms xe-1-2-0.ptw-cr02.plus.net [212.159.0.114]
5 17 ms 18 ms 61 ms ae2.ptw-cr01.plus.net [195.166.129.4]
6 * * 103 ms te-4-2.car5.London1.Level3.net [217.163.45.249]
7 * * * Request timed out.
8 94 ms 98 ms 97 ms 4.79.23.202
9 97 ms 92 ms 97 ms 159.153.93.2
10 94 ms 105 ms 96 ms 159.153.225.30
11 93 ms 94 ms 96 ms meav5-pub.pt.iad.ea.com [159.153.226.105]
12 93 ms 102 ms 106 ms easo.ea.com [159.153.234.54]
Trace complete.
The above screenshot was on this server: http://battlelog.battlefield.com/bf4/servers/show/pc/0437da91-a67c-42b0-ac1a-033beff42e1a/5-5-forums... which is UK
I have changed DNS back to auto on Router as this is the last thing setting wised that can be changed so will keep an eye out.
@_Adam_Walker_ as with everything before i come on here i try everything possible that includes going from WiFi back to Wired or in somecases Using both at the same time in Load Balance mode.
As for Wifi Channel in the close where i live only the following channels are used by others 6 9 11 which makes using channel 1 perfect to insure no Overlapping AP's. I have All the apps required for scanning AP's etc and do regular checks and change the channel as and when required.
Sorry for the rants as you tell its getting frustrating for myself trying to game online only to be booted of UK servers for packetloss or high ping.
I know the Wifi on the network is secure as WPS is OFF (Yes there is a security exploit for that hence its off) All WiFi client must also match the Whitelist for MAC Addresses, so i know its not a rouge device zapping the router whilst being outside in a car.
I will keep an eye now of the Stats from Whitebox and what i see in-game and will keep you guys updated.
Re: ADSL 2+ IP Profile Stuck.
14-11-2014 8:12 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: ADSL 2+ IP Profile Stuck.
16-11-2014 5:46 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Yet another bout of packetloss started at 17:30 today ended up getting disconnected from a Teamspeak server where i was chatting to people. The ping rocketed to over 1000ms before i got disconnected so ran my pingpath tests like normal. Here are the results.
Tracing route to easo.ea.com [159.153.234.54]
over a maximum of 30 hops:
0 solidus1983-gmc.hillside.home [192.168.1.105]
1 home.hillisde.hillside.home [192.168.1.254]
2 lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 link-a-central10.pcl-gw01.plus.net [212.159.2.168]
4 xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
5 xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 solidus1983-gmc.hillside.home [192.168.1.105]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% home.hillisde.hillside.home [192.168.1.254]
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% lo0-central10.pcl-ag03.plus.net [195.166.128.184]
0/ 100 = 0% |
3 20ms 0/ 100 = 0% 0/ 100 = 0% link-a-central10.pcl-gw01.plus.net [212.159.2.168]
0/ 100 = 0% |
4 21ms 0/ 100 = 0% 0/ 100 = 0% xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
100/ 100 =100% |
5 --- 100/ 100 =100% 0/ 100 = 0% xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
Trace complete.
Tracing route to lhr08s03-in-f3.1e100.net [173.194.41.131]
over a maximum of 30 hops:
0 solidus1983-gmc.hillside.home [192.168.1.105]
1 home.hillisde.hillside.home [192.168.1.254]
2 lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 link-b-central10.pcl-gw02.plus.net [212.159.2.170]
4 xe-10-2-0.pcl-cr02.plus.net [212.159.0.202]
5 ae1.ptw-cr02.plus.net [195.166.129.2]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 solidus1983-gmc.hillside.home [192.168.1.105]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% home.hillisde.hillside.home [192.168.1.254]
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% lo0-central10.pcl-ag03.plus.net [195.166.128.184]
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% link-b-central10.pcl-gw02.plus.net [212.159.2.170]
0/ 100 = 0% |
4 24ms 0/ 100 = 0% 0/ 100 = 0% xe-10-2-0.pcl-cr02.plus.net [212.159.0.202]
100/ 100 =100% |
5 --- 100/ 100 =100% 0/ 100 = 0% ae1.ptw-cr02.plus.net [195.166.129.2]
Trace complete.
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
0 solidus1983-gmc.hillside.home [192.168.1.105]
1 home.hillisde.hillside.home [192.168.1.254]
2 lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 link-a-central10.pcl-gw01.plus.net [212.159.2.168]
4 xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
5 ae1.ptw-cr01.plus.net [195.166.129.0]
6 te9-4.ptn-gw01.plus.net [195.166.129.33]
7 gi5-1.peh-cr02.plus.net [84.93.232.61]
8 po5.peh-cr01.plus.net [84.93.232.16]
9 vlan2657.peh-elb01.plus.net [84.93.232.44]
10 portal.plus.net [212.159.8.2]
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 solidus1983-gmc.hillside.home [192.168.1.105]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% home.hillisde.hillside.home [192.168.1.254]
0/ 100 = 0% |
2 30ms 0/ 100 = 0% 0/ 100 = 0% lo0-central10.pcl-ag03.plus.net [195.166.128.184]
0/ 100 = 0% |
3 24ms 0/ 100 = 0% 0/ 100 = 0% link-a-central10.pcl-gw01.plus.net [212.159.2.168]
0/ 100 = 0% |
4 25ms 0/ 100 = 0% 0/ 100 = 0% xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
0/ 100 = 0% |
5 29ms 0/ 100 = 0% 0/ 100 = 0% ae1.ptw-cr01.plus.net [195.166.129.0]
0/ 100 = 0% |
6 25ms 0/ 100 = 0% 0/ 100 = 0% te9-4.ptn-gw01.plus.net [195.166.129.33]
0/ 100 = 0% |
7 34ms 0/ 100 = 0% 0/ 100 = 0% gi5-1.peh-cr02.plus.net [84.93.232.61]
0/ 100 = 0% |
8 36ms 0/ 100 = 0% 0/ 100 = 0% po5.peh-cr01.plus.net [84.93.232.16]
0/ 100 = 0% |
9 34ms 0/ 100 = 0% 0/ 100 = 0% vlan2657.peh-elb01.plus.net [84.93.232.44]
0/ 100 = 0% |
10 34ms 0/ 100 = 0% 0/ 100 = 0% portal.plus.net [212.159.8.2]
Trace complete.
Not sure why the last pingpath has different info as the tests are ran one after the other and there hasn't been a disconnect at all either in between these tests.
Edit: Another bout of packetloss
Re: ADSL 2+ IP Profile Stuck.
17-11-2014 6:32 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
0 solidus1983-gmc.hillside.home [192.168.1.105]
1 home.hillisde.hillside.home [192.168.1.254]
2 lo0.11.central11.ptn-bng01.plus.net [195.166.128.229]
3 irb.11.PTW-CR01.plus.net [84.93.249.17]
4 te9-4.ptn-gw01.plus.net [195.166.129.33]
5 gi5-1.peh-cr02.plus.net [84.93.232.61]
6 po5.peh-cr01.plus.net [84.93.232.16]
7 vlan2657.peh-elb01.plus.net [84.93.232.44]
8 portal.plus.net [212.159.8.2]
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 solidus1983-gmc.hillside.home [192.168.1.105]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% home.hillisde.hillside.home [192.168.1.254]
0/ 100 = 0% |
2 24ms 0/ 100 = 0% 0/ 100 = 0% lo0.11.central11.ptn-bng01.plus.net [195.166.128.229]
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% irb.11.PTW-CR01.plus.net [84.93.249.17]
0/ 100 = 0% |
4 26ms 0/ 100 = 0% 0/ 100 = 0% te9-4.ptn-gw01.plus.net [195.166.129.33]
0/ 100 = 0% |
5 33ms 0/ 100 = 0% 0/ 100 = 0% gi5-1.peh-cr02.plus.net [84.93.232.61]
0/ 100 = 0% |
6 34ms 0/ 100 = 0% 0/ 100 = 0% po5.peh-cr01.plus.net [84.93.232.16]
0/ 100 = 0% |
7 32ms 0/ 100 = 0% 0/ 100 = 0% vlan2657.peh-elb01.plus.net [84.93.232.44]
0/ 100 = 0% |
8 31ms 0/ 100 = 0% 0/ 100 = 0% portal.plus.net [212.159.8.2]
Trace complete.
Tracing route to lhr08s03-in-f3.1e100.net [173.194.41.131]
over a maximum of 30 hops:
0 solidus1983-gmc.hillside.home [192.168.1.105]
1 home.hillisde.hillside.home [192.168.1.254]
2 lo0.11.central11.ptn-bng01.plus.net [195.166.128.229]
3 irb.11.PTW-CR02.plus.net [84.93.249.18]
4 * * *
Computing statistics for 75 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 solidus1983-gmc.hillside.home [192.168.1.105]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% home.hillisde.hillside.home [192.168.1.254]
100/ 100 =100% |
2 --- 100/ 100 =100% 0/ 100 = 0% lo0.11.central11.ptn-bng01.plus.net [195.166.128.229]
0/ 100 = 0% |
3 --- 100/ 100 =100% 0/ 100 = 0% irb.11.PTW-CR02.plus.net [84.93.249.18]
Trace complete.
Tracing route to easo.ea.com [159.153.234.54]
over a maximum of 30 hops:
0 solidus1983-gmc.hillside.home [192.168.1.105]
1 home.hillisde.hillside.home [192.168.1.254]
2 lo0.11.central11.ptn-bng01.plus.net [195.166.128.229]
3 irb.11.PTW-CR01.plus.net [84.93.249.17]
4 te-3-4.car5.London1.Level3.net [217.163.45.181]
5 * * *
Computing statistics for 100 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 solidus1983-gmc.hillside.home [192.168.1.105]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% home.hillisde.hillside.home [192.168.1.254]
0/ 100 = 0% |
2 17ms 0/ 100 = 0% 0/ 100 = 0% lo0.11.central11.ptn-bng01.plus.net [195.166.128.229]
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% irb.11.PTW-CR01.plus.net [84.93.249.17]
0/ 100 = 0% |
4 65ms 0/ 100 = 0% 0/ 100 = 0% te-3-4.car5.London1.Level3.net [217.163.45.181]
Trace complete.
Its nearly two days away from being like this for 2 Weeks and still no solution and not even a update from the network team. On the phone now in a Queue waiting to speak to someone for an update very much doubt i will get any further then i am currently getting.
Re: ADSL 2+ IP Profile Stuck.
17-11-2014 6:44 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I'm sad to see that you're still having issues. What's this address you're tracing to? lhr08s03-in-f3.1e100.net
I can see the others and what they are, but this is the one with packet loss on the last step.
Re: ADSL 2+ IP Profile Stuck.
17-11-2014 8:53 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Organization Google
ISP Google
but it still shows packet loss on your network either way.
Also trying to game at this moment and can still see packet loss.
Sorry i lost it with Tech support but as you can tell when packet loss is causing so much problems with online gaming and its nearly two weeks have pasted, Only be told because i responded to the ticket it's been pushed right back to the bottom of the queue, would make anyones blood boil.
Edit: Did wireshark show anything that might help solve this issue.
Re: ADSL 2+ IP Profile Stuck.
19-11-2014 10:03 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
It doesn't look like the wireshark capture showed anything. The ticket is now with our network team though. I'd expect them to be getting back to you pretty quickly, and I can chase for you as well.
Tony
Re: ADSL 2+ IP Profile Stuck.
19-11-2014 10:42 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
So i fired them some pingpaths.
The good news is that the packet loss has now come down to acceptable levels for the time being without changing anything, but i will keep an eye out and see if it flares up. Will keep this thread updated.
Re: ADSL 2+ IP Profile Stuck.
23-11-2014 12:18 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: ADSL 2+ IP Profile Stuck.
24-11-2014 9:58 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I can see one of my colleagues has been looking at your ticket and will pick up your latest comments and respond asap.
Re: ADSL 2+ IP Profile Stuck.
24-11-2014 2:49 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Ran a ping path directly to plus.net and here is the results
Tracing route to portal.plus.net [212.159.8.x]
over a maximum of 30 hops:
0 solidus1983-gmc.hillside.home [192.168.1.x]
1 home.hillisde.hillside.home [192.168.1.x]
2 lo0-central10.ptw-ag04.plus.net [195.166.128.x]
3 link-a-central10.ptw-gw01.plus.net [212.159.2.x]
4 xe-7-2-0.ptw-cr01.plus.net [212.159.0.x]
5 te9-4.ptn-gw01.plus.net [195.166.129.x]
6 gi5-1.peh-cr02.plus.net [84.93.232.x]
7 po5.peh-cr01.plus.net [84.93.232.x]
8 vlan2657.peh-elb01.plus.net [84.93.232.x]
9 portal.plus.net [212.159.8.x]
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 solidus1983-gmc.hillside.home [192.168.1.x]
0/ 100 = 0% |
1 5ms 0/ 100 = 0% 0/ 100 = 0% home.hillisde.hillside.home [192.168.1.x]
0/ 100 = 0% |
2 25ms 6/ 100 = 6% 6/ 100 = 6% lo0-central10.ptw-ag04.plus.net [195.166.128.x]
0/ 100 = 0% |
3 22ms 0/ 100 = 0% 0/ 100 = 0% link-a-central10.ptw-gw01.plus.net [212.159.2.x]
0/ 100 = 0% |
4 28ms 0/ 100 = 0% 0/ 100 = 0% xe-7-2-0.ptw-cr01.plus.net [212.159.0.x]
0/ 100 = 0% |
5 25ms 0/ 100 = 0% 0/ 100 = 0% te9-4.ptn-gw01.plus.net [195.166.129.x]
0/ 100 = 0% |
6 34ms 1/ 100 = 1% 1/ 100 = 1% gi5-1.peh-cr02.plus.net [84.93.232.x]
0/ 100 = 0% |
7 38ms 0/ 100 = 0% 0/ 100 = 0% po5.peh-cr01.plus.net [84.93.232.x]
0/ 100 = 0% |
8 37ms 0/ 100 = 0% 0/ 100 = 0% vlan2657.peh-elb01.plus.net [84.93.232.x]
0/ 100 = 0% |
9 38ms 0/ 100 = 0% 0/ 100 = 0% portal.plus.net [212.159.8.x]
Trace complete.
Also gaming last night was a joke. Other players was complaining about me being invisible to them due to the packet loss. This might get me banned now if this shows on a PBSS. Its nearly 2 days before its 3 weeks with this problem it needs sorting. If its not sorted by end of month i will be calling cancellations and you will be losing a customer, If you think that after that i will be paying a cancellation charge as well, i won't be.
Re: ADSL 2+ IP Profile Stuck.
24-11-2014 3:00 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote This might get me banned now if this shows on a PBSS.
Unless they've changed how PBSS reviews work you shouldn't have anything to worry about. When I used to review these it was only if there was clear evidence of cheating that action was taken, this was usually being able to see through walls, highlighting opponents etc.
Re: ADSL 2+ IP Profile Stuck.
24-11-2014 5:08 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: ADSL 2+ IP Profile Stuck.
24-11-2014 5:12 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
That's my understanding, but just to confirm I'm asking someone else too.
We're just having a look to see if anything else could be causing your issues.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page