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

Ask

2

Reply

3

Solution

Version 3 Sure Signal (Power - flashing, Internet - solid orange, In Service - off, In Use - off)

Retired-Lee
Moderator (Retired)
Moderator (Retired)

This thread's been created to discuss and troubleshoot the version 3 Sure Signal when the light sequence is as follows:

 

  • Power: Flashing
  • Internet: Solid Orange
  • In Service: Off
  • In Use: Off

 

Cause

 

This light sequence indicates the Sure Signal's not active and it has been unable to authenticate on the Vodafone network

 

Troubleshooting

 

Please restart your Sure Signal. If the symptoms continue please add the following details to this thread:

 

  • Your speed test results from here
  • Your ping test results from here
  • Your external IP address from here
  • Your Sure Signal serial number
  • The results of a traceroute

 

Traceroute command:

On a PC:

 

  1. Click on Start and select Run
  2. Type CMD into the Run box and press enter/click ok
  3. A black box will appear
  4. In this box type tracert 212.183.133.177 press Enter
  5. Paste the output of this command into your reply

 

On a Mac:

  1. Open Terminal (Applications, Utilities)
  2. Type 'traceroute 212.183.133.177'
  3. Press Enter

 

This will help us get the quickest possible resolution for you.

Thanks

LeeH

558 REPLIES 558

Dear Andrew.  Great to hear from you.  The information you requested is as follows:-

Serial No:-  40131957462

Speed Test:-  Download  54.04 and Upload 15.86

Ping 33 ms and Jitter 2 ms.  Line Quality B* to a BT Server in Maidenhead 150 miles away.

IP Address 86.156.84.89

 

Last login: Tue Nov 19 18:06:19 on console
derek-maitlands-mac-pro:~ djmaitla$ traceroute 212.183.133.177
traceroute to 212.183.133.177 (212.183.133.177), 64 hops max, 52 byte packets
 1  bthomehub.home (192.168.1.254)  1.240 ms  0.637 ms  0.739 ms
 2  217.32.143.226 (217.32.143.226)  4.735 ms  5.045 ms  4.714 ms
 3  217.32.144.14 (217.32.144.14)  4.985 ms  5.132 ms  4.708 ms
 4  212.140.206.114 (212.140.206.114)  6.482 ms  6.752 ms  6.475 ms
 5  217.41.169.43 (217.41.169.43)  7.981 ms  7.791 ms  7.479 ms
 6  217.41.169.107 (217.41.169.107)  7.483 ms  7.818 ms  7.477 ms
 7  acc1-xe-0-1-3.sf.21cn-ipp.bt.net (109.159.251.83)  26.481 ms
    acc1-xe-0-2-1.sf.21cn-ipp.bt.net (109.159.251.85)  7.406 ms
    acc1-xe-5-2-2.sf.21cn-ipp.bt.net (109.159.251.119)  7.367 ms
 8  core2-te-0-3-0-3.ilford.ukcore.bt.net (109.159.251.45)  17.904 ms
    core1-te-0-4-0-16.ealing.ukcore.bt.net (109.159.251.55)  10.673 ms
    core2-te-0-3-0-3.ilford.ukcore.bt.net (109.159.251.45)  11.904 ms
 9  peer1-xe0-1-0.telehouse.ukcore.bt.net (109.159.254.132)  14.093 ms
    peer1-xe3-2-0.telehouse.ukcore.bt.net (109.159.254.205)  13.902 ms
    peer1-xe0-1-0.telehouse.ukcore.bt.net (109.159.254.132)  13.660 ms
10  lndgw2.arcor-ip.net (195.66.224.124)  11.803 ms  16.175 ms  15.976 ms
11  85.205.116.6 (85.205.116.6)  13.727 ms  13.275 ms  13.223 ms
12  * * *
13  * * *

I hope this helps.

I was unaware of the fact you do not encounter a problem with the BT Homehub 4.  I will chase this up with BT.  IN the meantime I will be interested to learn if anything can be done to improve my connectivity of VSS v3 with Homehub 3.0.

Thank you for your assistance.

Derek

Hi Andrew.  I have looked briefly into the BT HH4 situation.  Apparently there are widespread problems with loss of connectivity to nearly all Apple Products.  I am therefore reluctant to try it.  I note there is now a BT HH5.  Has it been tested with VSS v3.   Derek

adamajis
4: Newbie
You have clearly identified an issue with bt. I have been banging on for 3 months for more information on this. What is the issue ? Also, I am not using a homehub. I use the apple extreme.
How do you know the issue is not with your servers?

Hi adamajis,

 

If it was a general issue with our servers, we’d be seeing a lot more posts from affected customers than we have been.

 

The way to confirm that it is the BT issue that’s the cause of your connection problems will be to try the Sure Signal in a different location with a different ISP.

 

Thanks,

 

Andrew

Andrew,

 

I am not convinced you would be seeing more complaints. It took me some while to find this forum - I am probably not the only one. I bought a SureSignal a couple of weeks ago and have been experiencing exactly this set of lights. I have had to restart the device half a dozen times, and also experience call dropouts.

 

If you do have a known issue with a particular piece of kit (e.g. a BT router or whatever) it would be helpful if you could describe that issue here.

 

Your suggestion that people try their VSS in another place with another ISP is hardly helpful.

couldnt agree more!

 

We still have not been told what the issue is.

 

we still havent been told what you guys are doing to resolve this.

 

