Ask
Reply
Solution
24-07-2015 10:00 AM
Hi, my SS2 has been down for the last couple of weeks having previously worked fine.
The tests (below) seem fine and I've tried resetting it and also restarting the router. I'm on Plusnet FTTC.
Can you advise what to do next?
Test details:
SureSignal id: 40114662550
IPV4 Address is 146.199.157.114
IPV6 Address is ::ffff:92c7:9d72
SPEEDTEST.NET
Ping 13ms
Download 29.81Mbps
Upload 6.45Mbps
PINGTEST.NET
Line Quality A
Ping 13ms
Jitter 3ms
Packet Loss 0%
TRACEROUTE
tracert 212.183.133.177
Tracing route to 212.183.133.177 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 9 ms 8 ms 8 ms lo0.10.Central10.pcl-bng04.plus.net [195.166.130
.177]
3 8 ms 8 ms 8 ms irb.10.PCL-CR02.plus.net [84.93.249.82]
4 9 ms 8 ms 8 ms ae2.pcl-cr01.plus.net [195.166.129.6]
5 9 ms 8 ms 9 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 10 ms 10 ms 11 ms lndgw2.arcor-ip.net [195.66.224.124]
7 10 ms 10 ms 10 ms 85.205.0.86
8 * * * Request timed out.
LAN SETTINGS:
Status: Active
Type: Gaming Console
Connected To: ethport1 (Ethernet)
Physical Address: 0c:4c:39:00:d2:ce
IP Address Assignment: DHCP
IP Address: 192.168.1.5
Always use the same IP address: Yes
DHCP Lease Time: Infinite
PORTFORWARDING:
Protocol Port Range Translate To ... Trigger Protocol Trigger Port
TCP 8 - 8 8 - 8 - -
UDP 8 - 8 8 - 8 - -
TCP 50 - 50 50 - 50 - -
UDP 50 - 50 50 - 50 - -
TCP 123 - 123 123 - 123 - -
UDP 123 - 123 123 - 123 - -
TCP 500 - 500 500 - 500 - -
UDP 500 - 500 500 - 500 - -
TCP 4500 - 4500 4500 - 4500 - -
UDP 4500 - 4500 4500 - 4500 - -
TCP 1723 - 1723 1723 - 1723 - -
UDP 1723 - 1723 1723 - 1723 - -
24-07-2015 10:12 AM
Current Phone >
Samsung Galaxy s²⁴ Ultra 512gb.
24-07-2015 03:12 PM
25-07-2015 05:36 PM
Thanks for having a look, ChazzD.
We've re-registered it (I'm not sure how it came to be de-registered - never mind). Waited 12 hours, tried another reset, but we're still stuck on the flashing red light.
Any idea what next?
27-07-2015 01:56 PM
Please go through the steps to ensure all these ports are forwarded to your Sure Signal's internal IP address.
It's also worth trying a different Ethernet cable to rule this out as a cause for the issues.
If neither of these options resolve the problem, please try connecting your Sure Signal in another location such as a friend of family member's house.
Leave it connected for at least 24 hours. We'll then be able to see if the problem is specific to your location or with the Sure Signal itself.