User comments on ISPs
  >> Sky Broadband


Register (or login) on our website and you will not see this ad.


  Print Thread
Standard User mbames
(regular) Sun 24-May-15 00:11:02
Print Post

Fibre connected, but nothing workis


[link to this post]
 
A couple of times over the last few days I have noticed that my internet connection drops out. If I log in the SR102 it reports the same WAN IP and connection as being up, but there is no DNS, and I can't ping the default DNS servers, etc.

If I click the disconnect and then connect buttons, connectivity is restored for say 24-32 hours before it might go wonky again.


C:\Users\Matthew>ping 90.207.238.97

Pinging 90.207.238.97 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 90.207.238.97:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


** disconnect & reconnet **

C:\Users\Matthew>ping 90.207.238.97

Pinging 90.207.238.97 with 32 bytes of data:
Reply from 90.207.238.97: bytes=32 time=532ms TTL=126
Reply from 90.207.238.97: bytes=32 time=441ms TTL=126
Reply from 90.207.238.97: bytes=32 time=446ms TTL=126
Reply from 90.207.238.97: bytes=32 time=337ms TTL=126

Ping statistics for 90.207.238.97:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 337ms, Maximum = 532ms, Average = 439ms

Router Statistics
System Up Time: 32:34:04
Port Status TxPkts RxPkts Collision Pkts Tx b/s Rx b/s Up Time
WAN MER 256956 140951 0 10405598 195637 00:05:04
LAN Up 47124167 69512287 0 276742 10157316 32:34:04
WLAN Up 166209 123647 0 402064 17305 32:33:41
Broadband Link Downstream Upstream
Connection Speed 39998 kbps 9995 kbps
Line Attenuation 14.9 dB 0.0 dB
Noise Margin 26.8 dB 6.6 dB

