DSL Connection Dropping Intermittently.
MisterTechnical
Enthusiast - Level 3

Hi there. I am currently having an issue that appears to be commonplace among users in my area, as of late.

My problem is with a Westell 7500 series  (A90-750015-07). This router is new, only a month old or so, and is a replacement for an older Westell 3000 series that I had swapped out for the same issue (which actually may be working fine, see below.)

My DSL connection (Paying for High Speed Internet Enhanced) Is consistently dropping my net connection throughout the day, in such a manner that it interrupts Web Browsing, uploads, downloads, and games.The internet drops are not for long periods of time, but they are constant and this constant disconnection makes it difficult (if not, at times, impossible) to use my internet service.

I have made several calls to Technical Support, but apparently they have absolutely no idea as to what could be causing this issue. 

Rebooting the Router does not help solve the intermittent connectivitiy issues for any length of time, and neither does power cycling. My network adapter configuration settings are set so that my laptop may not turn off the adapter to save power; this does not work either.

I have tried multiple channels (even though there are no other LANs in my immediate area) , updating my drivers for my adapters, and even had multiple technicians come out and examine the wiring, to no avail.

I'd really like to believe verizon is a reputable and reasonable company, but that hope is quickly fading and being replaced with lividity. 

Can someone here help me troubleshoot or make some tweaks to my connection settings? The DSL light  on my router is solid, but my wireless connection continues to drop.  My connection works correctly and consistently at other wireless locations, though (College campus, for instance).

This is my transceiver stat sheet.

Transceiver RevisionA2pB020b3.d20h
Vendor ID Code4D54
Line ModeADSL_ANSI_T1.413
Data PathFAST
 
Transceiver InformationDown Stream PathUp Stream Path
DSL Speed (Kbits/Sec)3360608
Margin (dB)33.06.0
Line Attenuation (dB)36.031.5
Transmit Power (dBm)19.611.3
0 Likes
37 Replies
JOSEm441
Specialist - Level 2

Your stats are not too bad BTW except for upstream margin.  http://www.ubasics.com/node/38/print Another thing that would help is to hook up the new modem directly into the Network interface device (where the line from the pole connects to you home) and see if the stats are similar, this will help isolate the issue to in or out of the house.

Did you ever notice if your line mode was ADSL_2+ when things were working fine? Since I was swithed to ..another line mode my speeds have dropped also!

Also try removing all your Phones and filters to see if you can isolate a bad phone or  filter.

MisterTechnical
Enthusiast - Level 3

Your stats are not too bad BTW except for upstream margin.  http://www.ubasics.com/node/38/print

Do you think the upstream margin being so low could be causing this issue?

 Another thing that would help is to hook up the new modem directly into the Network interface device (where the line from the pole connects to you home) and see if the stats are similar,

I'll do this now.

Did you ever notice if your line mode was ADSL_2+ when things were working fine? Since I was swithed to ..another line mode my speeds have dropped also!

I haven't noticed, no. Ill confirm this today.

Also try removing all your Phones and filters to see if you can isolate a bad phone or  filter.

The line for this internet is dedicated, so voice or filters are not attached anywhere in the house. 

0 Likes
smith6612
Community Leader
Community Leader

Your downstream's doing pretty good. Your upstream however is bad and would be the source of your problems. Have you attached any new devices to your phone line recently? If you have Voice service with Verizon, do you have any static on the line or is voice quality poor? The upstream frequencies are cloest to the ones used by voice.

Also, if you could locate your NID. Take your modem to the NID, plug it into the NID using the test jack found inside of modern NIDs and obtain your newer statistics. If the stats are still bad at the NID, it's a Verizon Truck roll to get the problem fixed.

See this FAQ: http://www.dslreports.com/faq/1317

0 Likes
MisterTechnical
Enthusiast - Level 3

Problems still not solved, but I'm making progress.

I have to find the correct NID jack. 

0 Likes
smith6612
Community Leader
Community Leader

