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

Ask

2

Reply

3

Solution

VSS v3 Red Power Light Slow Flashing Internet Light

will76
2: Seeker
2: Seeker

Hi,

Has the V3 VSS for about 3 months, hasn't worked for a month or so now.

Tried all the resets, done the port forwarding.

S/N is 40132755022

Service Provider is BT, Home Hub 3

If I do the tracert it fails immediately, makes no hops at all, I suspect that this is the problem?

 

9 REPLIES 9

will76
2: Seeker
2: Seeker

External IP address 81.152.252.9

Ping 21ms Jitter 4ms

Download 38Mbps Upload 9Mbps

 

Retired-Andy
Moderator (Retired)
Moderator (Retired)

Hi will76,

 

If the traceroute fails immediately, this does suggest a connection issue is the cause.

 

Try swapping out the Ethernet cable for a different one to see if this helps.

 

Also, check to make sure the following ports are open/forwarded on your router:-

 

Port Number

 

8          TCP      UDP

50         TCP      UDP

53         TCP      UDP

67                     UDP

68                     UDP

123                   UDP

500                   UDP

1723     TCP      UDP

4500                 UDP

33434 - 33445    UDP

 

Another thing to try is to disconnect the Sure Signal from the router and then switch both devices off.

 

Restart the router and once it’s back online, reconnect and switch on the Sure Signal.

 

Let me know how you go on.

 

Cheers,

 

Andy

Hi, I have all the ports forwarded, enabled port clamping, disabled UPnP, and placed the suresignal in the DMZ (read through a lot of topics on here)

Still no improvement, power light on, internet light flashes for a while, then goes off, then flashes again.

Tried all manner of resets, power, cables etc.

The sure signal is connecting as it gets a DHCP address from the router and it shows as connected on the router config pages.

What is causing the tracert to fail immediately? Anything I can do to test around this issue further (could it be something, firewall or AV on the laptop?)

21:09:35, 14 Jan.( 1774.540000) Lease for IP 192.168.1.78 renewed by host Unknown-b0:46:fc:9e:bf:17 (MAC b0:46:fc:9e:bf:17). Lease duration: 1440 min
21:09:35, 14 Jan.( 1774.540000) Device connected: Hostname: Unknown-b0:46:fc:9e:bf:17 IP: 192.168.1.78 MAC: b0:46:fc:9e:bf:17 Lease time: 1440 min. Link rate: 100.0 Mbps
21:09:35, 14 Jan.( 1774.490000) Lease requested
21:09:26, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:09:26, 14 Jan.IN: ACCEPT [54] Connection opened (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:08:56, 14 Jan.( 1735.570000) Wire Lan Port 2 up
21:08:53, 14 Jan.( 1732.600000) Device disconnected: Hostname: Unknown-b0:46:fc:9e:bf:17 IP: 192.168.1.78 MAC: b0:46:fc:9e:bf:17
21:08:53, 14 Jan.( 1732.570000) Wire Lan Port 2 down
21:08:39, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:08:39, 14 Jan.IN: ACCEPT [54] Connection opened (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:08:18, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60172    <-->109.150.24.110:60172  [173.194.78.109:993] CLOSED/CLOSED ppp1 Route)
21:08:16, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:08:16, 14 Jan.IN: ACCEPT [54] Connection opened (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:08:08, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60172    <-->109.150.24.110:60172  [173.194.78.109:993] CLOSED/CLOSED ppp1 Route)
21:08:08, 14 Jan.( 1687.080000) Lease for IP 192.168.1.78 renewed by host Unknown-b0:46:fc:9e:bf:17 (MAC b0:46:fc:9e:bf:17). Lease duration: 1440 min
21:08:08, 14 Jan.( 1687.080000) Device connected: Hostname: Unknown-b0:46:fc:9e:bf:17 IP: 192.168.1.78 MAC: b0:46:fc:9e:bf:17 Lease time: 1440 min. Link rate: 100.0 Mbps
21:08:08, 14 Jan.( 1687.030000) Lease requested
21:08:04, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:08:04, 14 Jan.IN: ACCEPT [54] Connection opened (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:07:58, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60172    <-->109.150.24.110:60172  [173.194.78.109:993] CLOSED/CLOSED ppp1 Route)
21:07:58, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:07:58, 14 Jan.IN: ACCEPT [54] Connection opened (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:07:55, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:07:55, 14 Jan.IN: ACCEPT [54] Connection opened (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:07:53, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] CLOSED/CLOSED ppp1 Route)
21:07:53, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:07:53, 14 Jan.IN: ACCEPT [54] Connection opened (Port Forwarding: TCP  192.168.1.78:60173    <-->109.150.24.110:60173  [17.149.36.183:5223] SYN_SENT/SYN_RECV ppp1 NAPT)
21:07:45, 14 Jan.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP  192.168.1.78:60172    <-->109.150.24.110:60172  [173.194.78.109:993] CLOSED/CLOSED ppp1 Route)
21:07:29, 14 Jan.( 1648.410000) Wire Lan Port 2 up
21:07:26, 14 Jan.( 1645.440000) Device disconnected: Hostname: Unknown-b0:46:fc:9e:bf:17 IP: 192.168.1.78 MAC: b0:46:fc:9e:bf:17
21:07:26, 14 Jan.( 1645.410000) Wire Lan Port 2 down

Jenny
Moderator (Retired)
Moderator (Retired)

Hi will76,

 

Are you trying to do the traceroute whilst connected to a VPN (Virtual Private Network)? This can cause it to fail.

 

What colours are each of the lights as these can be either white or orange?

 

It’s also worth mentioning that we’re aware of an issue with the Home Hub 3 which you can see here.

 

Thanks,

 

Jenny 

OK, so I have got BT to supply a HH3 type B, done port clamping, port forwarding, reset the VSS and still the same problem.

Do i need another resysnch? Can you see my device connecting.

Red power light on, ethernet light pulsing on and off for nearly 2 days

HELP!!!!!

Retired-James
Moderator (Retired)
Moderator (Retired)

Hi will76,

 

It’s still not connected for the last couple of weeks.

 

Do you see any other lights other than the power light?

 

Are you using the same Ethernet cable that came with the Sure Signal?

 

If yes, can you try a different cable?

 

I’d also do a full reset to make sure it’s goes through the setup correctly.

 

-Locate the button on the base of the box next to the Ethernet ports.

-Press and hold the button for approximately 30 seconds.

-Release the button and wait for the device to be configured.

 

James

Hi, tried several cables, and now 3 different routers, reset my sure signal multiple times and you guys have done a resynch twice. I've tested the port forwarding works by forwarding them to my PC rather than the sure signal and it is all working.

I can only think that the sure signal is faulty now.

Retired-Ian_
Moderator (Retired)
Moderator (Retired)

Hi will76,

 

Thanks for that.

 

It may point towards the Sure Signal being faulty, but we need you to try the Sure Signal at another address to be certain.

 

Once you've done that, let us know what happens.

 

Thanks

 

Ian