DELETED_96987

The standard BT one mate, smart hub 1.

I was considering switching to a separate modem and getting a Nighthawk router. Just don’t feel I should have to spend £300+ when I pay for too end fibre :p. However if it cured my problems I’d be willing to do it at this point tbh.
Seems the only thing you haven’t change to test.
Maybe order from Amazon then return if issue isn’t fixed?
 
He mentioned I'm a long way from the cabinet (almost 400m). The cabinet receives 360MB but I get 160MB at best. I'm on one of the all singing all dancing packages. He recommended ringing up BT and getting downgraded to a more suitable one, as I'll still receive the same speeds. He seemed to be alluding to the fact that the cabinet trying to push too much data over too far a distance could be causing issues. I don't see how that's the case but I'm not a BT engineer, so could be wrong.
If that line length is accurate then I'm not surprised G.fast is crapping out as it's hit and miss even at 300m.

You might as well try downgrading to Ultrafast 1 but I'd be a bit surprised if it helps. xDSL negotiates the fastest possible connection and then applies the maximum speed permitted by your ISP. Your gear is going to continue syncing with the cabinet at a speed that is unstable whether on Ultrafast 1 or 2 (although apparently not unstable enough to trigger DLM, which would cap your sync speed).

Reverting to FTTC (the 80Mbps package, which will be closer to 60Mbps at 400m) would probably work but you'd need to decide whether the line stability is worth the loss of speed. This also wouldn't address the separate issue of your PC losing connectivity to the router, which wouldn't be caused by a line fault/instability.

  • Internet was working without issue for 2 years until the date I posted this thread
Did you opt for an upgrade in line speed in recent weeks/months?
 
...
  • Ping tests to 8.8.8.8 and router IP fail simultaneously (usually on all devices, however slightly different results during last test, as mentioned above).
...

This sounds like a local issue if you are losing connection to the router IP. However looking at post 3 you show screenshot of 127.0.0.1 which is a loopback address (local interface on the test machine) not the router IP. The router IP will be the address you access it internally to manage it something like 192.168.0.1 or 192.168.1.1 etc. Check you are pinging the correct router IP.

If you are still seeing the connection drop to the router, then it narrows it down to be either: PC / cabling / router. (or some combination of the 3 if you are really unlucky).

Things to check:

  • Is the PC cable directly plugged into the router, or does it go via a switch / hub / powerline adaptor / patch panel / ethernet coupler / extension / network face plate or socket etc... If possible the cable is connected directly from the PC to the router.
  • Check the cable is plugged in securely (not loose / or clip not broken) into the ethernet port both ends (PC and router). Reseat the cable / wiggle them a bit to make sure it doesn't come out and link light on ethernet port stays lit up.
  • Try a different cable. I think you mentioned you already tried a different cable but is it known to be a good working cable? Some cables from old installs I found can have intermittent faults when you move them slightly because the cabling internally is split / damaged / cause short circuit when moved etc.
  • Try a different LAN port on the router.
  • When the issue happens check the uptime on the router to make sure it wasn't rebooted e.g. maybe local power issue / power adaptor was accidentally knocked / router randomly rebooted etc.
  • If possible check CPU usage on the router when issue occurs in case it's being maxed out.
  • Check download and upload Bandwidth usage at the time of the issue e.g. if the upload bandwidth is being maxed out from backup files uploading to the cloud etc.
  • Test with only one machine connected on the local network to rule out duplicate IP addresses or MAC addresses. Disconnect all WiFi devices etc..
  • Check the ethernet link light is lit up / check the windows logs to see if the network link was disconnected.

It's possible there may be multiple faults here LAN and WAN but i would try to fix the local LAN fault so you can reliably test for WAN issues from a cabled ethernet connection machine. The other option if possible is to test the WAN side directly from router itself if you can SSH onto the router and run ping tests to 8.8.8.8 from the router commandline. If you are also using a separate modem and router then this adds another layer of complexity and testing e.g. swapping out the cable between the modem and router, plugging a test machine directly into the modem, etc.

The issue with the other devices e.g. iPad, could be related to WiFi / Access Point / router / (or Internet connection if you can ping the router but not 8.8.8.8).
 
Last edited:
You shouldn't lose access to the router internal address so there is something not quite right on your local network. Just to confirm you are pinging your router local internal IP not the WAN IP address correct?
 
I've setup a constant ping test and will report back results when it next drops mate (undoubtedly later tonight).




I'm pinging the manufacturers IP which is 192.168.1.1 in the case of the Nighthawk.

I have the router monitoring page open now, so will let you know if network traffic changes when I next have an issue - although surely it will, given my PC loses connection and is sending most of the data on my network...

I'll post up my event logs later whenever it dies.
Still having issues?
 
Back
Top Bottom