Vodafone Servers Unreachable

[7ony]

Our two VSS 1 boxes have been down all week, presuming there was a DSL issue, but today I run some checks and the issue points to Vodafone.

We did a 'Tracert' to address 212.183.133.181 and the packets don't reach the destination (request timed out). So we did just a ping to the same address. No reply (100% packet loss). We did the same thing with the address 212.183.133.182 and this was OK. Pinging it was OK as well. Then we tried destinations between 212.183.131.128 and 212.183.131.191. Tracert timed out and we got 100% packet loss on pinging.

As so many people are having problems with BT (as we are with them) we tried the same procedure with an external website based in the UK. Same results.

Anyone else came the same conclusion as me?

Please investigate.

[7ony]

The other Sure Signal box starts working on the same connection.

I have replaced the cable and used a different socket. Still the same.

Could it be the power supply? I will try changing them over and see what happens.

[7ony]

That was it! It was the power supply.

Although the light where flashing as it seems to start working, when I swap the power supplies over, the other one stops working.

Any idea where I can get a new one?

[7ony · Accepted solution]

After doing a bit of research on this, apparently the 12v 1.5amp power supply provided does not "Cut the Mustard" for these units. When it's a few years old, the power it supplies drops too low. So the light make it look like it's working, but when the unit turns the cell active to connect to the phone, this is when it needs the most power but doesn't get it. So it resets.

Just purchased 2 x 2amp chargers and will report back how I get on.

[7ony]

Just to let you all know that updating the power supply to the new 2 amp version has now got it up and running.

[coremax]

I'm hoping you'd be able to help me find a solution to the same problem I've been having with my Sure Signal 3 for the last few months, here's the information requested earlier by James:

Internet Speed: 63.44Mbps Download, 2.90Mbps Upload

Ping: 59ms

My IP address: 77.100.12.16

Serial Number: 40131136851

Traceroute to 212.183.133.177:

~ $ traceroute 212.183.133.177

traceroute to 212.183.133.177 (212.183.133.177), 64 hops max, 52 byte packets

 1  routerlogin.net (192.168.0.1)  3.074 ms  0.964 ms  0.974 ms

 2  10.95.116.1 (10.95.116.1)  9.523 ms  10.101 ms  8.920 ms

 3  haye-core-2b-ae6-746.network.virginmedia.net (80.3.177.129)  10.795 ms  13.312 ms  9.144 ms

 4  brhm-bb-1c-ae11-0.network.virginmedia.net (62.253.174.185)  13.990 ms  14.892 ms  14.666 ms

 5  brnt-bb-2a-et-001-0.network.virginmedia.net (62.253.175.205)  15.763 ms

    brnt-bb-2a-et-101-0.network.virginmedia.net (62.253.175.209)  15.675 ms

    brnt-bb-2a-et-001-0.network.virginmedia.net (62.253.175.205)  19.107 ms

 6  brnt-bb-1c-ae1-0.network.virginmedia.net (62.254.42.102)  15.918 ms  15.078 ms  16.177 ms

 7  195.2.9.149 (195.2.9.149)  22.176 ms  22.125 ms  24.410 ms

 8  ae6-xcr1.bkl.cw.net (195.2.10.242)  68.073 ms  36.573 ms  25.932 ms

 9  * * *

10  * * *

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

Many thanks for looking into this, much appreciated as I can't use the sure signal for months now.

[Retired-James]

Hi coremax,

Everything looks fine with the tests that you’ve done, but the Sure Signal hasn’t connected to our server for quite a while.

What light sequence are you currently seeing?

As a Virgin Media customer, you may have been affected by the updates a couple of months ago that meant all of the settings were wiped.

When you first set up the Sure Signal, did you just plug it in and it worked first time?

If yes, I’d deregister and register this again after an hour to start the setup process through your router again.

If no, you’d also need to set all of the ports up again as mentioned here.

James

[coremax]

Hi James,

I've done a packet capture between VSS3 and your servers. By the looks of it 212.183.133.182 is your NTP server, which keeps on trying to sync the clock on the VSS3, but VSS3 is having difficulties with accepting this guidance.

1) VSS3 contacts Vodafone NTP, asking for the time, with default value 2036/02/07 06:28:18

