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

Ask

2

Reply

3

Solution

V3 Problems (Power flashing & solid Amber Service light)

Hambroski
4: Newbie

Please  note that this is a different problem to the one raised for a different serial number v3 unit.

 

I am trying to install 40124108412 and 40124107836 at PE31 8AE.

 

The FAQ does not appear to be relevant due to not covering v3 and also not covering the symptom.

I previously had a v1 box 21196758813 working here fine.

 

On both V3s I get a flashing red and a solid amber on the service light. No sign of internet and user lights.

 

I have amended the router to allow port access for:

Port 50 - TCP/IP
Port 4500 - UDP
Port 500 - UDP
Port 123 - UDP

Port 8 - TCP/IP

Port 1723 (BT Customers only) - TCP/UDP

 

My IP Address is:86.133.19.212

Speednet - 38ms Download 6.8mbps Upload 0.34mbps

Pingtest - 0% lost, Ping 37ms, Jitter 9ms

 

 

I have put one in the DMZ but this makes no difference. 

 

Traceroute via the router shows:

 

traceroute to 212.183.133.177, 30 hops max

  1  217.47.93.250         40 ms

  2  217.47.93.161         30 ms

  3  213.1.69.86           30 ms

  4  217.41.168.102        40 ms

  5  217.41.168.49         30 ms

  6  217.41.168.107        30 ms

  7  109.159.249.64        30 ms

  8  109.159.249.33        40 ms

  9  213.121.193.97        30 ms

 10  195.66.224.124        40 ms

 11  85.205.116.6          40 ms

 12 Request timed out.     *

 13 Request timed out.     *

Trace complete.

 

Please can you help

122 REPLIES 122

Hi Hambroski,

 

You can use more than one Sure Signal on a network providing it has the bandwidth to cope with both units.

 

The light sequence that you have mentioned relates to an issue with the Sure Signal performing the location lock to complete the set up, I would recommend de-registering that unit and registering it again to allow the setup process to begin again.

 

James

Gosh darnit - Netgear support is pretty awful. They cannot get it to work but that doesnt seem to mean anything to them - they believe my case is isolated and if the store will take it back i can exchange it and all will be well - that seems unlikely to me. I don't understand why they don't take some ###### responsibility and offer to send me a unit which they know works - how hard could that be? Anyway - Currys need Netgear to say it's faulty as it's been over a month since i started this nonsense and now i'm trying to persuade them to do that although they seem trained to avoid any talk of that kind. Trouble is that i dont know what to swap it for - a Belkin seems to be the only alternative Currys have but it gets quite poor reviews.

 

Does anyone have any suggestions on a fabulous quality router around £100-150 for regular phone line broadband with fabulous wireless and at least 4 ethernet ports that WORKS WITH THE VSS?

 

If i exchange the router and it ends up being the VSS at fault then i will probably kill somebody, or at least slap them about a bit.

god, is ###### a swear word? sorry about that - how about flipping?

robinv2,

 

I have the same problem with the same router model and version and I might be starting to get somewhere.  Can you do a log capture on the router and post the result.

 

Under Advanced -> Administration -> Logs.  Include all items in the log.  Wait for 5 minutes and press refresh.  What I think I'm seeing is the VSS constantly requesting DHCP from the router every 30 seconds.  I don't know why this is happening yet but there seems to be some incompatibility somewhere.  I've used a different dhcp server and the VSS power light goes solid and moves to the next stage of its set-up.  If you happen to be able to use a different machine as a DHCP server (maybe a windows or Linux machine) then you could try that.

 

Mark.

I still have the problems on my DGND3700. I tried my Vss v.3 on another network over Xmas and it connected with no configuration changes. It is starting to look like a Netgear issue. The only thing that is strange is that my VSS v2 worked for abount 4-6 months on this exact router and configuration. It only failed in November when the VSS firmware update was rolled-out. The VSS v3 has never worked on my network, and the config setting are the same as they have always been! 

You mean something like this?

[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:40:46       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:40:14       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:39:42       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:39:07       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:38:33       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:38:00       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:37:28       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:36:57       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:36:25       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:35:53       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:35:20       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:34:45       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:34:10       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:33:38       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:33:06       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:32:34       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:32:00       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:31:28       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:30:55       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:30:22       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:29:50       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:29:18       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:28:46       
[DHCP IP: (192.168.0.11)] to MAC address 00:1E:8F:C7:B4:5C Thursday, January 03,2013 09:28:24       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:28:12       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:27:40       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:27:08       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:26:37       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:26:05       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:25:32       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:25:00       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:24:27       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:23:55       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:23:20       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:22:45       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:22:13       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:21:38       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:21:04       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:20:30       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:19:57       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:19:24       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:18:50       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:18:15       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:17:42       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:17:09       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:16:36       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:16:04       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:15:32       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:15:00       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:14:28       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:13:57       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:13:25       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:12:54       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:12:22       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:11:49       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:11:17       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:10:46       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:10:14       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:09:40       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:09:06       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:08:33       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:08:01       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:07:29       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:06:56       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:06:23       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:05:48       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:05:16       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:04:42       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:04:10       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:03:37       
[DHCP IP: (192.168.0.3)] to MAC address 0C:4C:39:08:81:CE Thursday, January 03,2013 09:03:06  

 

My assumption is that the VSS is trying to do something - can't - and then tries again. I'm off to Curry's tomorrow (hopefully) to exchange it for something else - anything else.

That's right.  Good to see that you're getting the same behaviour from your VSS as me.  I've done some network sniffing and I can see that the VSS has accepted the DHCP request from the NetGear, this will be the same for you, so I think we can confirm that the DHCP is working corectly.  For reasons only known to the VSS it will not respond to ping in this state and when it fails to connect to Vodafone it starts from the DHCP request again.

 

I'm now going to try and get a better network trace to see if I can find out what service it is failing to get through.  I do know that the VSS does work with the NetGear as I can get the VSS to work if I connect it behind another NATed Firewall before the NetGear, and strangely this works.  So we know the VSS is good.  At the moment it seems to point to a port translation issue.

 

One thing I'm also going to try is to add a rule in the firewall to allow All to the VSS address but with logging enabled on this rule.  I hope to see the NetGear show all the connections it is allowing through to the VSS in the log as you've shown below.

 

I would not change the NetGear yet.

 

Mark.

Thanks Mark, that's very interesting and i understand some of it. A lot of my frustration with Netgear is that they are supposed to be the experts at telecomunications and yet couldn't seem to answer direct questions or offer anything other than a copy/paste script response. I build computers for a living so i'm not an idiot, but i'm not a network or comms engineer and so it's great to hear from someone who actually knows something in this area!

 

Anyway, i've ordered a cheap modem as a backup/spare which i'll test before exchanging the Netgear - if you do find a solution that would be a marvellous thing :Smiling:

Not sure if this will make a difference but I did find that when I setup my old netgear router which worked that some of the settings I had done were not required. For example it doesn't need to be in the DMZ, but changing the MTU from 1500 back to the default which I think was about 1450 did stop it working.

 

Try setting the MTU to 1500 - you never know :smileysurprised:

Setting the MPU to 1500 - doesn't work - Netgear suggested this but the router will only allow up to 1458

Don't ask me why it's different to yours - who knows - Netgear didn't :smileyembarrassed: