cancel
Showing results for 
Search instead for 
Did you mean: 

My Ping and I

DS
Champion
Posts: 2,187
Thanks: 455
Fixes: 22
Registered: ‎06-01-2017

Re: My Ping and I

Yep, I get you've tried multiple devices and from the router you're (and others for that matter) seeing the issues reported.

Regardless, you still shouldn't be seeing losses like that to the router

(wifi for example may show 1-6ms of latency and ethernet should be 1ms or under, both should not be showing packet loss)

You need to find out why you've got losses from your device to the router. Things like powerline adapters, damaged cables, faulty NIC*, possibly issues within the PC. Hence why I suggested using another device in it's place to see if they too show losses to the router

*NIC - https://en.wikipedia.org/wiki/Network_interface_controller

To see the router software version, simply go here http://192.168.1.254 and scroll to the bottom of that pageWink

IronBelly
Hooked
Posts: 7
Registered: ‎02-04-2019

Re: My Ping and I

@jbligh87 This post probably doesn't help solve your problem, but having looked at your pingplotter results I agree with @DS that you have an internal issue now, which is probably on top of your other problem at the cab which seems to have been resolved. One of either router, NIC, or ethernet cable is causing your issue. You should never see any packet losses to your gateway. Have you tried turning off every wifi and ethernet device and have only a PC plugged in by ethernet and retested? Maybe you have a rogue device on the network somewhere flooding your network with packets.

Plusnet Help Team
Plusnet Help Team
Posts: 6,869
Thanks: 696
Fixes: 261
Registered: ‎01-01-2012

Re: My Ping and I

@jbligh87 The engineers advised that they've done everything they can physically on the line to resolve the issue.

Going forward we need to fix the packet loss on the first hop to the router as it makes everything else after meaningless until it's resolved

If this post resolved your issue please click the 'This fixed my problem' button
 Matthew Wheeler
 Plusnet Help Team
jbligh87
Rising Star
Posts: 166
Thanks: 25
Registered: ‎07-03-2019

Re: My Ping and I

Thanks for everyone's comments here's what I've tried this evening...

 

1-I have tried a different device with a different cable post static IP added and still having same issues on that.

 

2-Currently the version on the router is: Plusnet Hub One | Software version 4.7.5.1.83.8.263 | Last updated 21/03/19 ( I cant see away to update this from the control panel)

 

3-I have tried different power cables and plug sockets (no adapters used)

 

4-I have checked my network adapter's drivers are up to date via control panel, they were(NIC?)

 

5-I have uninstalled any software which "improves internet connection" and retested to get same results.

 

6-I have re-run the test with only one device connected and got the same result.

 

This leads me to think that maybe it is the router? When I tried a different router before it was without the static IP applied and with a friend's old plusnet router (still latest model but he had replaced his). Do we try a new router?

 

**Also, I did find some interesting information on the router's Event Logs(this is just the first page), not that I understand this but there seems to be a lot being blocked:

Time and date Message

 

