cancel
Showing results for 
Search instead for 
Did you mean: 
1

Ask

2

Reply

3

Solution

Sure Signal not transmitting a 3G signal

Retired-George
Moderator (Retired)
Moderator (Retired)

This issue presents the following symptoms:

 

For version 1 Sure Signal (the one with four lights on the front):

  • Lights one and two are solid which indicates the Sure Signal is connected, but isn't giving a 3G signal.
  • Light four doesn’t light up or lights occasionally and then goes out at certain times of day.

 

For version 2 Sure Signal (the one with 3 lights on the front): 

  • The power and system lights are both solid, indicating that the Sure Signal is giving a 3G signal.
  • Your registered phones don’t pick up a 3G signal.

 

For version 3 Sure Signal (the plug in version):

  • Power, internet and service lights are solid and the ‘in use’ light is either solid or flashing
  • Your registered phones don’t pick up a 3G signal

 

Troubleshooting steps:

Check that your broadband connection meets our minimum requirements.
Please run the broadband speed checker.


If your connection fails any part of the test, this indicates an issue with your Internet Service Provider (ISP) and you’ll need to contact them to discuss this.

 

Your connection speed will vary throughout the day, so we recommend running it at various times to get an accurate reading.

 

To ensure the Sure Signal broadcasts at the correct frequency, it sends and receives small amounts of data to a Network Time Protocol Server hosted by ourselves. If these packets of data take longer than 240ms to make a round-trip, the accuracy can no longer be ensured and so the Sure Signal will automatically stop broadcasting and light four will go out.

 

Check for planned maintenance.

Planned maintenance can cause periods of downtime, so check the forum for any planned maintenance. If there is, this will be announced at the top of the Sure Signal forum.

 

Reset your Sure Signal:

 

  1. Hold in the reset button until all lights go solid
  2. Pull the power lead out with the reset button still pushed in
  3. Continue to hold down the reset button and reconnect the power lead
  4. Wait for all lights to come on and then release the reset button

 

The Sure Signal will be back online in around 1 hour.

 

Configure your Router Firewall.
The IP address and ports used for NTP (Network Time Protocol) synchronisation are listed below. You may need these to configure the correct firewall settings on your router.

 

This step isn’t usually necessary, but it may help if you’re using a complex network (such as a corporate or office LAN), or a complex router.

 

We recommend contacting your ISP or router manufacturer directly for detailed instructions on exactly how to change your router settings. Alternatively, select your router make and model over at http://portforward.com and follow the default guide there.

Destination IP addresses:

  • 212.183.133.181
  • 212.183.133.182
  • 212.183.131.128/26

 

  • Protocol = UDP
  • Port = 123


Please note that in the list of IP addresses above, the notation "212.183.131.128/26"means the entire range of IP addresses between 212.183.131.128 and 212.183.131.191

 

Perform a PathPing to our server.

In order to check if the Sure Signal's able to communicate with our NTP server, a PathPing can be performed as a test. In order to do this, you'll need to open the command prompt in Windows as follows:

  • For XP just click Start > Run and type cmd then hit enter
  • For Vista/Windows 7, press Start and type 'cmd' into the search bar
  • Right click the result and click ‘Run As Administrator’


Once you're in the command prompt, type in PathPing 212.183.133.181. This will perform a trace route to the NTP server and will show you the route it took to get there. One of the columns will display packet loss, if this occurs before hitting our server, you'll need to contact your ISP for further assistance.

 

If you've completed all the troubleshooting steps above and not identified the cause of the issue, your Sure Signal may be faulty. Please post in this thread and we can look into it further.

 

Thanks,

 

Jenny

1 ACCEPTED SOLUTION

Hello

 

serial number 21224717989 version 1

 

the sure signal stopped working a few days ago after a lont internet outage (2 hours), presented with only light 1 flashing.

 

I have done a little troubleshooting and have now manged to get to light 1 and 2 solid.

 

how is it looking from your end?

 

 

Internet speed >5 Mbps ping normally <55ms.

 

pathping 

C:\WINDOWS\system32>pathping 212.183.133.181

Tracing route to 212.183.133.181 over a maximum of 30 hops

