DSL Service Deterioration - the new solution
DSLnoise
Enthusiast - Level 2
On March 18th, there was a refrain on my DSL service. My service was 3360/640 with no sync problems. This was degraded from the 3360/864 I had for many years. Now I have 1184/448. I contacted them to report trouble with my DSL service and they sent a technician who performed no DSL testing whatsoever and said my line is fine. Today they called and informed me that they are pleased to offer me a discount of $10/month for 12 months for my trouble and inconvenience. So the new solution for a trouble report is to refuse to repair my service, reduce my tier to a lower tier, and offer me a discount which is the standard price. I had 3360/864 ADSL2+ FAST for years...
0 Likes
1 Solution

Correct answers
Re: DSL Service Deterioration - the new solution
DSLnoise
Enthusiast - Level 2

The problem was decreased noise margins on the line.  After several tech visits and nothing being resolved, the problem somehow corrected itself several days after the strike. I still don't have 3360/864 ADSL2+ FAST, but the DL side is 3360.

View solution in original post

0 Likes
Re: DSL Service Deterioration - the new solution
dslr595148
Community Leader
Community Leader

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 non D-Dlink modem?

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

a) What is the brand and model of your non D-Dlink 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?

0 Likes
Re: DSL Service Deterioration - the new solution
DSLnoise
Enthusiast - Level 2

The problem was decreased noise margins on the line.  After several tech visits and nothing being resolved, the problem somehow corrected itself several days after the strike. I still don't have 3360/864 ADSL2+ FAST, but the DL side is 3360.

0 Likes