Child Item

Site Totals

61410 Questions Answered 270 Categories

DSL slow, router needs frequent resets.

Hi everyone. My DSL has been dialup slow the last week and a half or so, and I'm not sure what the issue is. Both speedtest.net and Verizon's own speedtester show speeds less than 2mbps, while my router shows a downstream speed of 7304 kbps. I'm paying for the 7.1-15mbps tier, though I haven't ever gotten speeds like that (which is another issue altogether.)

I also have to frequently reset my router to factory settings. At least a couple times a week I'll completely lose my connection, and the only way to get it back is to reset to factory settings.

It's only me and my girlfriend using the wifi. I have it set to WPA2, and we only ever have 5 items connected (two laptops, two smartphones, and a PS3.) I've got no idea if this is a router issue, or an ongoing network issue.

Any ideas?

Comments

dslr595148

See the info from your other thread

http://forums.verizon.com/t5/High-Speed-Internet-DSL-and-Dial/Slow-service-after-moving-and-phantom-pending-order/m-p/615288

tavisc

Thanks, but I'm not sure how that's supposed to help. I'm not even at the same address that I was when I posted that, and if you read my OP, I said that this issue has just started in the last couple weeks.

tavisc

Here's my modem info:

Firmware Version:	GT784WN-VZ-1.1.6
Model Number:	GT784WNV
Serial Number:	{edited for privacy}
WAN MAC Address:	00:7f:28:98:d3:b6
Downstream Rate:	6795Kbps
Upstream Rate:	763Kbps
PPP User Name:	Newdsl
ISP Protocol	PPPoE
Encapsulation:	LLC
Gateway IP Address:	{edited for privacy}
DNS Address #1:	71.242.0.12
DNS Address #2:	71.250.0.12

I ran a Verizon speedtest just before this post, and it shows me getting 2.59 down, and .68 up.

Here's the traceroute:

news.giganews.com

traceroute to {edited for privacy}, 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 ash-bb1-link.telia.net (213.248.70.241) 27 ms 27 ms 27 ms
3 ash-b2-link.telia.net (213.155.137.225) 0 ms 0 ms ash-b2-link.telia.net (80.91.245.109) 0 ms
4 TenGigE0-0-0-10.GW1.IAD8.ALTER.NET (152.179.50.233) 10 ms 2 ms 10 ms
5 so-0-0-0-0.ALT2-CORE-RTR2.verizon-gni.net (130.81.20.65) 12 ms 12 ms 12 ms
6 A1-0-1723.ALTNPA-STCGPAES-ERXG04.verizon-gni.net () 15 ms 14 ms 14 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * Max number of unresponsive hops reached (firewall or filter?)

news-europe.giganews.com

traceroute to {edited for privacy}, 30 hops max, 60 byte packets
1 vl201.gw1.ams.giganews.com (216.196.110.3) 11 ms 11 ms 11 ms
2 te7-8.ccr01.ams05.atlas.cogentco.com (149.11.104.17) 146 ms te7-7.ccr01.ams05.atlas.cogentco.com (149.11.104.9) 146 ms te7-8.ccr01.ams05.atlas.cogentco.com (149.11.104.17) 146 ms
3 te0-3-0-6.mpd21.ams03.atlas.cogentco.com (130.117.2.105) 1 ms te0-7-0-28.mpd22.ams03.atlas.cogentco.com (154.54.72.54) 2 ms te0-0-0-1.ccr21.ams03.atlas.cogentco.com (130.117.0.81) 0 ms
4 be2276.ccr22.lon13.atlas.cogentco.com (154.54.36.57) 8 ms be2182.ccr21.lpl01.atlas.cogentco.com (154.54.77.246) 10 ms be2288.mpd22.lon13.atlas.cogentco.com (154.54.62.149) 8 ms
5 be2347.ccr21.jfk02.atlas.cogentco.com (154.54.27.141) 80 ms be2386.ccr21.bos01.atlas.cogentco.com (154.54.44.161) 76 ms 76 ms
6 be2148.ccr21.dca01.atlas.cogentco.com (154.54.31.117) 86 ms be2095.mpd21.jfk02.atlas.cogentco.com (154.54.30.37) 84 ms be2094.ccr21.jfk02.atlas.cogentco.com (154.54.30.13) 82 ms
7 be2113.ccr41.iad02.atlas.cogentco.com (154.54.6.169) 87 ms be2150.mpd21.dca01.atlas.cogentco.com (154.54.31.129) 88 ms be2149.ccr22.dca01.atlas.cogentco.com (154.54.31.125) 90 ms
8 be2177.ccr41.iad02.atlas.cogentco.com (154.54.41.205) 89 ms verizon.iad01.atlas.cogentco.com (154.54.10.226) 98 ms uunet.iad01.atlas.cogentco.com (154.54.13.138) 120 ms
9 verizon.iad01.atlas.cogentco.com (154.54.12.46) 115 ms 119 ms uunet.iad01.atlas.cogentco.com (154.54.13.138) 115 ms
10 A0-0-1722.ALTNPA-STCGPAES-ERXG04.verizon-gni.net (130.81.195.151) 106 ms so-0-0-0-0.ALT2-CORE-RTR1.verizon-gni.net (130.81.20.165) 125 ms 109 ms
11 A0-0-1722.ALTNPA-STCGPAES-ERXG04.verizon-gni.net (130.81.195.151) 124 ms A1-0-1723.ALTNPA-STCGPAES-ERXG04.verizon-gni.net () 121 ms 123 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * Max number of unresponsive hops reached (firewall or filter?)