21:27:38, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [88.221.48.250]:80-​>[212.159.118.76]:50391 on ppp3) 21:27:36, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [213.19.162.80]:443-​>[212.159.118.76]:41728 on ppp3) 21:27:09, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:41440-​>[148.251.77.207]:443 on ppp3) 21:27:04, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [23.198.72.115]:443-​>[212.159.118.76]:39444 on ppp3) 21:26:55, 17 Apr. BLOCKED 4 more packets (because of Packet invalid in connection) 21:26:54, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:48740-​>[157.240.1.23]:443 on ppp3) 21:26:53, 17 Apr. BLOCKED 2 more packets (because of Packet invalid in connection) 21:26:52, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:37750-​>[216.58.208.162]:443 on ppp3) 21:26:50, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:40542-​>[216.58.212.98]:443 on ppp3) 21:26:49, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:48620-​>[35.244.232.184]:443 on ppp3) 21:26:49, 17 Apr. BLOCKED 1 more packets (because of Packet invalid in connection) 21:26:48, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:35276-​>[157.240.1.35]:443 on ppp3) 21:26:47, 17 Apr. BLOCKED 1 more packets (because of Packet invalid in connection) 21:26:46, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:52368-​>[31.13.90.6]:443 on ppp3) 21:26:35, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:55540-​>[212.82.100.146]:443 on ppp3) 21:26:35, 17 Apr. BLOCKED 2 more packets (because of Packet invalid in connection) 21:26:34, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:58012-​>[151.101.17.208]:443 on ppp3) 21:26:27, 17 Apr. BLOCKED 2 more packets (because of Packet invalid in connection) 21:26:26, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:38816-​>[23.212.1.43]:443 on ppp3) 21:26:25, 17 Apr. BLOCKED 2 more packets (because of Packet invalid in connection) 21:26:24, 17 Apr. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [31.13.90.2]:443-​>[212.159.118.76]:58288 on ppp3) 21:26:05, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.67]:39630-​>[157.240.1.18]:443 on ppp3) 21:25:56, 17 Apr. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [157.240.1.52]:443-​>[212.159.118.76]:60692 on ppp3) 21:25:21, 17 Apr. IN: BLOCK [16] Remote administration (TCP [88.36.135.138]:2366-​>[212.159.118.76]:80 on ppp3) 21:24:24, 17 Apr. BLOCKED 2 more packets (because of ICMP replay) 21:24:23, 17 Apr. OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 212.159.118.76-​>84.53.168.7 on ppp3) 21:21:46, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.58.198.234]:443-​>[212.159.118.76]:42306 on ppp3) 21:21:17, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [91.198.174.192]:443-​>[212.159.118.76]:34452 on ppp3) 21:20:26, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.70]:63115-​>[52.211.183.4]:443 on ppp3) 21:20:00, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:37054-​>[35.201.121.164]:443 on ppp3) 21:18:31, 17 Apr. IN: BLOCK [7] ICMP replay (ICMP type 3 code 3 195.166.129.160-​>212.159.118.76 on ppp3) 21:18:00, 17 Apr. OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 212.159.118.76-​>77.234.44.81 on ppp3) 21:17:57, 17 Apr. BLOCKED 2 more packets (because of ICMP replay) 21:17:56, 17 Apr. OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 212.159.118.76-​>77.234.44.81 on ppp3) 21:17:51, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [52.17.43.202]:80-​>[212.159.118.76]:63013 on ppp3) 21:17:36, 17 Apr. (91147.500000) Lease for IP 192.168.1.95 renewed by host DESKTOP-​66JR7K0 (MAC d8:9e:f3:79:7d:15). Lease duration: 1440 min 21:17:36, 17 Apr. (91147.500000) Device connected: Hostname: DESKTOP-​66JR7K0 IP: 192.168.1.95 MAC: d8:9e:f3:79:7d:15 Lease time: 1440 min. Link rate: 1000.0 Mbps 21:17:36, 17 Apr. (91147.420000) Lease requested 21:17:33, 17 Apr. (91144.550000) Wire Lan Port 3 up 21:17:16, 17 Apr. (91127.510000) Device disconnected: Hostname: DESKTOP-​LP1Q2TF IP: 192.168.1.96 MAC: d8:9e:f3:79:81:56 21:17:15, 17 Apr. (91126.550000) Wire Lan Port 2 down 21:17:06, 17 Apr. (91117.550000) Wire Lan Port 2 up 21:17:03, 17 Apr. (91114.550000) Wire Lan Port 2 down 21:16:55, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [23.198.64.54]:443-​>[212.159.118.76]:52723 on ppp3) 21:16:49, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.64]:42494-​>[151.101.61.140]:443 on ppp3) 21:16:49, 17 Apr. BLOCKED 3 more packets (because of Packet invalid in connection) 21:16:48, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.64]:35214-​>[151.101.17.140]:443 on ppp3) 21:16:48, 17 Apr. BLOCKED 3 more packets (because of Packet invalid in connection) 21:16:47, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [151.101.17.140]:443-​>[212.159.118.76]:35215 on ppp3) 21:16:46, 17 Apr. OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 212.159.118.76-​>216.58.204.42 on ppp3) 21:16:44, 17 Apr. BLOCKED 2 more packets (because of ICMP replay) 21:16:43, 17 Apr. OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 212.159.118.76-​>216.58.204.42 on ppp3) 21:16:39, 17 Apr. OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 212.159.118.76-​>77.78.109.83 on ppp3) 21:16:37, 17 Apr. BLOCKED 1 more packets (because of ICMP replay) 21:16:36, 17 Apr. OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 212.159.118.76-​>77.78.109.83 on ppp3) 21:15:04, 17 Apr. BLOCKED 1 more packets (because of ICMP replay) 21:15:04, 17 Apr. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [104.103.158.159]:443-​>[212.159.118.76]:1026 on ppp3) 21:15:03, 17 Apr. OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 212.159.118.76-​>104.20.67.57 on ppp3) 21:14:47, 17 Apr. BLOCKED 6 more packets (because of ICMP replay) 21:14:46, 17 Apr. OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 212.159.118.76-​>74.125.140.157 on ppp3) 21:14:44, 17 Apr. BLOCKED 7 more packets (because of ICMP replay) 21:14:43, 17 Apr. OUT: BLOCK [7] ICMP replay (ICMP type 3 code 1 212.159.118.76-​>74.125.140.157 on ppp3) 21:13:51, 17 Apr. (90922.550000) Wire Lan Port 1 down 21:13:51, 17 Apr. (90922.490000) Device disconnected: Hostname: DESKTOP-​66JR7K0 IP: 192.168.1.95 MAC: d8:9e:f3:79:7d:15 21:13:42, 17 Apr. (90912.900000) Lease for IP 192.168.1.96 renewed by host DESKTOP-​LP1Q2TF (MAC d8:9e:f3:79:81:56). Lease duration: 1440 min 21:13:42, 17 Apr. (90912.900000) Device connected: Hostname: DESKTOP-​LP1Q2TF IP: 192.168.1.96 MAC: d8:9e:f3:79:81:56 Lease time: 1440 min. Link rate: 1000.0 Mbps 21:13:42, 17 Apr. (90912.760000) Lease requested 21:13:39, 17 Apr. (90910.340000) Wire Lan Port 2 up 21:13:36, 17 Apr. (90907.490000) Device disconnected: Hostname: DESKTOP-​LP1Q2TF IP: 192.168.1.96 MAC: d8:9e:f3:79:81:56 21:13:36, 17 Apr. (90907.340000) Wire Lan Port 2 down 21:13:27, 17 Apr. (90898.340000) Wire Lan Port 2 up 21:12:02, 17 Apr. BLOCKED 1 more packets (because of Packet invalid in connection) 21:12:01, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [178.249.97.70]:443-​>[212.159.118.76]:47412 on ppp3) 21:11:44, 17 Apr. BLOCKED 1 more packets (because of Packet invalid in connection) 21:11:43, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [178.249.97.70]:443-​>[212.159.118.76]:47412 on ppp3) 21:11:35, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [88.221.48.250]:80-​>[212.159.118.76]:50159 on ppp3) 21:11:00, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [108.177.15.192]:7275-​>[212.159.118.76]:59934 on ppp3) 21:10:14, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:56502-​>[54.246.173.68]:443 on ppp3) 21:10:12, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:56508-​>[54.246.173.68]:443 on ppp3) 21:09:26, 17 Apr. BLOCKED 1 more packets (because of Packet invalid in connection) 21:09:25, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [88.221.48.243]:80-​>[212.159.118.76]:50131 on ppp3) 21:07:32, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.70]:62894-​>[37.77.187.139]:443 on ppp3) 21:07:14, 17 Apr. (90525.440000) Admin login successful by 192.168.1.95 on HTTP 21:06:09, 17 Apr. (90460.450000) New GUI session from IP 192.168.1.95 21:04:17, 17 Apr. BLOCKED 1 more packets (because of Packet invalid in connection) 21:04:16, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.64]:51520-​>[31.13.90.36]:443 on ppp3) 21:04:16, 17 Apr. BLOCKED 4 more packets (because of Packet invalid in connection) 21:04:15, 17 Apr. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [74.125.140.157]:443-​>[212.159.118.76]:57434 on ppp3) 21:03:30, 17 Apr. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [77.234.42.107]:443-​>[212.159.118.76]:49707 on ppp3) 21:03:13, 17 Apr. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [5.62.40.204]:443-​>[212.159.118.76]:49787 on ppp3) 21:03:10, 17 Apr. IN: BLOCK [16] Remote administration (TCP [192.54.57.24]:59166-​>[212.159.118.76]:8080 on ppp3) 21:02:24, 17 Apr. IN: BLOCK [16] Remote administration (TCP [87.22.66.6]:58930-​>[212.159.118.76]:80 on ppp3) 21:02:06, 17 Apr. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [157.240.1.18]:443-​>[212.159.118.76]:34344 on ppp3) 21:01:31, 17 Apr. BLOCKED 1 more packets (because of Packet invalid in connection) 21:01:30, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.64]:35050-​>[151.101.17.140]:443 on ppp3) 21:01:23, 17 Apr. (90174.670000) Lease for IP 192.168.1.95 renewed by host DESKTOP-​66JR7K0 (MAC d8:9e:f3:79:7d:15). Lease duration: 1440 min 21:01:23, 17 Apr. (90174.670000) Device connected: Hostname: DESKTOP-​66JR7K0 IP: 192.168.1.95 MAC: d8:9e:f3:79:7d:15 Lease time: 1440 min. Link rate: 1000.0 Mbps 21:01:23, 17 Apr. (90174.570000) Lease requested 21:01:23, 17 Apr. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.64]:35032-​>[151.101.17.140]:443 on ppp3) 21:01:23, 17 Apr. BLOCKED 1 more packets (because of Packet invalid in connection)

 