The correct jack in the NID may be the one that has something plugged into it. Most NIDs disconnect the house when the door is opened to access the individual test jack, but some have things plugged into them. Just unplug it, connect the modem, and then re-connect the house when done. My NID is like that above, so when I open it up, I also have to open the door to get to the jack and then disconnect my house from the port (it's just an RJ-11 terminated cable).

masho951
Enthusiast - Level 3

Most NIDs don't disconnect the house when the door is opened. They disconnect everything after the point at the NID when something is plugged into the RJ port. Is this a multi dwelling complex or a single family home? Looking at your tranceiver stats something is going on with the upload side. You're getting full bit rate with good SNR on the download side but less that full bit rate on the upload with bad SNR. If you haven't changed anything inside the house since the problem started to occur (assumming this is an existing line) then more than likely it's an outside issue.

MisterTechnical
Enthusiast - Level 3

Alright, update. Technician came out and replaced my pair and fixed a few minor shorts in the line. Wonderful. He tested the NID for me and got a fantastic signal. Still having the dropouts though.

Tests with pingplotter and other dsl line tests show that there is a specific hop in Washington D.C. that is dropping packets.

This person is having the same issue.

http://forums.verizon.com/t5/High-Speed-Internet-DSL-and-Dial/Constantly-losing-internet-connection-...

I am fully convinced that the intermittent packet loss is not on my end, as a technician JUST replaced everything worth replacing on my end, and I am using a new modem. Pingplotter is noting, as I said before, significant packet loss here:

P0-3-0-3.WASHDC-LCR-22.verizon-gni.net

Here is a line test I just did.

Test (From Central USA)LossMin
Latency
Avg
Latency
Max
Latency
Pass
Fail
basic ping
10s of 40 byte packets, 2 per second
0%53.4ms53.9ms55.3ms
pass
low bandwidth stream
10s of 512 byte packets at 56 kbit
90%60.0ms60.5ms62.1ms
fail
medium bandwidth streamwas not performed
higher bandwidth streamwas not performed
your first hop ping
stream of 40byte pings to 130.81.196.47
1% loss45.3msYou are 8ms
to your first hop

pass
 
 

1 minute MTR (hop loss analysis) from Central - USA
HopHostLOSSRcvSentBestAvgWorst
0ae-2.bb-c.slr.lxa.us.oneandone.net0%60600.280.360.53
1ae-10.bb-c.ms.mkc.us.oneandone.net0%60600.790.881.18
264.209.105.2330%606013.9426.39213.94
30.xe-8-2-0.BR3.CHI13.ALTER.NET0%606014.1418.8269.41
40.ae3.CHI01-BB-RTR1.verizon-gni.NET0%606014.4920.52163.89
5P0-4-0-0.WASHDC-LCR-22.verizon-gni.net0%606043.1443.7144.51
6P12-0.WASHDC-CHCHMDBE-ERXG04.verizon-gni.net32%416067.7174.1277.91
7(TARGET IP ADDRESS)2%596046.0173.8291.91

pass

1 minute MTR (hop loss analysis) from West Coast - USA
HopHostLOSSRcvSentBestAvgWorst
0h-67-100-37-242.noclli.covad.net0%60602.457.11158.24
1ge-6-14.car2.SanJose1.Level3.net0%60602.5313.72181.75
2ae-3-80.edge1.SanJose3.Level3.net0%60602.865.2564.99
3MCI-level3-20G.SanJose3.Level3.net0%60602.906.2477.99
40.ae3.SJC01-BB-RTR1.verizon-gni.NET0%60605.148.0591.32
5P0-14-0-0.WASHDC-LCR-21.verizon-gni.net0%606085.9086.2589.09
6P10-0.WASHDC-CHCHMDBE-ERXG04.verizon-gni.net62%236086.4087.7393.33
7(TARGET IP ADDRESS)49%316087.5398.30106.51

fail
0 Likes
masho95
Enthusiast - Level 3

Could you post the tranceiver statistics again since the technician made changes to the line? According to the packet loss that you are experiencing on that one hop it looks like Verizon's router is having trouble. The ERX04 is the router that your DSL line is on. Getting another service call to get the technician to place a change order to change the router would be a great next step especially if the upstream noise margin and bitrates improved. BTW with a 3360 downstream bitrate you should be at 864 for full bitrate on the upstream. That previous 600 number you had on the upstream with a 6 noise margin is no good. Good luck.

MisterTechnical
Enthusiast - Level 3

Upstream improved significantly; same techician also came back and is helping me recitfy the problem.

Apparently they're replacing their front end router now. Stay posted.

Transceiver Statistics
Transceiver Revision:7.2.3.0 
Vendor ID Code:4 
Line Mode:G.DMT Mode 
Data Path:Fast 
 
Transceiver InformationDownstream PathUpstream Path
DSL Speed (Kbits/Sec)3360864
Margin (dB)16.06.0
Line Attenuation (dB)21.511.0
Transmit Power (dBm)1.510.9



0 Likes
MisterTechnical
Enthusiast - Level 3

Verizon changed the front end router for my area. The problems seem to be gone at this point. Ill keep you posted. 

0 Likes
shall1
Enthusiast - Level 1

I have just started having the same issue after almost 2 years on DSL with a Westell A90-750015-07 modem from Verizon.  Yesterday in less than 1 hour, it dropped 4 times and I had to reboot..  Verizon tech support said they would monitor the line yesterday for four hours.  It never dropped again that day.  They mentioned a negative test result and then told me that was normal also (?) .  Then they monitored it for another 24 hours.  It dropped once, but Verizon claims there is no line issue, so therefore they can do nothing about the problem.  I use this line when working from some days.  They told it is caused by too much traffic on the line.  I live in a rural area in Western PA which is certainly not heavily populated.  When it was dropping yesterday both the DSL and Internet light went out on the modem.

If someone could tell me how to obtain the stats I am reading in this thread on the connection, I would love to try to track this issue down and figure out what the problem is.  It is annoying enough when it happens, let alone when I am using it for work on a day when I could not make the hour drive into the office.  Verizon service around here, even for just the phone is pretty poor.

0 Likes
dslr595148
Community Leader
Community Leader

@shall wrote:

If someone could tell me how to obtain the stats I am reading in this thread on the connection, I would love to try to track this issue down and figure out what the problem is.  It is annoying enough when it happens, let alone when I am using it for work on a day when I could not make the hour drive into the office.  Verizon service around here, even for just the phone is pretty poor.


In your case, this means:

Visiting http://192.168.1.1/ for me and do the following:

1: If you see a Blue and White Westell page, mouse over Troubleshooting, go to DSL, and choose Transceiver Statistics. Copy/Paste the information on that page.

2: If you see a Red and Black Westell page: Go to System Monitoring -> Advanced Monitors -> Transceiver Statistics. Copy/Paste the information on that page.

3: Try visiting http://192.168.1.1/transtat.htm which is a direct link to the Stats on older modems.

If you need a Username and Password, try the following:

admin/password

admin/password1

admin/admin

admin/admin1

admin/Serial Number.

* By Serial Number, I don't mean type in the words Serial Number. I mean find and type in the serial number found on the bottom of this router.

0 Likes
smith6612
Community Leader
Community Leader

Sounds great! The upstream statistics are improved but the margin is still a bit shoddy. If it's holding stabaly however, then it probably isn't an issue. Be awesome to see some additional speed added to your line once we've confirmed all issues are resolved.

0 Likes
MisterTechnical
Enthusiast - Level 3

Alllmost there. Connection is not dropping anymore, but there is packet loss that is causing lag.

Line Quality / Ping Test : Results
Anonymous test
 Tools page
 Test again
 Forum: Site Tools
 recent results from verizon.net
Test (From Central USA)LossMin
Latency
Avg
Latency
Max
Latency
Pass
Fail
basic ping
10s of 40 byte packets, 2 per second
0%45.8ms46.4ms48.1ms
pass
low bandwidth stream
10s of 512 byte packets at 56 kbit
10%52.0ms52.9ms63.1ms
fail
medium bandwidth streamwas not performed
higher bandwidth streamwas not performed
your first hop ping
stream of 40byte pings to 130.81.45.13
0% loss39.2msYou are 6ms
to your first hop

pass
Jitter/loss with small packets tested from Central - USA:
Jitter/loss with small packets tested from West Coast - USA:
Sooooo close to normal. So close. 
Im going to see what I can do to fix this once and for all. (Another) modem coming tomorrow, maybe thatll be easier to handle data from on verizons end. 
0 Likes
MisterTechnical
Enthusiast - Level 3

http://www.pingtest.net/result/63379293.png

^ My current packet loss. They said theyll fix it in 24-48 hours.

Its been three months since my net has been satisfactory.

0 Likes
smith6612
Community Leader
Community Leader

Unless your line is hitting a lot of errors and another modem is more tolerant to the noise, I doubt changing the modem is going to resolve the packet loss issue. I don't know why they keep sending you new ones when the DSLReports Line Quality Test simply relies on the modem/router itself to return packets. They always do unless there's something seriously wrong with the unit which would be noticed immediately. So, to sum it up, it's something on their end if there's packet loss. It always has been for every issue I've seen so far with the DSLReports Line Quality Test (granted, DSLReports might be having spasms but users don't report trouble that DSLReports shows if it's only DSLReports' servers having issues!)

