- Community home
- Community
- Archive
- Sure Signal V3 not working even after resetting
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Ask
Reply
Solution
Sure Signal V3 not working even after resetting
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
07-11-2015 01:48 PM
Power - flashing, Internet - solid orange, In Service - off, In Use - solid orange reset done and router checked please help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
12-11-2015 02:04 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
12-11-2015 05:43 PM
Hi Peter,
There is currently an issue with Virgin media and the Sure Signal.
Check this link for further info........
http://forum.vodafone.co.uk/t5/Vodafone-Sure-Signal/Sure-Signal-Outage-on-Virgin-Media/td-p/2448467
Regards,
Mike.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
12-11-2015 02:37 PM - edited 12-11-2015 02:38 PM
My sure signal stopped working, I noticed this yesterday although it could of course have occure earlier
My sure signal is now in the following state
Light 1 red flashing
Light 2 solid orange
light 3 off
Light 4 solid orange
I have tried resetting the sure signal and restarting the broadband
Speedtest
Ping 10ms
Download speed 125.78Mbps
Upload 11.7111Mbps
s/n 40132203585
trace result
1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 6 ms 17 ms 8 ms 10.27.136.1
3 11 ms 8 ms 10 ms nrth-core-2b-xe-121-0.network.virginmedia.net [80.3.131.33]
4 * * * Request timed out.
5 13 ms 45 ms 9 ms nrth-bb-1b-ae0-0.network.virginmedia.net [62.254.42.130]
6 24 ms 24 ms 10 ms tele-ic-4-ae0-0.network.virginmedia.net [62.253.174.18]
7 42 ms 15 ms 15 ms ldngw1.arcor-ip.net [195.66.224.209]
8 12 ms 12 ms 11 ms 85.205.0.86
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
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.
Hopefully someone can help
Best regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
13-11-2015 03:33 PM - edited 13-11-2015 03:36 PM
Having the same problem as well. We're in Bromley and have used VFSS/VM set-up flawlessly since Aug 2014, but since about 2 Nov we're getting zero signal and yellow indications exactly as described above. Annoying because we can't use mobile at home. Though all other aspects of VM set-up including TV and wifi working normally. Rang VF twice with no resolution, and tried to call them a third time but hung up after 45min wait (!!). Whole point of VFSS is that it should work on any line, so shouldn't blame compatibility issues with VM!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
13-11-2015 04:08 PM
Just got off the phone with VF after ages on hold and am very disappointed. Technical team still have no indication of when this will be resolved - could be days, weeks or even months. Totally unacceptable and we're considering switching mobile providers. We simply cannot go without a mobile signal at home for much longer; and are also annoyed by the lack of regular updates.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
13-11-2015 04:51 PM
At least you got a reply. I just got cut off and then they sent me a text pointing me to this forum, which they seem to be ignoring.
I am not as badly off as some people here; I can get a signal in some upper rooms of my house, but nonetheless it's a pain and we've paid money for the service, so surely someone on their customer care team could spare five minutes to tell us what's going on?
Frankly, if I were told what they thought the problem was, what they were doing to fix it and roughly how long it would take, I wouldn't be too bothered and I'd just grin and bear it.
But just being treated as garbage that they don't even feel they need to communicate with makes me feel very bad about them. I've been with them since I was one of their very first customers in 1985 (0836 507333 - those were the days!), that's 30 years, so I feel a certain amount of loyalty and affection, but just to be treated like ##~## makes all that loyalty float away.
Oh, and if I go, so does my whole company, which is quite a big deal :smileymad:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
13-11-2015 05:22 PM
Hi all,
I am having exactly the same issue here. Have spoken to both VM and VF. VM very helpful and did various troubleshooting and they set up port forwarding on my router, but the same issue.
VF said it was a known issue and should be resolved in days. However it has been days and I am now coming here to hopefully get a VF person to review.
Tracing route to 212.183.133.177 over a maximum of 30 hops
1 7 ms 7 ms 4 ms routerlogin.net [192.168.0.1]
2 * * * Request timed out.
3 19 ms 14 ms 14 ms nott-core-2a-xe-200-0.network.virginmedia.net [
0.1.79.253]
4 * * * Request timed out.
5 * * * Request timed out.
6 38 ms 23 ms 24 ms nrth-bb-1b-ae1-0.network.virginmedia.net [62.25
.42.218]
7 20 ms 21 ms 22 ms tele-ic-4-ae0-0.network.virginmedia.net [62.253
174.18]
8 26 ms 24 ms 25 ms LDNGW1.arcor-ip.net [195.66.224.209]
9 29 ms 21 ms 23 ms 85.205.0.93
10 * * * Request timed out.
11 * * * Request timed out.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
13-11-2015 06:03 PM
I concur with what has been said before. We have one suresignal at one office which stopped working on 10th November, and the second at office 2 which stopped working on 12th November.
As per other people, we have zero VF coverage in our offices and rely 100% on the suresignal for mobile phone coverage.
I had to leave the office at lunchtime and drive 5 miles to find out whether I have any messages. OK for today, but can't live with that ongoing.
Trace routes have been done by several people posted on this forum, with the last hop going to an 85.205 address. This address range is owned by Vodafone Group Services.
Today, with calls being made between VF and VM I have spend in the order of 2 hours being passed between the two companies, neither wishing to take any responsibility, nor providing sufficient data for any meaningful investigation work to be undertaken.
VM are absolutely catagoric that there is nothing on their network which would cause an issue with traffic flow, and the tracert does show a correct route into the Vodafone network. Whether there is a specific port that the SS uses which is being blocked is another matter?
Vodafone suresignal tech support say that have received "a lot" of calls regarding suresignals of all variants which have stopped working, and all are on the VM network.
They have confirmed that we will receive compensation, but knowing VF this will be a paltry amount if indeed they keep this promise.
They say they are working closely with VM to resolve the issue, however VM third line support say they are not - VM said that in their opinion the problem is within Vodafone and Vodafone know it is. They could not explain why on the forums the problem does indeed seem to be limited to VM customers.
Tracing route to 212.183.133.177 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.50.254
2 1 ms 1 ms 1 ms 94-130-12-86.static.virginm.net [86.12.130.94]
3 6 ms 6 ms 6 ms brhm-lam-2-tenge23-2595.network.virginmedia.net
[62.255.59.114]
4 6 ms 6 ms 6 ms brhm-core-2b-xe-1101-0.network.virginmedia.net [
213.106.231.249]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 10 ms 11 ms 11 ms lndgw2.arcor-ip.net [195.66.224.124]
9 11 ms 11 ms 11 ms 85.205.0.86
10 * * * Request timed out.
11 * * * Request timed out.
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.
Has anyone more technical than me done a packet trace on a SS to find out what it does? Does it use any unusual port numbers in its communication back to VF?
Thanks again to VF for consistency of really poor customer service.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
13-11-2015 06:20 PM
Information as requested by post from Sarah at VF
Virgin Media business service
Ping 19ms
Download 27.95Mbps
Upload 19.54Mbps
Public IP 86.12.130.89
SS s/no 42144631654
Tracing route to 212.183.133.177 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.50.254
2 1 ms 1 ms 1 ms 94-130-12-86.static.virginm.net [86.12.130.94]
3 7 ms 6 ms 6 ms brhm-lam-2-tenge23-2595.network.virginmedia.net
[62.255.59.114]
4 6 ms 6 ms 6 ms brhm-core-2b-xe-1101-0.network.virginmedia.net [
213.106.231.249]
5 * * * Request timed out.
6 21 ms 6 ms 5 ms brhm-bb-1c-ae0-0.network.virginmedia.net [62.254
.42.110]
7 * * * Request timed out.
8 12 ms 12 ms 11 ms lndgw2.arcor-ip.net [195.66.224.124]
9 11 ms 11 ms 11 ms 85.205.0.86
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
Vodafone - will you please tell us what the specifics are as to why this problem exists and who is responsible for fixing it, and when?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
13-11-2015 06:35 PM
My tracert is nearly identical:
Tracing route to 212.183.133.177 over a maximum of 30 hops
1 1 ms 1 ms 1 ms routerlogin.net [192.168.0.1]
2 38 ms 11 ms 23 ms cpc69762-epso4-2-0-gw.6-3.cable.virginm.net [86.7.63.1]
3 13 ms 9 ms 13 ms hers-core-2a-ae7-1820.network.virginmedia.net [80.3.33.85]
4 29 ms 13 ms 19 ms brnt-bb-1c-ae21-0.network.virginmedia.net [62.254.42.33]
5 * * * Request timed out.
6 * * * Request timed out.
7 39 ms 17 ms 20 ms brhm-bb-1c-ae1-0.network.virginmedia.net[62.254.42.210]
8 * * * Request timed out.
9 22 ms 20 ms 21 ms lndgw2.arcor-ip.net [195.66.224.124]
10 16 ms 24 ms 20 ms 85.205.0.86
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
It does seem to be stopping within the VM network, not the VF.