EDIT: completely lost message format when I posted for some reason...

EDIT2: added screenshot so you can see what the logs say in a more readable format...

DS
Champion
Posts: 2,187
Thanks: 455
Fixes: 22
Registered: ‎06-01-2017

Re: My Ping and I

different device ... different cable ... still having same issues on that.

Huh So pingplotter is showing losses to the router?Shocked

What about a 'normal' command prompt (CMD) tracert community.plus.net for example (only need to see hop1)

but I've never seen losses to the router myself going wired to any 3 plusnet hub ones I've ever owned

( guess it could be bufferbloat - http://www.dslreports.com/speedtest )

Software version 4.7.5.1.83.8.263 | Last updated 21/03/19

That is the latest software <insert a deep inhale of breath>

You/we can't update it, but wondering if downgrading it would give the same results - only plusnet can do this, if they agree to it

tried different power cables and plug sockets

How's about a laptop running on battery only? Though I'm not sure mains borne electrickery would do this. I still don't get why other devices are doing the same, unless (doubtful) your antivirus could be fudging the results...?

checked my network adapter's drivers are up to date via control panel

Up to date and working correctly are different things. Though still can't suss out why other devices give the same results. I've gotta be missing something here

uninstalled any software which "improves internet connection" and retested to get same results

That's a new one on me. Software to improve an internet connection.....Huh

re-run the test with only one device connected and got the same result.

I's baffled. If it was the router, most of us would be seeing the same.

This leads me to think that maybe it is the router? When I tried a different router before it was without the static IP applied and with a friend's old plusnet router (still latest model but he had replaced his).

It could be, but again doubtful, then again these are PN routers afterall.

So, your friends router didn't show any loss on your connection?

Do we try a new router?

Unless (IIRC) the 2 you already tried are faulty then I'm not sure if another PNH1 would show different results. On the other hand, a FTTC BT Hub 6 (off ebay, no more than £20 inc p&p) might be an option. But this may not pay off if your friends router also gave losses to the router.

 

88.221.48.250

Someone can verify, but DCH. Hosting provider proxy, from datacenter or CDN (Content Delivery Network).

(If this is within PN's network, then could it be something at their end?)

212.159.<redacted>.<redacted>

I've never had a static IP before, and pretty gobsmacked it's giving out your plusnet username to the world (I have no idea if this is normal or not) "212.159.***.** or ********.plus.com is an IPv4 address owned by PlusNet Technologies Ltd and located in ****"

Don't panic on the last 2 quotes until someone else comments on this. But when I was using my PNH1 running software ending 263 I too saw events like this. I didn't start digging as to why. I, due to the software and my own connection issues, have swapped to my BTH6. I therefore can't cross reference your event log Sad

 

 

DS
Champion
Posts: 2,187
Thanks: 455
Fixes: 22
Registered: ‎06-01-2017

Re: My Ping and I

I struggling with the format, not your fault.

But furthermore some of the IP's are:

https://ipinfo.io/213.19.162.80

https://www.abuseipdb.com/whois/148.251.77.207

https://www.abuseipdb.com/check/157.240.1.23

https://ipinfo.io/216.58.208.162

http://en.utrace.de/whois/91.198.174.192

 

21:13:51, 17 Apr. (90922.550000) Wire Lan Port 1 down

21:13:51, 17 Apr. (90922.490000) Device disconnected: Hostname: DESKTOP-​66JR7K0 IP: 192.168.1.95 MAC: d8:9e:f3:79:7d:15

This device disconnected at 21:13

 

21:13:42, 17 Apr. (90912.900000) Lease for IP 192.168.1.96 renewed by host DESKTOP-​LP1Q2TF (MAC d8:9e:f3:79:81:56). Lease duration: 1440 min

21:13:42, 17 Apr. (90912.900000) Device connected: Hostname: DESKTOP-​LP1Q2TF IP: 192.168.1.96 MAC: d8:9e:f3:79:81:56 Lease time: 1440 min. Link rate: 1000.0 Mbps

21:13:42, 17 Apr. (90912.760000) Lease requested

21:13:39, 17 Apr. (90910.340000) Wire Lan Port 2 up

This device connected on port2, via DHCP, at 1000Mbps, for 24 hours (default 1 day)

 

21:13:36, 17 Apr. (90907.490000) Device disconnected: Hostname: DESKTOP-​LP1Q2TF IP: 192.168.1.96 MAC: d8:9e:f3:79:81:56

21:13:36, 17 Apr. (90907.340000) Wire Lan Port 2 down 21:13:27, 17 Apr. (90898.340000) Wire Lan Port 2 up

This device disconnected at 21:13, a little before the top one.

 

Hope this helps you understand how to read the event log?

(still not sure myself on the formatting on the rest, but blocked means the router firewall block that connection - most, if not all will be normal)

jbligh87
Rising Star
Posts: 166
Thanks: 25
Registered: ‎07-03-2019

Re: My Ping and I

Just ran a trace route to comunity.plus.net as you suggested, with everything connected (as taking things off the network isn't making any difference) and look at the results... hop1 looks healthy, hop 2, not so much.

 

I will run a pingplotter to compare... maybe that software is throwing up a red herring

 

EDIT: added ping plotter's view of events... no idea what to make of it..

jbligh87
Rising Star
Posts: 166
Thanks: 25
Registered: ‎07-03-2019

Re: My Ping and I

Also just read 100% packet loss at router is not an issue in pingplotter, its something to do with how the router priorities return messages. The more I read into this, the more I think it is a red herring and looking at the command prompt trace route, the issues seems to be at hop 2 (which was what was showing as the issue before static IP was applied and where the engineer though the issue was).

Maybe static IP changes how pingplotter reads the trace, again red herring... thoughts?

 

Thanks, Joe

DS
Champion
Posts: 2,187
Thanks: 455
Fixes: 22
Registered: ‎06-01-2017

Re: My Ping and I

Hmm, well to me, the traceroute (tracert) on hop2 shows something isn't right. There isn't a loss but there is a delay. The same goes for hop5, a delay. The latter, according to this points to it being in Sheffield, which again I'd of thought this was within Plusnets network. Hopefully one of staff can clarify

I can't answer why pingplotter is giving those results as I've never used it.

I don't recall your results showing 100% loss to the router, though guess I could have missed it.

 

Getting out of my area of knowledge, but on a static IP the router doesn't always respond to ICMP requests if they are busy. Plusnet have posted that this isn't a problem.

 

Rather than me skimming back through all this, have you changed your DNS settings on the device you normally use?

jbligh87
Rising Star
Posts: 166
Thanks: 25
Registered: ‎07-03-2019

Re: My Ping and I

Hi DS,

No, I haven't changed the DNS settings on the router or my pc.

I agree it, would be good to hear from Plusnet.

Thanks again for advice, Joe
Plusnet Help Team
Plusnet Help Team
Posts: 278
Thanks: 75
Fixes: 14
Registered: ‎25-09-2018

Re: My Ping and I

Hi @jbligh87, Looking at the tracert results you provided and as @MatthewWheeler mentioned, I'd very much be looking at hops 1 to 2 (local network).

 

I would recommend, to rule out a potential LAN issue, disconnect as much as possible from the network. If you have a switch, take it out of the equation. 

 

And with a single device connected try and same traceroute. If that comes back better, then it could be a weak link in the network causing the latency.

It's then a case of process of elimination reintroducing things to see what that weak link is.

 

In regards to hop 5 having high latency, this isn't uncommon. A single high latency hop with low latency around it, is generally just an indication of the router sending to that specific hop on a lower priority.  This is not really an issue and you see the hops after come back to a respectable level.

 

If this post resolved your issue please click the 'This fixed my problem' button
 Matt L
 Plusnet Help Team
DS
Champion
Posts: 2,187
Thanks: 455
Fixes: 22
Registered: ‎06-01-2017

Re: My Ping and I

What he saidWink

And try using the following DNS settings on just that main PC (you can't change it on the router)

google will show you how (but) control panel - network and internet - network and sharing - click ethernet - properties - IPv4 - change from auto DNS to 9.9.9.9 and 8.8.8.8

Then see if anything gets better or worse.

 

As an example, using the auto allocated DNS gives me pretty low latency:

1 <1 ms <1 ms <1 ms bthub [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 9 ms 9 ms 9 ms 136.hiper04.sheff.dial.plus.net.uk [195.166.143.136]
5 9 ms 9 ms 9 ms 195.99.125.134
6 10 ms 9 ms 16 ms 62.172.103.234
7 10 ms 13 ms 9 ms 109.159.253.177
8 * * * Request timed out.
<snipped>
14 * * * Request timed out.
15 14 ms 10 ms 10 ms server-99-84-8-85.lhr62.r.cloudfront.net [99.84.8.85]

 

jbligh87
Rising Star
Posts: 166
Thanks: 25
Registered: ‎07-03-2019

Re: My Ping and I

Hi Folks, 

Ran two trace routes, one to community.plus.net and the other to bbc.co.uk. Both of these were run on the only device one the network. Both of these point outside my internal network being the issue :/

 

See attached 

Thanks, Joe

 

EDIT: added another traceroute with all devices back on network, just for comparison.

Highlighted
jbligh87
Rising Star
Posts: 166
Thanks: 25
Registered: ‎07-03-2019

Re: My Ping and I

Hi DS,

Followed your advice and changed DNS settings and reran the traceroute again. Similar behavior. Attached a screenshot for reference, again hop 2/3 struggling

jbligh87
Rising Star
Posts: 166
Thanks: 25
Registered: ‎07-03-2019

Re: My Ping and I

Do you know if this second 'Npcap Loopback Adapter' is normal? I haven't changed any settings on that. screenshot attached.