Can you tell us what you are doing to resolve this? What have you done so far and what is planned?

Hi guys,

 

jladbury - We have a lot of people posting on the eForum each day to seek help or advice, and our team handles our Twitter and Facebook channels as well. Between them, we get a pretty good guide of what is or isn't working at any time.

 

Most of the cases we see have something specific we can pin down, rather than a broader issue. The suggestion to try a different connection is one which helps us see if the box itself is the problem - if it works there, then it's not broken.

 

We'll be happy to look into your issues. Post us some details and we'll take a look:


 - Your speed test results from here.
 - Your ping test results from here.
 - Your external IP address from here.

 - Your Sure Signal serial number.

We'd also need the results of a traceroute:

On a PC

 - Click on Start and select Run
 - Type CMD into the Run box and press enter/click ok
 - A black box will appear.
 - In this box type tracert 212.183.133.177 press Enter
 - Paste the output of this command into your reply.

On a Mac

 

 - Open Terminal (Applications, Utilities)

 - Type traceroute 212.183.133.177 and press Enter

 - Paste the output of this command into your reply.

 

---------------------------------------------

 

Toon_Hak We have seen a variation on the reset procedure help in some cases. Can you try it again but this time unplug the Ethernet cable before you press the button and plug it back in at the end of the process?

 

If that doesn't help, can you check that you have the following ports open for forwarding on the router for me?

 

 - 8

 - 50

 - 123

 - 500

 - 1723

 - 4500

 

Also, you need to make sure the following IP ranges are allowed on the router and firewall:

 

212.183.133.177-179

212.183.133.181-182

212.183.131.128-191

88.82.13.177-179

88.82.13.169-171

88.82.13.183

 

These should be picked up automatically, but it's best to check.

 

---------------------------------------------

 

Kevf123 - I've given the box a resync, so give it a reset for me.

 

The Sure Signal needs times of no more than 200ms for each step in the connection or it times out. Looking at the traceroute, there's some fluctuation in the times you're getting. Step 2 gets pretty close to that maximum, whilst step 3 goes over. 

 

This wild swing would fit with the on/off nature of your connection - it works fine until something slows the connection, then times out and has to retry. If the resync doesn't help, I'd check with your Internet Service Provider to see if they can pin down what's causing these delays.

 

Dave

I tried the reset after the resync but no joy, it lost connection again.

 

I decided to use my wired system instead of my wireless one to do the traceroute and the high latency hops disappear, so I doubt if the Sure Signal is experiencing the issue either as it is wired. I used a couple of flags to prevent DNS lookups and limit the number of hops so I could run repeated tests, they're all very similar to the below. There's nothing here I can take to my ISP.

 

traceroute to 212.183.133.177 (212.183.133.177), 11 hops max, 38 byte packets
1 192.168.1.254 0.357 ms 0.251 ms 0.245 ms
2 217.32.143.225 4.657 ms 4.476 ms 4.450 ms
3 217.32.143.254 4.760 ms 4.438 ms 4.704 ms
4 212.140.235.226 6.247 ms 5.999 ms 6.450 ms
5 217.41.169.13 6.269 ms 6.459 ms 6.448 ms
6 217.41.169.107 6.232 ms 6.464 ms 6.217 ms
7 109.159.251.83 7.027 ms 109.159.251.117 6.537 ms 109.159.251.115 6.095 ms
8 109.159.251.29 12.981 ms 109.159.251.43 16.961 ms 109.159.251.7 14.588 ms
9 213.121.193.144 14.068 ms 109.159.254.134 12.472 ms 12.240 ms
10 195.66.224.124 12.969 ms 14.160 ms 12.232 ms
11 85.205.116.10 12.965 ms 12.194 ms 13.497 ms

Hi Guys,

 

Thanks for your posts.

 

@ danielanthony – Everything looks fine with the registration as it updated yesterday.

 

Looking at the traceroute, you do have one ping on hope 8 which is a little high, can you run the traceroute again to see if this is still the case?

 

The Sure Signal needs hops to be under 200ms.

 

@ kevf123 – Everything looks fine with the traceroute and it is hitting our server with all pings under 200ms.

 

I know were currently investigating an issue with BT around fragmented packets as we transmit packets at an MTU of 1500 but then only accept up to 1492 which has seen to cause a few problems.

 

To rule this out, are you able to test this on another internet connection to see if you get the same issue?

 

James

Here is another tracert:

 

Tracing route to cluster4.vap.vodafone.co.uk [212.183.133.177]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 26 ms 24 ms 25 ms esr15.kingston5.broadband.bt.net [217.47.66.146]

3 25 ms 24 ms 24 ms 217.47.66.13
4 29 ms 26 ms 26 ms 213.1.69.130
5 38 ms 27 ms 27 ms 217.41.168.191
6 27 ms 31 ms 26 ms 217.41.168.109
7 28 ms 27 ms 26 ms acc2-10GigE-0-1-0-6.l-far.21cn-ipp.bt.net [109.159.249.222]
8 30 ms 30 ms 30 ms core2-te0-0-0-17.faraday.ukcore.bt.net [109.159.249.135]
9 28 ms 28 ms 27 ms peer1-xe-8-2-1.telehouse.ukcore.bt.net [213.121.193.137]
10 32 ms 30 ms 31 ms lndgw2.arcor-ip.net [195.66.224.124]
11 31 ms 29 ms 28 ms 85.205.116.2
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.