Ask
Reply
Solution
06-10-2010 12:15 PM - last edited on 14-07-2014 03:58 PM by Jenny
We’ve created this thread to help with an issue that some people find during setup.
This issue has the following symptoms:
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 your My Vodafone 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 your My Vodafone Account .
If you’re a Business customer, please register on our business Sure Signal page.
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).
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 (Internet Service Provider).
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
07-10-2014 03:33 PM
Hopefully you find out what is amiss soon.
For your points above
1. No need for a static address it works fine on dhcp issued IPs on the public network, and most of the time on the private side too.
2. No need to change registration details for the duration of the test, that will not stop it connecting, just confuse the emergency services if you need to call 999 while connected to it.
3. Maybe, it depends what router they have, some work out the box, others need 1 setting changing, others need a whole raft of things.
4. Not such a big ask now points 1 and 2 and maybe 3 don't need to be considered.
However as your device did work, and then stopped, if nothing has changed in your network environment, the next stage would be looking at the hardware... Getting the forum guys to do a tracert from their end to your IP isn't going to help, as the chances are they are not in the same location as the suresignal terminating kit, and the fact your trace is getting replies, shows that the route back is going to be ok, otherwise you would not get the reply.
Out of interest, what was the resolution of your tracert not giving any replies at all? as Hop 1 should always be your default gateway, and if that was not replying, that is a local network issue rather than anything external.
07-10-2014 03:55 PM
Thanks for trying to help but I have already performed much analysis of the suresignal box at our end and it is definitely working outbound. I did get a new V3 suresignal to eliminate the suresignal as a possible cause and this V3 box did not work either. I dont actually have anyone else I can use to test at a different location and anyway I think this is totally a red herring.
I need Vodafone to prove to me that a tracert works to my IP because I know that the suresignal box at my end is communicating to the vodafone servers but we get nothing back from them. I have now had the problem since 18th August and I need someone at Vodafone to actually help in troubleshooting the problem from their side.
Surely it is not a lot to ask for a TRACERT which would prove they can connect to my ISP network. Both myself and my ISP have spent many days (probably 8 or so) trying to resolve this. We can see traffic going to vodafone. We can see the packets getting to vodafone but absolutely nothing hits my firewall coming back from Vodafone IPs. I have been trying to get this TRACERT provided for more than a week but get no direct response in terms of running it and providing me with the output. I do not understand why this is so difficult.
My ISP thinks Vodafone may be blocking the IP and a TRACERT is a first step for me. This is soooooooo frustrating.
07-10-2014 05:19 PM
Has anyone resoved this yet?
We have tried 2 V1 suresignals on a BT HH5.
Both give the same symptons. Light 1 steady, light2 flashes.
Have de registered and re registered and left running for over 30hours.
Tracert below;
Please respond.
We live in a dire signal area
Bazza
07-10-2014 05:28 PM
Problems with the traffic getting through the HH5 can sometimes be fixed by enabling the Port Clamping option found in the advanced settings of the router.
If you are happy logging into the HH web interface (password should be on the info sticker), give that a go and then reset the suresignal to see if it helps.
07-10-2014 05:37 PM
Thanks grolschuk.
Willing to try anything.
Will post outcome
Bazza
07-10-2014 07:35 PM
Hi again grolschuk - or anyone else that can help.
It was already clamped.
I forgot we had tried that yesterday after forum hunting.
ISP Provider was Bt
Have attached unit to another line with a different ISP and Asus router.
40meg down, 15 up. Firewall disabled.
Now, first light remains steady, then 2nd flashed until both 1 and 2 are steady, then 4 flashes for a couple of mins without stabilising and lights drop back to 1 solid and the cycle repeats itself after 5 mins or so.
This is the tracert from that.
Bazza
07-10-2014 09:14 PM - edited 08-10-2014 03:06 PM
@Matt_B
SureSignal Serial Number - 21221056076
traceroute to 212.183.133.177 (212.183.133.177), 64 hops max, 52 byte packets
1 vigor.router (192.168.1.254) 0.455 ms 0.214 ms 0.245 ms
2 * * *
3 * * *
4 213.120.158.173 (213.120.158.173) 6.547 ms 6.098 ms 6.048 ms
5 212.140.206.98 (212.140.206.98) 10.945 ms 11.266 ms 10.869 ms
6 217.41.169.229 (217.41.169.229) 9.935 ms 9.911 ms 9.904 ms
7 217.41.169.109 (217.41.169.109) 10.624 ms 10.560 ms 10.221 ms
8 acc2-xe-10-2-0.sf.21cn-ipp.bt.net (109.159.251.197) 9.421 ms
acc2-10gige-10-3-0.sf.21cn-ipp.bt.net (109.159.251.225) 10.367 ms
acc2-xe-0-2-1.sf.21cn-ipp.bt.net (109.159.251.213) 9.274 ms
9 core2-te0-0-0-6.ealing.ukcore.bt.net (109.159.251.159) 22.888 ms
core2-te0-0-0-7.ealing.ukcore.bt.net (109.159.251.35) 21.713 ms
core2-te-0-13-0-10.ealing.ukcore.bt.net (109.159.251.179) 20.899 ms
10 194.72.31.139 (194.72.31.139) 17.981 ms 16.790 ms
peer1-xe3-2-1.telehouse.ukcore.bt.net (109.159.254.209) 17.665 ms
11 lndgw2.arcor-ip.net (195.66.224.124) 19.668 ms 22.163 ms 21.539 ms
12 85.205.0.93 (85.205.0.93) 20.655 ms 18.396 ms 21.331 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
Thanks v much
09-10-2014 03:05 PM
Hi everyone,
solvetech - This isn’t something we can provide.
The next step would be for you to test this on another connection as this would rule out an issue with the Sure Signal.
As grolschuk advised above, you wouldn’t need to register this or set up a static IP address so it shouldn’t take too long.
bazza987 – if you can let us know your Sure Signal serial number, we can look into this further.
jezgardner – Your Sure Signal hasn’t connected to our servers since December 2012.
Please try resetting this as follows:
Thanks,
Jenny
09-10-2014 03:14 PM
@Jenny
It would help me to understand why VF are being unhelpful if you would explain why you cannot provide a TRACERT. After all your customers are ferequently asked by VF to provide them so why can you not provide one?
09-10-2014 03:16 PM
We already know it is not an issue with the SS so it seems very odd to test it at another location. Is there a different reason why you are asking this?