After 2 weeks of calls to tech support and a visit from a technician this past weekend, my speed was back to near the 3 Mbps I'm provisioned. The technician "cleaned-up" some wiring in the box outside, and tested the line. He said everything looked great, and it could probably handle 5 Mbps.
However, as usual, that only lasts a couple of days, now I'm right back down to 1.3-1.7 Mbps. **bleep**??? I'm really getting tired of calling support every other day to get this back to "full speed".
Before anyone asks, I cannot provide transceiver stats, since my D-link 2750B does not offer this option.
Is there any way to get their "optimization" turned off, so that my speed is not cut in half every time there is a hiccup in the line?
Now, besides the speed being down again, I'm having intermittent connection problems. First thing in the morning, I'll try to get online, and it's down. The only way to restore Internet is to reboot the modem. Same thing when I get home from work. And all this after numerous calls to tech support, a new modem, and a visit from a technician.
Get the line reset again, the next time you call in, and point out something called ASSIA. Specifically, ask the Verizon rep to disable the ASSIA Optimizer on your line, and then turn the speed up to where it should be.
If the drop-outs continue, Verizon will need to tackle the problem as a line issue. Especially if the tech is saying 5Mbps isn't out of the ballpark. Without Transceiver Statistics I cannot validate the claim at all. To help us out, when you are on the phone with Verizon, ask the tech what your downstream attentuation and SNR is, along with your upstream SNR and attenuation. They should be able to supply this for you. If you can get this info and share it, that'd be awesome.
I re-connected my old Westell 2100 modem and was able to download the Westell Modem Browser ultility to get the following stats from the DSL tab. Speed test shows 1.40 Mbps down & 0.40 Mbps up with 55ms latency.
Noise Margin
Upsteam = n/a
Downstream = 16.5 dB
Output Power
Upsteam = n/a
Downstream = n/a
Attenuation
Upsteam = n/a
Downstream = 46.5 dB
Data Rate
Upsteam = 448 kbps
Downstream = 1792 kbps
FEC errors = 9
CRC errors = 2
HEC errors = 0
Signal Lost = 0
Frame Loss = 0
I checked again first thing this morning, and speed has been lowered even further.
As of 6:45am
Noise Margin
Upsteam = n/a
Downstream = 31.0 dB
Output Power
Upsteam = n/a
Downstream = n/a
Attenuation
Upsteam = n/a
Downstream = 46.5 dB
Data Rate
Upsteam = 448 kbps
Downstream = 1504 kbps
FEC errors = 0
CRC errors = 2
HEC errors = 0
Signal Lost = 0
Frame Loss = 0
Ok.
#1 An original or very old style NID with a spark gap and ground wire can even get spiders in it that could cause an issue. Inspect the NID first before thinking of changes or wiring.
http://en.wikipedia.org/wiki/Network_interface_device
http://en.wikipedia.org/wiki/Demarcation_point
Running a good quality wire CAT5, no need for CAT6, directly to the NID for the DSL modem jack may help. That is what I had done with mine. Depending on the number of loads or amount of wire in the house could also cause issues. But if the user's signal quality is not being pulled low due to a wiring issues, it would usually indicate a problem elsewhere. Unless there was noise being picked up on the premises wiring. Wire DSL directly to the NID and install a filter there for all other in house wiring may help. There used to be available what was called a NID Filter, and I am sure you can still get them.
Ideal Connection if house wiring is an issue, or very old, and lengthy. Install a filter / splitter at the NID.
Run CAT5 directly to the NID location, and install a dedicated jack for the DSL modem.
Remove all in house wiring from the NID.
Connect piece of CAT5 from the NID to the filter / splitter input
Connect all existing phone lines to the phone side of the filter output.
Connect the new DSL CAT5 directly to the NID before the filter / splitter, or to the DSL side of the filter / splitter, depending on the device purchased.
This will take all the existing premises wiring out of the picture unless there is a short circuit or excessive load somewhere in the house.
At this point all the single filters could be removed because the DSL is filtered at the NID.
http://www.homephonewiring.com/dsl.html
#2 You can test outbound to Giganews. But giganews has/had a test that will check your inbound connection from their servers to you.
I heard from another user that
Giganews is being watched very closely because of multipart binaries, and pirated material. MP3s and Video Content. 7 years ago you could get 10-20 MP3 albums in a single day, and that was with a 15/5 fios connection. So they started providing an encrypted connection service for an added fee. I have not messed with news groups for a very long time. Now with deep packet inspection, and other enforcement, I would not even think of it. No news I want there. But there may be content that people want? They may even be checking and limiting speed from that domain. Never tested. But let me see. It looks as if reverse trace routes and speed tests are being blocked by Verizon from Giganews to my router.
Reverse Traceroute
Tool news.giganews.com
traceroute to *.*.*.*, 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 te0-0-0-7.mpd22.iad02.atlas.cogentco.com (38.122.67.49) 0 ms 0 ms te0-7-0-9.mpd22.iad02.atlas.cogentco.com (38.122.62.193) 0 ms
3 te0-0-0-4.ccr21.iad02.atlas.cogentco.com (154.54.31.105) 0 ms 0 ms te0-2-0-0.ccr21.iad02.atlas.cogentco.com (154.54.31.101) 0 ms
4 uunet.iad01.atlas.cogentco.com (154.54.13.138) 28 ms verizon.iad01.atlas.cogentco.com (154.54.10.226) 40 ms uunet.iad01.atlas.cogentco.com (154.54.13.138) 28 ms
5 0.ae1.RES-BB-RTR2.verizon-gni.net (152.63.32.157) 41 ms 41 ms 0.ae2.RES-BB-RTR1.verizon-gni.net (152.63.34.22) 13 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * Max number of unresponsive hops reached (firewall or filter?)
#3 Have the provider run a local loop test to see if any problems are indicated. If there are, then they could run the test with everything in the house disconnected, except the new DSL modem connection. If issues are still indicated, then the DSL provider needs to make connections on the local loop. Another user told me that they had issues when it rained, and it was because construction had left a splice box open on a line somewhere.
I contacted Verizon Direct support on the the dslreports.com forums. The re-set my line and made a change to my profile. Everythng seems fine...for now.
Start a new topic or ask questions in the open forum.