anyone else seeing dodgy behaviour? When I was using my HG612 and Vigor 2820 I never saw these total failures, with both units reporting uptimes of 300+days. To make matters worse, it knocks out my SureSignal box so then I have no Vodafone mobile data (obviously wifi isn't working....)

Matt

Administrator MrSaffron
(staff) Sun 24-May-15 09:09:19
Print Post

Re: Fibre connected, but nothing workis


[re: mbames] [link to this post]
 
Tried using different DNS servers, though the fact an IP will not ping suggests it is not that.

SR102 stable as any router I've ever had here.

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User mbames
(regular) Sun 24-May-15 16:33:24
Print Post

Re: Fibre connected, but nothing workis


[re: MrSaffron] [link to this post]
 
It has just done it again.... noticed the connection was very slow, so I tried a ping.

The ping went back to 12ms for a few pings after I performed the disconnect/reconnect, but then went high again (300+ms).

Guess I am going to have a try their support line. Or I could swap back to using my HG612 and see if that suffers, but then I'm not in a supportable "condition".


C:\Users\matth_000>ping www.bbc.co.uk -t

Pinging www.bbc.net.uk [212.58.244.66] with 32 bytes of data:
Reply from 212.58.244.66: bytes=32 time=2563ms TTL=56
Reply from 212.58.244.66: bytes=32 time=151ms TTL=56
Reply from 212.58.244.66: bytes=32 time=141ms TTL=56
Reply from 212.58.244.66: bytes=32 time=3282ms TTL=56
Reply from 212.58.244.66: bytes=32 time=185ms TTL=56
Reply from 212.58.244.66: bytes=32 time=3779ms TTL=56
Reply from 212.58.244.66: bytes=32 time=111ms TTL=56
Reply from 212.58.244.66: bytes=32 time=51ms TTL=56
Reply from 212.58.244.66: bytes=32 time=2883ms TTL=56
Reply from 212.58.244.66: bytes=32 time=143ms TTL=56
Reply from 212.58.244.66: bytes=32 time=3187ms TTL=56
Reply from 212.58.244.66: bytes=32 time=194ms TTL=56
Reply from 212.58.244.66: bytes=32 time=30ms TTL=56
Reply from 212.58.244.66: bytes=32 time=2256ms TTL=56
Reply from 212.58.244.66: bytes=32 time=1177ms TTL=56
Reply from 212.58.244.66: bytes=32 time=538ms TTL=56
Reply from 212.58.244.66: bytes=32 time=33ms TTL=56
Request timed out.
Request timed out.
Reply from 212.58.244.66: bytes=32 time=3340ms TTL=56
Reply from 212.58.244.66: bytes=32 time=72ms TTL=56
Request timed out.
Reply from 212.58.244.66: bytes=32 time=2121ms TTL=56
Reply from 212.58.244.66: bytes=32 time=1782ms TTL=56
Reply from 212.58.244.66: bytes=32 time=293ms TTL=56
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.
Reply from 94.12.73.214: Destination host unreachable.
Request timed out.
Reply from 94.12.73.214: Destination host unreachable.
*disconnecd*
Request timed out.
Request timed out.
Request timed out.
*reconnected*
Reply from 212.58.244.66: bytes=32 time=12ms TTL=56
Reply from 212.58.244.66: bytes=32 time=11ms TTL=56
Reply from 212.58.244.66: bytes=32 time=12ms TTL=56
Reply from 212.58.244.66: bytes=32 time=11ms TTL=56
Reply from 212.58.244.66: bytes=32 time=12ms TTL=56
Reply from 212.58.244.66: bytes=32 time=11ms TTL=56
Reply from 212.58.244.66: bytes=32 time=12ms TTL=56
Reply from 212.58.244.66: bytes=32 time=11ms TTL=56
Reply from 212.58.244.66: bytes=32 time=11ms TTL=56
Reply from 212.58.244.66: bytes=32 time=13ms TTL=56
Reply from 212.58.244.66: bytes=32 time=23ms TTL=56
Reply from 212.58.244.66: bytes=32 time=14ms TTL=56
Reply from 212.58.244.66: bytes=32 time=80ms TTL=56
Reply from 212.58.244.66: bytes=32 time=68ms TTL=56
Reply from 212.58.244.66: bytes=32 time=185ms TTL=56
Reply from 212.58.244.66: bytes=32 time=263ms TTL=56
Reply from 212.58.244.66: bytes=32 time=144ms TTL=56
Reply from 212.58.244.66: bytes=32 time=409ms TTL=56
Reply from 212.58.244.66: bytes=32 time=117ms TTL=56
Reply from 212.58.244.66: bytes=32 time=405ms TTL=56
Reply from 212.58.244.66: bytes=32 time=300ms TTL=56
Reply from 212.58.244.66: bytes=32 time=316ms TTL=56
Reply from 212.58.244.66: bytes=32 time=347ms TTL=56
Reply from 212.58.244.66: bytes=32 time=366ms TTL=56
Reply from 212.58.244.66: bytes=32 time=352ms TTL=56
Reply from 212.58.244.66: bytes=32 time=277ms TTL=56
Reply from 212.58.244.66: bytes=32 time=294ms TTL=56
Reply from 212.58.244.66: bytes=32 time=308ms TTL=56
Reply from 212.58.244.66: bytes=32 time=312ms TTL=56
Reply from 212.58.244.66: bytes=32 time=310ms TTL=56
Reply from 212.58.244.66: bytes=32 time=314ms TTL=56

Ping statistics for 212.58.244.66:
Packets: Sent = 72, Received = 55, Lost = 17 (23% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 3779ms, Average = 634ms
Control-C
^C
C:\Users\matth_000>

Edited by mbames (Sun 24-May-15 16:57:57)


Register (or login) on our website and you will not see this ad.

Standard User tommy45
(knowledge is power) Sun 24-May-15 19:12:11
Print Post

Re: Fibre connected, but nothing workis


[re: mbames] [link to this post]
 
In reply to a post by mbames:
It has just done it again.... noticed the connection was very slow, so I tried a ping.

The ping went back to 12ms for a few pings after I performed the disconnect/reconnect, but then went high again (300+ms).

Guess I am going to have a try their support line. Or I could swap back to using my HG612 and see if that suffers, but then I'm not in a supportable "condition".


C:\Users\matth_000>ping www.bbc.co.uk -t

Pinging www.bbc.net.uk [212.58.244.66] with 32 bytes of data:
Reply from 212.58.244.66: bytes=32 time=2563ms TTL=56
Reply from 212.58.244.66: bytes=32 time=151ms TTL=56
Reply from 212.58.244.66: bytes=32 time=141ms TTL=56
Reply from 212.58.244.66: bytes=32 time=3282ms TTL=56
Reply from 212.58.244.66: bytes=32 time=185ms TTL=56
Reply from 212.58.244.66: bytes=32 time=3779ms TTL=56
Reply from 212.58.244.66: bytes=32 time=111ms TTL=56
Reply from 212.58.244.66: bytes=32 time=51ms TTL=56
Reply from 212.58.244.66: bytes=32 time=2883ms TTL=56
Reply from 212.58.244.66: bytes=32 time=143ms TTL=56
Reply from 212.58.244.66: bytes=32 time=3187ms TTL=56
Reply from 212.58.244.66: bytes=32 time=194ms TTL=56
Reply from 212.58.244.66: bytes=32 time=30ms TTL=56
Reply from 212.58.244.66: bytes=32 time=2256ms TTL=56
Reply from 212.58.244.66: bytes=32 time=1177ms TTL=56
Reply from 212.58.244.66: bytes=32 time=538ms TTL=56
Reply from 212.58.244.66: bytes=32 time=33ms TTL=56
Request timed out.
Request timed out.
Reply from 212.58.244.66: bytes=32 time=3340ms TTL=56
Reply from 212.58.244.66: bytes=32 time=72ms TTL=56
Request timed out.
Reply from 212.58.244.66: bytes=32 time=2121ms TTL=56
Reply from 212.58.244.66: bytes=32 time=1782ms TTL=56
Reply from 212.58.244.66: bytes=32 time=293ms TTL=56
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.
Reply from 94.12.73.214: Destination host unreachable.
Request timed out.
Reply from 94.12.73.214: Destination host unreachable.
*disconnecd*
Request timed out.
Request timed out.
Request timed out.
*reconnected*
Reply from 212.58.244.66: bytes=32 time=12ms TTL=56
Reply from 212.58.244.66: bytes=32 time=11ms TTL=56
Reply from 212.58.244.66: bytes=32 time=12ms TTL=56
Reply from 212.58.244.66: bytes=32 time=11ms TTL=56
Reply from 212.58.244.66: bytes=32 time=12ms TTL=56
Reply from 212.58.244.66: bytes=32 time=11ms TTL=56
Reply from 212.58.244.66: bytes=32 time=12ms TTL=56
Reply from 212.58.244.66: bytes=32 time=11ms TTL=56
Reply from 212.58.244.66: bytes=32 time=11ms TTL=56
Reply from 212.58.244.66: bytes=32 time=13ms TTL=56
Reply from 212.58.244.66: bytes=32 time=23ms TTL=56
Reply from 212.58.244.66: bytes=32 time=14ms TTL=56
Reply from 212.58.244.66: bytes=32 time=80ms TTL=56
Reply from 212.58.244.66: bytes=32 time=68ms TTL=56
Reply from 212.58.244.66: bytes=32 time=185ms TTL=56
Reply from 212.58.244.66: bytes=32 time=263ms TTL=56
Reply from 212.58.244.66: bytes=32 time=144ms TTL=56
Reply from 212.58.244.66: bytes=32 time=409ms TTL=56
Reply from 212.58.244.66: bytes=32 time=117ms TTL=56
Reply from 212.58.244.66: bytes=32 time=405ms TTL=56
Reply from 212.58.244.66: bytes=32 time=300ms TTL=56
Reply from 212.58.244.66: bytes=32 time=316ms TTL=56
Reply from 212.58.244.66: bytes=32 time=347ms TTL=56
Reply from 212.58.244.66: bytes=32 time=366ms TTL=56
Reply from 212.58.244.66: bytes=32 time=352ms TTL=56
Reply from 212.58.244.66: bytes=32 time=277ms TTL=56
Reply from 212.58.244.66: bytes=32 time=294ms TTL=56
Reply from 212.58.244.66: bytes=32 time=308ms TTL=56
Reply from 212.58.244.66: bytes=32 time=312ms TTL=56
Reply from 212.58.244.66: bytes=32 time=310ms TTL=56
Reply from 212.58.244.66: bytes=32 time=314ms TTL=56

Ping statistics for 212.58.244.66:
Packets: Sent = 72, Received = 55, Lost = 17 (23% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 3779ms, Average = 634ms
Control-C
^C
C:\Users\matth_000>
You could swap back to the BT OR modem and your router if you have the correct sky log in credentials needed, for process of elimination purposes, but don't be rebooting the modem frequently or DLM will clobber the connection

If foolwing the change to the BTOR modem everything works properly, i would leave it like that if you ever get an issue just swap back again before you ring em
Standard User ggremlin
(committed) Sun 24-May-15 19:51:46
Print Post

Re: Fibre connected, but nothing workis


[re: MrSaffron] [link to this post]
 
could this be linked to ???
http://forums.thinkbroadband.com/sky/t/4408243-sky-d...
Administrator MrSaffron
(staff) Sun 24-May-15 21:27:08
Print Post

Re: Fibre connected, but nothing workis


[re: mbames] [link to this post]
 
The fine for a short while after a restart is the sort of thing that suggests something is doing an awful lot across your connection e.g. P2P software

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User mbames
(regular) Thu 28-May-15 18:08:02
Print Post

Re: Fibre connected, but nothing workis


[re: MrSaffron] [link to this post]
 
Transmission was running on rpi, but there were only a few (old) torrents - such as old rpi images, so I doubt it was generating a lot of traffic, but possible.

I have now successfully flashed the latest firmware into my HG612, so I have switched back to that. Haven't seen a similar issue in the last few days, so fingers crossed.

  Print Thread

Jump to