Child Item

Site Totals

61487 Questions Answered 271 Categories

Paying for 1.1-3 mbps...getting .90

Figured I'd try this forum before calling support. I'm signed up for the Enhanced DSL, but speed tests routinly come up around .90 mbps (download) and less than .3 (upload).

What can I do to improve the speed? I'd at least like to get what I'm paying for. FIOS is not available in my area.

Thanks

Comments

Rich_Pollock

Our speeds have tested at about 3.5mbps. Should be closer to 7. My area too. (La Habra) no FIOS. Surrounded by TWC and I can't get anything else besides TWC or DSL. Not in Uverse area (Fullerton).

Try rebooting your modem. Shut it down unpklug it and hit the reset button. See if that gets yoyu some more speed.

Also may want to try one of the programs such as Ascentive's Active Speed.

Rich

Weebutts

Thanks for the info Rich. I have tried all that, ran the speed optimizer, virus malware scans ect. Still tops out at .9mbps (on a good day). I'm wondering if its not the wiring in my house...or the phone lines. I do live in a semi-rural area.

If i cant get this improved I'll have to switch to cable internet.

dslr595148

Step one: Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that your non-bogan public IP Address will show up. It might shown up as the final hop (bottom-most line of the trace) might contain a hop with your IP address in it. Either remove that line or show only the first two octets. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.

For example this what I saw when I was using Verizon

news.giganews.com

traceroute to 71.242.*.* (71.242.*.*), 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 13 ms 13 ms 13 ms
2 ash-bb1-link.telia.net (213.248.70.241) 39 ms 7 ms 7 ms
3 TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (63.125.125.41) 4 ms 4 ms GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (63.65.76.189) 4 ms
4 so-7-1-0-0.PHIL-CORE-RTR1.verizon-gni.net (130.81.20.137) 6 ms 6 ms 6 ms
5 P3-0-0.PHIL-DSL-RTR11.verizon-gni.net (130.81.13.170) 6 ms 6 ms 6 ms
6 static-71-242-*-*.phlapa.east.verizon.net (71.242.*.*) 32 ms 32 ms 33 ms

Step two: Can you provide the Transceiver Statistics from your modem?

#3 If you don't know how to get that info:

a) What is the brand and model of your modem?

b) If you have a RJ-45 WAN port router connected to it: What is the brand and model of the RJ-45 WAN port router?

#4 If you have a RJ-45 WAN port router connected to the modem, even if you know how to get the Transceiver Statistics from the modem: What is the brand and model of the RJ-45 WAN port router?

Weebutts

Thanks for the reply.

I have the D Link DSL 2750b modem, connected to the pc by ethernet cable

news.giganews.com

traceroute to 72.92. (72.92.), 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) 0 ms 0 ms 0 ms
3 ash-b2-link.telia.net (213.155.137.229) 0 ms ash-b2-link.telia.net (213.155.130.91) 0 ms 0 ms
4 TenGigE0-0-0-10.GW1.IAD8.ALTER.NET (152.179.50.233) 9 ms 3 ms 3 ms
5 P0-4-0-0.PHLAPA-LCR-22.verizon-gni.net (130.81.22.61) 10 ms 10 ms 10 ms
6 P9-0.PHLAPA-FTWSPAFW-ERXG03.verizon-gni.net (130.81.33.171) 9 ms 10 ms P12-0.PHLAPA-FTWSPAFW-ERXG03.verizon-gni.net (130.81.136.81) 9 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * Max number of unresponsive hops reached (firewall or filter?)

news-europe.giganews.com

traceroute to 72.92. (72.92.), 30 hops max, 60 byte packets
1 vl201.gw1.ams.giganews.com (216.196.110.3) 0 ms 0 ms 0 ms
2 te7-8.ccr01.ams05.atlas.cogentco.com (149.11.104.17) 0 ms 0 ms te7-7.ccr01.ams05.atlas.cogentco.com (149.11.104.9) 0 ms
3 te0-7-0-4.ccr21.ams03.atlas.cogentco.com (130.117.1.81) 0 ms te0-0-0-1.ccr22.ams03.atlas.cogentco.com (130.117.1.105) 0 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 multi-use.cogentco.com (154.54.62.145) 9 ms 8 ms
5 be2285.ccr21.lpl01.atlas.cogentco.com (130.117.49.126) 27 ms be2284.ccr22.lpl01.atlas.cogentco.com (130.117.49.38) 32 ms be2285.ccr21.lpl01.atlas.cogentco.com (130.117.49.126) 62 ms
6 be2286.mpd22.lon13.atlas.cogentco.com (130.117.50.73) 95 ms te0-2-0-3.ccr21.bos01.atlas.cogentco.com (154.54.31.189) 97 ms be2286.mpd22.lon13.atlas.cogentco.com (130.117.50.73) 92 ms
7 be2097.mpd22.jfk02.atlas.cogentco.com (154.54.30.117) 98 ms te0-3-0-4.ccr21.bos01.atlas.cogentco.com (154.54.30.129) 101 ms be2097.mpd22.jfk02.atlas.cogentco.com (154.54.30.117) 118 ms
8 be2150.mpd21.dca01.atlas.cogentco.com (154.54.31.129) 116 ms be2149.ccr22.dca01.atlas.cogentco.com (154.54.31.125) 110 ms be2150.mpd21.dca01.atlas.cogentco.com (154.54.31.129) 150 ms
9 be2112.ccr41.iad02.atlas.cogentco.com (154.54.5.233) 106 ms be2113.ccr41.iad02.atlas.cogentco.com (154.54.6.169) 146 ms be2112.ccr41.iad02.atlas.cogentco.com (154.54.5.233) 116 ms
10 uunet.iad01.atlas.cogentco.com (154.54.13.138) 158 ms 174 ms verizon.iad01.atlas.cogentco.com (154.54.12.46) 140 ms
11 uunet.iad01.atlas.cogentco.com (154.54.13.138) 147 ms B300.PHLAPA-LCR-21.verizon-gni.net (130.81.163.125) 163 ms P0-15-0-0.PHLAPA-LCR-21.verizon-gni.net (130.81.199.19) 222 ms
12 P0-15-0-0.PHLAPA-LCR-22.verizon-gni.net (130.81.199.21) 256 ms P10-0.PHLAPA-FTWSPAFW-ERXG03.verizon-gni.net (130.81.136.79) 249 ms B200.PHLAPA-LCR-21.verizon-gni.net (130.81.199.203) 160 ms
13 P12-0.PHLAPA-FTWSPAFW-ERXG03.verizon-gni.net (130.81.136.81) 232 ms * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * Max number of unresponsive hops reached (firewall or filter?)

dslr595148

#1 When you look for the Transceiver Statistics, this text gives to you an idea of what to look for:

Line Mode, Data Path:, Transceiver Information Down Stream Path Up Stream Path, DSL Speed (Kbits/Sec), Margin (dB), Line Attenuation (dB), and Transmit Power (dBm).

#2 As where the Transceiver Statistics are located in the DLink 2750:

To my knowledge, no one has managed to find and report the location of the Transceiver Statistics page on the D-Liink mode, so we'll need Verizon to grab the stats from the DSLAM, and while they're at it, check the logs on their end to see if the line is dropping out physucally, or is dropping out on another sense.

Weebutts

Ok, so whats my next step? Call support?

Child Item