Anyone have any ideas? Seems like there's a big discrepency between what I'm paying for, and what I'm actually getting.

adf5

I am having the same problem. About two weeks ago my bandwidth has dropped from 6.5Mbps to 2.9Mbps (down). Transceiver stats indicate 7000Mbps down. My upload is not affected however. I have run various bandwidth tests on a completely clean machine, have reset the modem a dozen times and connect it straight to the computer. I am going to give a call this weekend and see if they can send out a new modem, this is ridiculous.

smith6612

@tavisc wrote:
Here's my modem info:

Firmware Version:

GT784WN-VZ-1.1.6

Model Number:

GT784WNV

Serial Number:

{edited for privacy}

WAN MAC Address:

00:7f:28:98:d3:b6

Downstream Rate:

6795Kbps

Upstream Rate:

763Kbps

PPP User Name:

Newdsl

ISP Protocol

PPPoE

Encapsulation:

LLC

Gateway IP Address:

{edited for privacy}

DNS Address #1:

71.242.0.12

DNS Address #2:

71.250.0.12

I ran a Verizon speedtest just before this post, and it shows me getting 2.59 down, and .68 up.

Here's the traceroute:

news.giganews.com

traceroute to {edited for privacy}, 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 ash-bb1-link.telia.net (213.248.70.241) 27 ms 27 ms 27 ms
3 ash-b2-link.telia.net (213.155.137.225) 0 ms 0 ms ash-b2-link.telia.net (80.91.245.109) 0 ms
4 TenGigE0-0-0-10.GW1.IAD8.ALTER.NET (152.179.50.233) 10 ms 2 ms 10 ms
5 so-0-0-0-0.ALT2-CORE-RTR2.verizon-gni.net (130.81.20.65) 12 ms 12 ms 12 ms
6 A1-0-1723.ALTNPA-STCGPAES-ERXG04.verizon-gni.net () 15 ms 14 ms 14 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * Max number of unresponsive hops reached (firewall or filter?)

news-europe.giganews.com

traceroute to {edited for privacy}, 30 hops max, 60 byte packets
1 vl201.gw1.ams.giganews.com (216.196.110.3) 11 ms 11 ms 11 ms
2 te7-8.ccr01.ams05.atlas.cogentco.com (149.11.104.17) 146 ms te7-7.ccr01.ams05.atlas.cogentco.com (149.11.104.9) 146 ms te7-8.ccr01.ams05.atlas.cogentco.com (149.11.104.17) 146 ms
3 te0-3-0-6.mpd21.ams03.atlas.cogentco.com (130.117.2.105) 1 ms te0-7-0-28.mpd22.ams03.atlas.cogentco.com (154.54.72.54) 2 ms te0-0-0-1.ccr21.ams03.atlas.cogentco.com (130.117.0.81) 0 ms
4 be2276.ccr22.lon13.atlas.cogentco.com (154.54.36.57) 8 ms be2182.ccr21.lpl01.atlas.cogentco.com (154.54.77.246) 10 ms be2288.mpd22.lon13.atlas.cogentco.com (154.54.62.149) 8 ms
5 be2347.ccr21.jfk02.atlas.cogentco.com (154.54.27.141) 80 ms be2386.ccr21.bos01.atlas.cogentco.com (154.54.44.161) 76 ms 76 ms
6 be2148.ccr21.dca01.atlas.cogentco.com (154.54.31.117) 86 ms be2095.mpd21.jfk02.atlas.cogentco.com (154.54.30.37) 84 ms be2094.ccr21.jfk02.atlas.cogentco.com (154.54.30.13) 82 ms
7 be2113.ccr41.iad02.atlas.cogentco.com (154.54.6.169) 87 ms be2150.mpd21.dca01.atlas.cogentco.com (154.54.31.129) 88 ms be2149.ccr22.dca01.atlas.cogentco.com (154.54.31.125) 90 ms
8 be2177.ccr41.iad02.atlas.cogentco.com (154.54.41.205) 89 ms verizon.iad01.atlas.cogentco.com (154.54.10.226) 98 ms uunet.iad01.atlas.cogentco.com (154.54.13.138) 120 ms
9 verizon.iad01.atlas.cogentco.com (154.54.12.46) 115 ms 119 ms uunet.iad01.atlas.cogentco.com (154.54.13.138) 115 ms
10 A0-0-1722.ALTNPA-STCGPAES-ERXG04.verizon-gni.net (130.81.195.151) 106 ms so-0-0-0-0.ALT2-CORE-RTR1.verizon-gni.net (130.81.20.165) 125 ms 109 ms
11 A0-0-1722.ALTNPA-STCGPAES-ERXG04.verizon-gni.net (130.81.195.151) 124 ms A1-0-1723.ALTNPA-STCGPAES-ERXG04.verizon-gni.net () 121 ms 123 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * Max number of unresponsive hops reached (firewall or filter?)

Anyone have any ideas? Seems like there's a big discrepency between what I'm paying for, and what I'm actually getting.

Looks like your line is out of sync, but you could also be suffering from congestion. Please do the following:

Click on Status > Select DSL (WAN) Status. You should find a page giving information such as your DSL Connection's attenuation, error counts, the last time the line retrained, along with a full listing of speed and specs. IF you could post up this information, that would be great.

@adf: You may want to consider starting your own thread so we can troubleshoot this issue a bit further without confustion 🙂

Child Item