21:28:45.916215 IP (tos 0xb8, ttl 64, id 46835, offset 0, flags [none], proto UDP (17), length 76)

    192.168.2.2.50124 > 212.183.133.182.ntp: [udp sum ok] NTPv4, length 48

        Client, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 16s, precision 0

        Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: (unspec)

          Reference Timestamp:  0.000000000

          Originator Timestamp: 0.000000000

          Receive Timestamp:    0.000000000

          Transmit Timestamp:   2.228306278 (2036/02/07 06:28:18)

            Originator - Receive Timestamp:  0.000000000

            Originator - Transmit Timestamp: 2.228306278 (2036/02/07 06:28:18)

2) Vodafone NTP provides the correct time as 2014/04/08 21:28:44

21:28:46.039108 IP (tos 0x0, ttl 49, id 46835, offset 0, flags [none], proto UDP (17), length 76)

    212.183.133.182.ntp > 192.168.2.2.50124: [udp sum ok] NTPv4, length 48

        Server, Leap indicator:  (0), Stratum 1 (primary reference), poll 16s, precision -22

        Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: GPS^@

          Reference Timestamp:  3605977724.000000000 (2014/04/08 21:28:44)

          Originator Timestamp: 2.228306278 (2036/02/07 06:28:18)

          Receive Timestamp:    3605977726.305049091 (2014/04/08 21:28:46)

          Transmit Timestamp:   3605977726.305060118 (2014/04/08 21:28:46)

            Originator - Receive Timestamp:  -688989571.923257172

            Originator - Transmit Timestamp: -688989571.923246145

3) VSS3 insists that it's calling from 2036, specifically 2036/02/07 06:28:18

21:28:46.916319 IP (tos 0xb8, ttl 64, id 46836, offset 0, flags [none], proto UDP (17), length 76)

    192.168.2.2.50124 > 212.183.133.182.ntp: [udp sum ok] NTPv4, length 48

        Client, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 16s, precision 0

        Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: (unspec)

          Reference Timestamp:  0.000000000

          Originator Timestamp: 0.000000000

          Receive Timestamp:    0.000000000

          Transmit Timestamp:   2.232776597 (2036/02/07 06:28:18)

            Originator - Receive Timestamp:  0.000000000

            Originator - Transmit Timestamp: 2.232776597 (2036/02/07 06:28:18)

And this goes on and on and on...

I've checked a few posts which referenced an NTP issue in cases of latency over 240ms, which is not the case with my connection.

                                                                                                                                    Packets               Pings

 Host                                                                                                                             Loss%   Snt   Last   Avg  Best  Wrst StDev

 1. routerlogin.net                                                                                                                0.0%     3   92.1  70.9   1.2 119.4  61.9

 2. 10.95.116.1                                                                                                                    0.0%     3   31.2  48.6  31.2  66.7  17.7

 3. haye-core-2b-ae6-747.network.virginmedia.net                                                                                   0.0%     3  105.2  77.0  10.5 115.4  57.9

 4. haye-core-2a-ae1-0.network.virginmedia.net                                                                                     0.0%     3   50.1  49.9  19.9  79.7  29.9

 5. brnt-bb-1c-ae9-0.network.virginmedia.net                                                                                       0.0%     3  130.8  74.7  11.9 130.8  59.7

 6. 195.2.9.149                                                                                                                    0.0%     3   65.5  65.0  19.4 110.0  45.3

 7. ae6-xcr1.bkl.cw.net                                                                                                            0.0%     3   55.2  69.7  55.2  84.2  20.5

 8. ???

 9. ???

10. ???

11. ???

12. ???

13. ???

14. 212.183.133.182                                                                                                                0.0%     2   23.3  33.7  23.3  44.1  14.7

This suggests 33.7ms of an average and 44.1ms worst case roundtrip.

Any suggestions?

Many thanks for your help.

[coremax]

Hi James,

some additional information, I have tried with multiple ISPs in addition to Virgin Media, and the NTP sync failure is still the case when connected to the internet with Vodafone 3G USB and with BT, separately.

Should I consider replacing the VSS3 with a new one?

[Retired-Kay]

Hi coremax, 

This would suggest the Sure Signal is faulty. 

Details on arranging a repair can be found here.

Thanks,

Kay 

[coremax]

Thanks Kay and James,

I'll stop by at the local vodaphone shop tomorrow and leave the unit.