0 Likes
masho951
Enthusiast - Level 3

Some lines will always test at 6.0db noise for the upstream. This happens when the line is served out of a remote DSLAM CATENA system. Could you post a new tracert log to verify that you actually got moved to a new router?

smith6612
Community Leader
Community Leader

@masho95 wrote:

Some lines will always test at 6.0db noise for the upstream. This happens when the line is served out of a remote DSLAM CATENA system. Could you post a new tracert log to verify that you actually got moved to a new router?



True. Just like the annoying 6dB bug with IKANOS systems as well. I guess we find out then if he's on a Catena just to confirm 🙂

0 Likes
The_Toddler
Newbie

How do things look today, MisterTechnical?

I've been having what I think is the same problem. I called Verizon tech support on Wednesday and the rep could tell there was some trouble in my line, but it coincided with some other outage in Georgetown, so she said she would call back last night before escalating the situation just in case the two problems were related.

She did call back, but the DSL service was almost back to normal. I had a few dropouts, things seemed to be pretty stable. The verizon rep said she would call back again on Tuesday. This morning service is a little more spotty. Nowhere near as bad as what it was this past week, but not as stable as it was last night.

The rep wasn't all that helpful, and sounded like she was from a foreign call center. I said I had seen many posts such as yours on the forum, and asked if she knew anything about the front end router being replaced as you said. Of course her reply was "No, the router is your modem." OK.

