Ask
Reply
Solution
11-01-2013 11:17 AM - last edited on 14-07-2014 05:14 PM by Jenny
This light sequence indicates that the Sure Signal isn’t active and has failed to connect with our network.
Troubleshooting steps:
Wait 24 hours.
It can sometimes take up to 24 hours for the Sure Signal to fully register with the server. Before attempting any of the steps below, please wait 24 hours.
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.
Check that your Sure Signal has registered successfully.
Before your Sure Signal can connect to our network, you need to register it with us.
You’ll receive a text or email to let you know when the registration is complete and your Sure Signal won’t work until you’ve received this message.
To check your Sure Signal is registered, login to My Account and click on the 'My Sure Signal' tab. Your Sure Signal details should be listed, along with the status 'Registered'.
If you’ve not yet registered your Sure Signal, you can do this directly from the My Sure Signal page in My Account.
If you’re a Business customer, please register at our Business Sure Signal page.
Check the physical connection between your Sure Signal and the router/modem.
In order to work, the Sure Signal needs to be connected to a spare Ethernet port on your router or modem, or a Hub/Switch that is connected to an internet gateway.
In some cases, it’s possible for an Ethernet cable to be faulty, in which case it may not allow your router and Sure Signal to talk to each other.
To verify that the Ethernet cable works, check the lights at the back of your Sure Signal where the cable is plugged in.
There should be a link light on permanently which indicates that an electrical circuit has been established through the cable.
There should also be a light which flashes whenever data is being passed through the cable. If either the data light or the link light do not come on, this could indicate a problem with the cable itself. Please try a spare cable, or plug the cable into a different port on your router/modem.
Check that you’ve got an active internet connection.
Make sure you can connect to the internet on another device, such as your PC or phone. If you can’t connect, this indicates a problem with your router or your Internet Service Provider (ISP).
We recommend rebooting the router to see if this then allows you to connect to the internet.
Reboot your router/modem.
Check that your Sure Signal has been assigned an internal IP address by your router.
The Sure Signal must be assigned an internal IP address by your router. If your router supports DHCP (Dynamic Host Configuration Protocol), this must be enabled as doing so will enable the router to assign an IP address to your Sure Signal automatically.
For more instructions on how to do this, please check your router manual or contact your ISP or router manufacturer.
If your router or network configuration doesn’t allow DHCP, you’ll need to assign a static IP address to your Sure Signal's MAC Address by using your router's configuration panel. Please contact your ISP or router manufacturer for instructions on how to do this. The MAC address can be found on the sticker at the back of the Sure Signal.
Manually configure your router to allow port-forwarding.
In most cases, routers support a system called Universal Plug-n-Play (UPnP), which sets up port-forwarding for you automatically. If you’ve got a complicated network setup, or a complex router, you may need to enter these settings manually.
Please see the following for a list of IP addresses and port numbers that need to be forwarded to your Sure Signal's internal IP address. For instructions on how to do this, we recommend you contact your ISP or Router Manufacturer, or refer to the default guide for your particular make and model, over at http://portforward.com.
Destination IP Addresses:
Ports and Protocols:
Please note that in the above list of IP addresses, the notation "212.183.131.128/26" means the complete range of IP addresses between 212.183.131.128 and 212.183.131.191.
Your router also needs to assign the Sure Signal with a DNS (Domain Name Server) address via DHCP (Dynamic Host Configuration Protocol).
Check your MTU settings.
Log into your router admin page and find the location of the MTU field. This varies depending on the make and model so you’ll need to look for it.
Change the value of the MTU size to 1500.
Log out of the router, this will usually result in a reboot.
Perform a reset of the Sure Signal:
Post your router/ISP details and Sure Signal serial number.
If you’ve done all of the above, or you’re struggling with configuring your router, please post your router's make and model number below. Please also include your Sure Signal serial number and the name of your ISP.
We find that other users of the same router will usually be able to share tips with you, to get things working.
We’ll also attempt to help with this, but due to the number of different manufacturers and models, it is not always possible. We don’t officially support any form of router configuration, so we’ll always recommend contacting your router manufacturer or ISP for assistance first.
Thanks,
Jenny
26-11-2014 11:19 AM
Am pretty sure it will be the HH3 causing the problems with the box trying to connect.
A few posts up there are a list of inbound ports that if forwarded to the suresignal, sometimes help get the traffic past the blockage.
You could try setting that to see if it helps.
If it's a business hub 3 then i'm not sure if there have been any successful connections.
26-11-2014 11:41 AM
Thank you Grolschuk.
It is a private (home) HH3 rather than a business one.
With reference to Portforward.com, I've just opened up/forwarded the ports 8, 50, 123, 500, 4500, 1723 to the Sure Signal. Reset the SS but same status.
Any other suggestions from Vodafone or other members?
Anthony
26-11-2014 01:06 PM
I know the later versions of the HH also have an option in there called 'Port Clamping' that stops a port from randomly changing numbers, again it may help.
Although not sure if that came in on the v4 or the v3, so take a look around the firewall/vpn settings to see if you can see such a thing.
28-11-2014 12:12 PM
Port Clamping also enabled. Still no progress and same lights are illuminated on the SS.
Is anyone from Vodafone monitoring this page as I have not yet had a response or advice.
I will switch mobile provider on Monday if no solution to this.
Thanks.
01-12-2014 11:59 AM
18-05-2015 06:31 PM
My SureSignal lost its connection with the Vodafone server a around 4 days ago.
It is connected to a BT HomeHub 4 and this combination has been working for ages without the need for any tweaking of the HomeHub settings (apart from a fixed IP address for the SureSignal). My Hub has been using the default upnp setting.
I have tried resetting the HomeHub and SureSignal and waiting for 24 hours, without success.
The SureSignal serial number is 40130423268 and it is showing as active on my Vodafone account.
I have run a traceroute, with the following results:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nnnnnn>TRACERT 212.183.133.177
Tracing route to 212.183.133.177 over a maximum of 30 hops
1 4 ms 4 ms 4 ms BThomehub.home [192.168.1.254]
2 21 ms 20 ms 21 ms 217.32.141.12
3 21 ms 20 ms 21 ms 217.32.140.238
4 25 ms 23 ms 36 ms host109-159-245-18.range109-159.btcentralplus.com [109.159.245.18]
5 24 ms 23 ms 23 ms 31.55.164.71
6 24 ms 23 ms 23 ms 31.55.164.107
7 26 ms 26 ms 27 ms acc1-10GigE-0-2-0-6.bm.21cn-ipp.bt.net [109.159.248.108]
8 38 ms 31 ms 33 ms core2-te0-15-0-15.ilford.ukcore.bt.net [109.159.248.36]
9 34 ms 30 ms 40 ms peer1-xe2-1-0.telehouse.ukcore.bt.net [109.159.254.136]
10 34 ms 29 ms 33 ms lndgw2.arcor-ip.net [195.66.224.124]
11 31 ms 29 ms 29 ms 85.205.0.93
12 * * * Request timed out.
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.
IP address: 31.50.86.119
Ping Test: 29 ms
Speed Test: Download 4.49 Mbps, Upload 0.61 Mbps
Having looked at the Port Forwarding settings, I cannot correlate the recommendations in this topic with the available options on the HomeHub, so I am not inclined to touch this unless someone can give me a step-by-step guide, although I do not see why this should suddently become necessary when it has been working for such a long time with upnp.
Oh, and I have also disabled Smart Setup in the Hub, as suggested in another topic. It has made no difference.
I would really appreciate some help with this.
22-05-2015 01:53 PM
Hi folks
@EdwinK - I'm afraid we're not licenced to give you step by step instructions on how to open the ports for your router.
Your ISP can set them up for you though if you'd rather not portforward.com
Everything else seems fine with your results, but we've been blocked from making contact with your Sure Signal since 16 May.
@JamieEff - It's better to have a fixed IP, as dynamic IP's will be more difficult for the Sure Signal to track. Your ISP can advise you how to do this if you're unsure.
Also, let me know if the upload and download speeds you've posted are the right way round. Typically, your download speed should be faster.
We also advise a minimum of 4.13Mbps for the Sure Signal to work.
Thanks,
Ben
27-05-2015 09:59 AM
Hi Ben
OK, my Broadband speed is back 'up' now - with a download of 6.19 and upload of 0.38
Still no suresignal though
28-05-2015 03:35 PM
Hi @JamieEff
Please ensure your SS is showing as a connected device on your router admin portal.
If this is still giving you issues, please try using the SS on a different Internet connection.
Thanks,
Rodney
19-05-2015 07:55 PM - edited 20-05-2015 06:07 PM
Hi
My SS was working fine. Then on Sunday we needed to move furniture around, unplugged the router and the SS unit and 10 mins later plugged back in and since it hasnt worked...red flashing light and solid centre icon in orange.
I have tried following the instructions on the forum with no joy. I have spoken with someone in Egypt who had as little clue as me and was unable to help with any of the port forwarding.
so am now hoping that someone here will be able to help get md back on track and onine.
details required:
Router: Netgear DGN2200v3
SS serial: 40123307007
ISP: BT
External IP 31.50.130.62 edited as IP changed to 31.50.131.254
Speed test 4.89 Mbs Upload 0.36 Mbs Download
PING 31.50.132.62 (31.50.132.62): 56 data bytes
no need set tos. 0
64 bytes from 31.50.132.62: seq=0 ttl=54 time=57.693 ms
64 bytes from 31.50.132.62: seq=1 ttl=54 time=156.598 ms
64 bytes from 31.50.132.62: seq=2 ttl=54 time=121.763 ms
64 bytes from 31.50.132.62: seq=3 ttl=54 time=62.072 ms
--- 31.50.132.62 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 57.693/99.531/156.598 ms
traceroute:
1
***
2
hos-tr3.juniper2.rz13.hetzner.de
213.239.224.65
0.142 ms
0.206 ms
hos-tr2.juniper1.rz13.hetzner.de
213.239.224.33
17.638 ms
3
core22.hetzner.de
213.239.245.121
0.196 ms
0.989 ms
core21.hetzner.de
213.239.245.81
3.664 ms
4
core11.hetzner.de
213.239.245.221
6.818 ms
core4.hetzner.de
213.239.245.14
8.310 ms
8.367 ms
5
juniper4.rz2.hetzner.de
213.239.203.138
6.278 ms
6.311 ms
3.652 ms
6
et-1-0-0-710.nbg40.core-backbone.com
81.95.15.5
2.860 ms
et-0-3-0-710.fra20.core-backbone.com
80.255.15.121
4.894 ms
et-1-0-0-710.nbg40.core-backbone.com
81.95.15.5
2.860 ms
7
ae2-2075.lon10.core-backbone.com
80.255.14.34
18.940 ms
15.139 ms
16.043 ms
8
***
9
core2-te0-15-0-10.ilford.ukcore.bt.net
109.159.254.216
24.703 ms
10
acc2-10GigE-0-0-1.sf.21cn-ipp.bt.net
109.159.251.178
27.237 ms
28.252 ms
acc2-xe-7-0-0.sf.21cn-ipp.bt.net
109.159.251.38
25.566 ms
11
***
12
***
13
***No reply for 3 hops. Assuming we reached firewall.
Thanks