SureSignal won't work.

[Growltiger]

I had a problem that lasted two years with my Vodafone PAYG account. Here is the link:

http://forum.vodafone.co.uk/t5/Pay-as-you-go-services/Technical-problem-on-my-account-I-am-in-despai...

As part of your attempts to solve that problem, some of my records were cleared by Vodafone. I now discovered that my SureSignal isn't working. On checking the account online, I found I no longer had a SureSignal registered! I registered it again two days ago, and added a second phone, and that all worked as it should in the system.

But it doesn't work, the phones don't see it and only the top light is on. . So I looked at the trobleshooting guide. I have the first model, version 1, the white box with a black base. The symptom is that only the top light is on, and it is continuous.

I then followed the guide. I checked the cable and the lights by the cable. I rebooted the router - a BT Home Hub. I rebooted the SureSignal. I checked the DHCP was working correctly and it is, after the reboot it assigned 192.168.1.64 to its MAC address. I have a superb internet connection, about 10Mb connection speed. It never goes wrong. (Standard BT contract).

The reset procedure described does not work:

Perform a reset of the Sure Signal:

-Hold in the reset button until all lights go solid

-Pull the power lead out with the reset button still pushed in

-Continue to hold down the reset button and reconnect the power lead

-Wait for all lights to come on and then release the reset button

Holding in the reset button even for a long time makes no difference to the lights at all.

Sometimes the box starts flashing different lights, in a sequence like this:

123

2

13

and sometimes other complex sequences including 4.

Then it goes back to just the first light again, steady.

I also double checked the serial number I entered online. It is:

21230680940

It is now nearly two days since I set it up and it still doesn't work, so I have run out of ideas.

Is it possible that it is still associated in your system with my previous registration, on the same account, which you deleted? If so I don't see how it can be made to work without your help.

[Growltiger]

A development! Now the top two lights are on continuously.

[Growltiger]

Then it got more exciting still.

I had the top one solid and the second blinking.

Then I had 1 and 2 solid and 4 blinking.

Now it is back to just the top one solid, back where I started.

Perhaps all this tells you something?

[Growltiger]

I've done more reading.

If I ping 212.183.133.181 it times out.

If I ping 212.183.133.182 it works in just 40ms.

I suspect your server at 212.183.133.181 is not in service?

Maintenance?

[grolschuk]

(having only read the last post in this thread)

No, it is probably set to not reply to ping requests for security reasons

If you tried to ping your home broadband connection public address you would get the same unless you had disabled the security on your network

[Growltiger]

The troubleshooting page recommends using pathping to test the .181 address. So it is reasonable to expect ping to work. And note that ping does work for their .182 address, so they are happy to allow ping.

[grolschuk]

For the pathping it is to see that you are hitting the right destination in the right time, the final hop will be protected, so if you get as far as that all is good on the routing side of things.

Having just read the question, it seems a strange one, if it was working and then stopped with no changes at your end then it may just need VF to resync the registration on their servers, since the second flashing light is it trying to download the config and failing if it does not then light light 4

If any service or routing has changed at home, then double check that IPSEC VPN or Port Clamping has been enabled in the new router if either are an option

[Growltiger]

Nothing whatever changed at home.

Vodafone themselves cleared out my online profile to try to sort out my other problem. I think that completely deleted the SureSignal registration, which I had not touched.

I really don't think there is anything more I can do at my end. It is an ordinary BT Home Hub, I'm sure many users have them. It does not appear necessary to do any special configuration such as port forwarding. It certainly worked perfectly previously, with the same equipment.

I have two possible explanations.

1. My SureSignal profile is now messed up at the Vodafone end. This may be a unique problem due to what they have done to my account. In this case I doubt it will be solved, and I doubt they will replace the box. After the incredible problems I have suffered (see other thread) and their failure to fully solve that problem, I have little confidence.

2. The system is currently not working, so not delivering the profile to the box. In which case it may spring to life.

The only other odd thing is that I can't make the box reset by following their procedure (see my first message).

[Growltiger]

Still not working.

Help from Vodafone please.

[Growltiger]

More info for you.

Speedtest:

Ping 31ms.

Down: 8.74Mb

Up 1.02Mb

External IP: 86.168.42.158

Serial number: 21230680940

Tracert:

C:\WINDOWS\system32>tracert 212.183.133.177

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

  1    74 ms    99 ms    99 ms  BThomehub.home [192.168.1.254]
  2    19 ms    19 ms    20 ms  217.32.147.97
  3    20 ms    19 ms    21 ms  217.32.147.126
  4    24 ms    23 ms    23 ms  212.140.206.82
  5    23 ms    23 ms    23 ms  217.41.169.219
  6    23 ms    23 ms    23 ms  217.41.169.109
  7    23 ms    23 ms    22 ms  acc2-xe-1-2-0.sf.21cn-ipp.bt.net [109.159.251.19
5]
  8    34 ms    31 ms    31 ms  core2-te-0-13-0-13.ealing.ukcore.bt.net [109.159
.251.175]
  9    32 ms    29 ms    32 ms  peer1-xe10-1-0.telehouse.ukcore.bt.net [109.159.
254.110]
 10    36 ms    30 ms    30 ms  lndgw2.arcor-ip.net [195.66.224.124]
 11    34 ms    33 ms    34 ms  85.205.116.6
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
...

Looks to me like your system is not working?