0 XPS-M133064BIT.int.hillblock.com [192.168.1.104]
1 WRT54GL [192.168.1.251]
2 192.168.1.250
3 losubs.subs.dsl5.wh-man.zen.net.uk [62.3.83.10]
4 no-dns-yet-62-3-86-29.zen.co.uk [62.3.86.29]
5 ge-2-0-0-0.cr1.wh-man.zen.net.uk [62.3.80.49]
6 ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]
7 ldngw1.arcor-ip.net [195.66.224.209]
8 85.205.116.14
9 * * *
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 XPS-M133064BIT.int.hillblock.com [192.168.1.104]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% WRT54GL [192.168.1.251]
0/ 100 = 0% |
2 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.250
1/ 100 = 1% |
3 44ms 2/ 100 = 2% 1/ 100 = 1% losubs.subs.dsl5.wh-man.zen.net.uk [62.3.83.10]
0/ 100 = 0% |
4 45ms 1/ 100 = 1% 0/ 100 = 0% no-dns-yet-62-3-86-29.zen.co.uk [62.3.86.29]
0/ 100 = 0% |
5 46ms 1/ 100 = 1% 0/ 100 = 0% ge-2-0-0-0.cr1.wh-man.zen.net.uk [62.3.80.49]
1/ 100 = 1% |
6 54ms 2/ 100 = 2% 0/ 100 = 0% ge-3-0-0-0.cr2.th-lon.zen.net.uk [62.3.80.45]
0/ 100 = 0% |
7 54ms 2/ 100 = 2% 0/ 100 = 0% ldngw1.arcor-ip.net [195.66.224.209]
98/ 100 = 98% |
8 --- 100/ 100 =100% 0/ 100 = 0% 85.205.116.14

Trace complete.

 

Can you see the sure signal from your end?

 

Thanks in advance

IAn

 

 

FIXED

 

Came back about an hour later and it is working OK

 

Don't you just hate it when that happens

 

Ian

View solution in original position

501 REPLIES 501

Hello, 

 

At the moment it has the red power line on solidly, the System light on solidly but the phone indicator is off. If i reset the box the phone indicators flashes for a long time then eventually goes off. 

 

thanks

 

rog

Ben_H
Moderator (Retired)
Moderator (Retired)

Hi Rog,

 

Thanks for confirming. 

 

This sequence tells me the Sure Signal is struggling to setup fully.

 

Would there be anything on the powerline adapters you mentioned that could be restricting or blocking access? Could I also ask what model or make of powerline adapters you're using to the workshop? 

Many thanks, Ben

Hello,

 

The powerline adaptors are Simpler Networks HP200PT64 adaptors, as supplied by BT for use with their home hub. There is also a wireless access point that is fed from that adaptor in the workshop and the VSS2 takes its network connection directly from that wireless access point (as i believe it is a straight passthrough of the network connection rather than reallocated IP addresses as it would for a wifi connection).  What i could try is plugging the VSS2 directly into the powerline adaptor to see if that helps. Would need to reset it for that to take effect ? 

 

thanks

 

rog

Hi MrBadger,

 

That's a good thing to check. I'd also try connecting it directly to the Home Hub. If it starts working, leave it overnight to check it holds the connection.

 

If neither of these work, try it with the Ethernet cable used on the working Sure Signal.

 

Also, try swapping the Sure Signals. If the v3 Sure Signal works where the v2 doesn't, that points to a fault with the Sure Signal itself.

 

It would be best to reset with each test. Follow these steps:

 

  • Unplug the ethernet cable from the Sure Signal
  • Hold down the reset button until all the lights show (about 30 seconds)
  • Keeping the reset button held down, remove then re-insert the power lead.
  • Once all lights display release the reset button.
  • Plug the cable back in
  • Allow around one hour for the Sure Signal to come back online.

 

Dave

just a quick update. The VSS3 works when plugged into the wireless access point in the workshop. so that proves the power line adaptors and wireless access point are not interfering with the signal. The VSS2 which i was trying to install in the workshop does not work when plugged in to the main BT router back in the house. so I think i have to conclude that while the VSS2 did work a few months ago, the brief period of inactivity for a few months while i put the VSS3 in has caused something in it to stop working. 

 

Next step is to get a new VSS2 or VSS3 and try again. Do you know whether these boxes can be repaired ?

thanks for your help.

 

rog

 

Hi JohnPead,

 

I’ve made a not of your serial number because I want to get one of my colleagues to take a closer look at this for you.

 

When I have done this I will pop back with another post.

 