0 Likes
MisterTechnical
Enthusiast - Level 3

No problem. I used pingplotter so I saw the exact moment when the modem was replaced. 

Also, Verizon has been irritating me to an almost intolerable extent when I call for tech support repair. I now frequently get connected to technicians who agressively pressure me to upgrade to Fios. 

If I -wanted- to upgrade to FIOS, believe me I would have.  A nice man named Stuart also portrayed it as the "solution to my problems" in a phrasing / demeanor that sounded suspiciously like extortion, before adding that "technology is evolving" and that I should upgrade to keep up. 

It is -not- the tech support's job to recommend I pay more money for a service I do not want, because the company I am paying "does not want" to address my issue. They are gladly accepting my monthly payments, but when it comes to making sure I recieve adequate service -for- that money, their stubborness is almost pitiful. '

It is also amusing. If they cannot repair tthis grade of connection, why should they expect me to pay them MORE? Usually, people upgrade when they are given -reliable- and -adequate- service, moreso than out of necessity (And the necessity usually does not stem from the previous item/service being poor.)

usually, when the  above situation happens, people switch companies. 

Still major packet loss. A  much-nicer rep I called last night gave me a ticket number regarding the repair that should fix the issue, Ill call in regarding its progress soon.

Test (From Central USA)LossMin
Latency
Avg
Latency
Max
Latency
Pass
Fail
basic ping
10s of 40 byte packets, 2 per second
30%52.6ms53.7ms55.4ms
fail
low bandwidth stream
10s of 512 byte packets at 56 kbit
25%58.7ms59.7ms88.4ms
fail
medium bandwidth streamwas not performed
higher bandwidth streamwas not performed
your first hop ping
stream of 40byte pings to 130.81.46.83
0% loss44.4msYou are 8ms
to your first hop

pass
Jitter/loss with small packets tested from Central - USA:
Jitter/loss with small packets tested from West Coast - USA:
 

1 minute MTR (hop loss analysis) from Central - USA
HopHostLOSSRcvSentBestAvgWorst
0ae-1.bb-c.slr.lxa.us.oneandone.net0%60600.321.7110.45
1ae-10.bb-c.ms.mkc.us.oneandone.net0%60600.780.881.08
264.209.105.2330%606013.9659.44949.29
30.xe-8-2-0.BR3.CHI13.ALTER.NET0%606014.1417.84102.95
40.ae3.CHI01-BB-RTR1.verizon-gni.NET0%606014.4821.07111.17
5P12-0.WASHDC-LCR-03.verizon-gni.net0%606043.1243.2543.38
6P4-0.WASHDC-CHCHMDBE-ERXG07.verizon-gni.net0%606044.6445.2456.28
7(TARGET IP ADDRESS)37%386058.3459.3961.11

fail

1 minute MTR (hop loss analysis) from West Coast - USA
HopHostLOSSRcvSentBestAvgWorst
0h-67-100-37-242.noclli.covad.net0%60602.426.14183.93
1ge-6-14.car2.SanJose1.Level3.net0%60602.5226.36383.09
2ae-1-60.edge1.SanJose3.Level3.net0%60603.105.0748.55
3MCI-level3-20G.SanJose3.Level3.net0%60603.055.1254.88
40.ge-2-0-0.SJC01-BB-RTR2.verizon-gni.net0%60605.1711.94102.57
5P12-0.WASHDC-LCR-04.verizon-gni.net0%606089.0989.2289.47
6P0-0.WASHDC-CHCHMDBE-ERXG07.verizon-gni.net0%606092.3792.5493.53
7(TARGET IP ADDRESS)44%3460103.91104.51105.44

fail