Connection just not usable
Enthusiast - Level 1

I've been unhappy with my DSL connection for a while and have called a number of times, had some slight improvements that don't last and this will be my last effort to get a usable connection before I look into changing to cable.  Here are upload and download speeds over the last 36 hours using Verizon Speed Test:

Down    Up

.024    .124

.804    .452

.892    .588

.300    .130

.890    .476

.892    .474

.068    .138

.429    .448

Transceiver Stats are as follows

Transceiver Statistics

Transceiver Revision A2pB020b3.d20h Vendor ID Code 4D54 Line Mode ADSL_G.dmt Data Path INTERLEAVED   Transceiver Information Down Stream Path Up Stream Path DSL Speed (Kbits/Sec) 1056 448 Margin (dB) 7.1 12.0 Line Attenuation (dB) 63.5 31.5 Transmit Power (dBm) 16.1 11.9


Current details of speed test:

Download  .408   Upload  .428

Analysis information:

Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
SendBufferSize set to [131768]
running 10s outbound test (client to server) . . . . . 428.08Kb/s
running 10s inbound test (server to client) . . . . . . 408.70kb/s

------ Client System Details ------
OS data: Name = Mac OS X, Architecture = x86_64, Version = 10.6.8
Java data: Vendor = Apple Inc., Version = 1.6.0_26

------ Web100 Detailed Analysis ------
Client Receive Window detected at 455040 bytes.
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 1545.99 msec; the Packet size = 1440 Bytes; and
No packet loss - but packets arrived out-of-order 0.36% of the time
This connection is sender limited 82.58% of the time.
This connection is network limited 17.41% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: ON
RFC 1323 Window Scaling: ON
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address

Any help will be greatly appreciated.


Re: Connection just not usable
Specialist - Level 1

This is an issue you'll need to contact Verizon for help with. Here's the direct link to Residential Support:

Here are links with all means to contact Verizon: The Chat link will load after the page is fully loaded.

Finally, the Verizon Troubleshooter has a number of resources that allow you to try and fix your issue, if that's the way you'd like to go:

Hope this helps.

Re: Connection just not usable
Enthusiast - Level 1

Thanks but that has never really solved the problem.  I have a 3 month trial with local cable company and will compare services.  I had hoped that some info from the forum might help but I've dealt with tech support many times before and find myself frustrated each time.

Re: Connection just not usable
Super User
Super User

Your modem seems to be suggesting that your line has some length to it. An attenuation of 63.5dB is pretty high. Your line isn't holding the correct sync rate (should be 1184kbps download, 448kbps upload) so it could use some work. Even though I know you are trialing out the Cable Company's service, we can see what can be done to improve the DSL service to make it obtain the speeds you're looking for.

It's hard to tell if your slow speed issue in regards to the sync rate is from poor line quality or if it is really from length, but as a test, what you can do is plug your modem into your NID to see if you can obtain better statistics at the NID. If they are much improved, you will need to just inspect/repair some wiring in your home to suit the DSL better. If there is no improvement, Verizon will need to improve the line on their end.

If there are still slower speeds occurring, you may be experiencing the Juniper/Litespan issue I've talked about in other forum threads. This requires someone with higher access to the network to fix, but I can direct you to that fix if it turns out your issue may be a result of this.