@ MrBadger – If a Sure Signal is faulty, it can be repaired within the warranty period which lasts for two years.

 

 James

[URL=http://www.speedtest.net/my-result/3409015498][IMG]http://www.speedtest.net/result/3409015498.png[/I...

 

MY IP 86.144.99.197


My SureSignal Version1 serial number 21197096536

 

I have been struggling to get this to work for some time. 

I can get as far as the first two lights on solid and the fourth flashing then it does goes to power on light.

 

The pathping test only gets about three steps before giving up , but other machines on this network use ntp without any issues. I have the recomended port set open includeing udp 123 to the VSS

 

My ISP is BT infinity and the standard ping -f -l 1472 www.dslreports.com   works fine

 

Can you check that I am whitelisted 

 

Thanks

 

Andy

 

Sorry my speedtest URL got garbled it is

 

http://www.speedtest.net/my-result/3409015498

 

Thanks

The pathping result

 

C:\Windows\system32>PathPing 212.183.133.181

Tracing route to 212.183.133.181 over a maximum of 30 hops

  0  Monsta-PC [192.168.10.2]
  1  RT-N66U [192.168.10.1]
  2  172.16.15.140
  3     *        *        *
Computing statistics for 50 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Monsta-PC [192.168.10.2]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  RT-N66U [192.168.10.1]
                              100/ 100 =100%   |
  2  ---     100/ 100 =100%     0/ 100 =  0%  172.16.15.140

Trace complete.

 

C:\Windows\system32>pathping www.dslreports.com

Tracing route to www.dslreports.com [64.91.255.98]
over a maximum of 30 hops:
  0  Monsta-PC [192.168.10.2]
  1  RT-N66U [192.168.10.1]
  2  172.16.15.140
  3     *        *        *
Computing statistics for 50 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Monsta-PC [192.168.10.2]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  RT-N66U [192.168.10.1]
                              100/ 100 =100%   |
  2  ---     100/ 100 =100%     0/ 100 =  0%  172.16.15.140

Trace complete.

C:\Windows\system32>ping www.dslreports.com

Pinging www.dslreports.com [64.91.255.98] with 32 bytes of data&colon;
Reply from 64.91.255.98: bytes=32 time=131ms TTL=42
Reply from 64.91.255.98: bytes=32 time=132ms TTL=42

Ping statistics for 64.91.255.98:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 131ms, Maximum = 132ms, Average = 131ms
Control-C
^C
C:\Windows\system32>ping 212.183.133.181

Pinging 212.183.133.181 with 32 bytes of data&colon;
Request timed out.
Request timed out.

Ping statistics for 212.183.133.181:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C

 

 

C:\Windows\system32>ping -f -l 1472 www.dslreports.com

Pinging www.dslreports.com [64.91.255.98] with 1472 bytes of data&colon;
Reply from 64.91.255.98: bytes=1472 time=134ms TTL=42
Reply from 64.91.255.98: bytes=1472 time=134ms TTL=42
Reply from 64.91.255.98: bytes=1472 time=135ms TTL=42
Reply from 64.91.255.98: bytes=1472 time=134ms TTL=42

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

 

Apparently pathping cannot get data if any single hop blocks icmp , but traert not a lot more convincing

 

C:\Windows\system32>tracert 212.183.133.181

Tracing route to 212.183.133.181 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  RT-N66U [192.168.10.1]
  2    21 ms    20 ms    20 ms  172.16.15.140
  3     *        *        *     Request timed out.
  4    21 ms    20 ms    20 ms  217.41.217.13
  5    23 ms    23 ms    23 ms  host109-159-245-18.range109-159.btcentralplus.co
m [109.159.245.18]
  6    23 ms    23 ms    23 ms  213.120.182.65
  7    23 ms    23 ms    24 ms  31.55.164.107
  8    24 ms    23 ms    23 ms  109.159.248.121
  9    30 ms    27 ms    27 ms  core1-te0-3-0-14.ealing.ukcore.bt.net [109.159.2
48.24]
 10    28 ms    29 ms    27 ms  peer2-xe0-0-0.telehouse.ukcore.bt.net [109.159.2
54.102]
 11    28 ms    28 ms    28 ms  t2c3-xe-1-1-3-0.uk-lon1.eu.bt.net [166.49.211.18
2]
 12    28 ms    28 ms    28 ms  166-49-211-254.eu.bt.net [166.49.211.254]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Windows\system32>