Choose your cart
Choose your cart
Receive up to $504 promo credit ($180 w/Welcome Unlimited, $360 w/ 5G Start, or $504 w/5G Do More, 5G Play More, 5G Get More or One Unlimited for iPhone plan (Welcome Unlimited and One Unlimited for iPhone plans can't be mixed w/other Unlimited plans; all lines on the account req'd on respective plans)) when you add a new smartphone line with your own 4G/5G smartphone on an eligible postpaid plan between 2/10/23 and 4/5/23. Promo credit applied over 36 months; promo credits end if eligibility requirements are no longer met.
$699.99 (128 GB only) device payment purchase or full retail purchase w/ new smartphone line on One Unlimited for iPhone (all lines on account req'd on plan), 5G Start, 5G Do More, 5G Play More or 5G Get More plan req'd. Less $699.99 promo credit applied over 36 mos.; promo credit ends if eligibility req’s are no longer met; 0% APR.
Just recently updated to the "new" dsl & phone package for $58 after being stuck with verizon's old slow DSL system for the last 5 years. The old verizon DSL service was insanely slow but it constantly worked. My DSL is now constantly crashing everyday. Today alone i've dropped connection roughly 15 times now. The crashing just started "11/20/14" and we did the update the previous day.
I do have a feeling i know what is the main problem but i'm worried that its' going to cost quite a bit of money to have it replaced. Our NID - Network Interface in the house and the main junction outside the house is about 30 years old. The rest of the wiring going between phones and the NID are the same age. Nothing has been updated. We are still using the filters from our first 2008-09 DSL hookup. Those may need to be changed.
Heres a series of images of my setup / situation. I posted the direct link and embed them onto the thread.
-----------------------------------------
The NID inside the house
https://www.dropbox.com/s/aa0gro1qzl2ypi7/2014-11-26%2018.09.40.jpg?dl=0
https://www.dropbox.com/s/95y18jbd1l294q8/2014-11-26%2018.40.27.jpg?dl=0
https://www.dropbox.com/s/5qudsb2495wdxvc/2014-11-26%2018.40.41.jpg?dl=0
-----------------------------------------
The box outside the house.
https://www.dropbox.com/s/npr1deqn7rjmpdn/2014-11-26%2018.41.46.jpg?dl=0
https://www.dropbox.com/s/jo6sr1lz80q0pdj/2014-11-26%2018.41.54.jpg?dl=0
https://www.dropbox.com/s/pm87p0hgswntdzp/2014-11-26%2018.41.59.jpg?dl=0
-----------------------------------------
Netgear n600 router
https://www.dropbox.com/s/72vmqm2nnt30w8e/2014-11-26%2018.55.49.jpg?dl=0
https://www.dropbox.com/s/lbnu3c1dg5w1dke/2014-11-26%2018.56.04.jpg?dl=0
Our original Verizon Westell 7500 router shorted out during a storm last year and I replaced it with the current Netgear n600 router. The belkin range extender was hooked up around june of this year. For some reason the range extender doesn't renew its' lease the wireless sometimes stops working but I can deal with that issue. My main concern is the main internet connection.
LAN Issues:
All lan phones do experience static, popping / clicking, and echoing. The phone closest to the NID experiences the worst of the feedback. The phone in my bedroom has mild feedback and is the furthest away.
DSL Dropping symptoms:
Our download speed drops from 10mbps to around 90kbps and finally gets the 404 / can't find site error. Not sure about upload. I rarely even use upload speed.
Old Service info:
Verizon DSL 2.5mbps / .75mbps
Netgear n600 dual band router
Southern Berkshire County
New Service:
Verizon DSL 10mbps / 1.2mbps
Netgear n600 dual band router
Belkin Range Extender
Southern Berkshire County
Summary
So what do you think is wrong with my connection? I do understand a bot will most likely post on here about pushing my issue forward.
It's possible the speed increase has made your line operate outside of tolerance. Does your modem display the DSL statistics such as Attenuation, SN Margin, speed, etc?
Since you also indicate phone line noise, we will want o try to get that squared away. The best way to go about troubleshooting these issues is to take a wired phone and plug it directly into the NID. If the noise stops, then that tells us there may be a problem inside. As an extra step, I like to take a phone splitter and a dsl filter, and connect both the modem and a filtered wired phone directly to the NID. If the noise returns, this is usually the sign of a wiring problem such as a crossed line on Verizon's end, or a bad microfilter.
The best thing to try doing first, is to have Verizon install a home run in your home. This is, in short a whole home filter setup that filters out every jack in your home, and provides your DSL modem with a dedicated clean connection back to the NID. Verizon will usually install these for free if you report service troubles like this.
Hi. Luckily my router does show the statistics. Ill give that phone test a try right now and report back. Others are on the internet and need to wait till tomorrow. Ill also give verizon a call on monday and setup an appointment to have that dedicated line installed. Thanks for replying.
Thanks. Just as I suspected, your noise margin is lousy. The attenuation is a bit high for 10Mbps servicd, although that could be just a side effect of the noise on the landline. Please let us know of how the efforts for getting the noise of the line goes. Also, let us know what those transceiver statistics look like after repairs.
If the noise margin is still lousy after repair, you do have the option of dropping the speed down to 7.1Mbps, which will add stability and also let you have Fast path. fast path will allow you to have reduced latency or "ping" in applications like Games, at the cost of some error checking.
Sorry about the late reply. I did the test this morning on just the phone and on both phone and router. Both tests returned static and popping.
Awesome, so you'll need to call Verizon Voice Repair to have them come out and repair your line. Once repaired, the DSL should stabalize.
Just leaving another update. I finally was able to call verizon today and had them do a line test & router test. The line test came back fine but the modem test showed that my Netgear router isn't showing an IP. Not sure how its' not showing one. I can easily get it on speed test, tracert, etc. Verizon is sending me a new router to try out. Hopefully the new router fixes it.
I've some bad news. I got the "new" router (ActionTec GT784WNV) and hooked it up. Worked absolutely fine until 5:30pm this time and then my internet started shutting off. So far in the past hour its' shut off about 8 times. The router had one quick cluster where it restarted about 4-5 times in under 2 minutes. Usually it always shut off after 7pm.
Luckly this router alows me to log more things now. I was able to catch a couple stack traces / exception errors that prove its' coming from verizon's end. It appears the connection is straight up being dropped. I believe I can write out that my LAN Junction and NID is shot. My new feeling is that the DSLAM (Digital subscriber line access multiplexer) im hooked to is faulty.
Ill call verizon again tomorrow and continue to provide more updates on here till its' either fixed or i change services.
In the logs below you can see that i flushed the DNS, released the ip, and renewed it on multiple devices.
DATE TIME SYSTEM ACTION 12/11/2014 07:00:46 PM kernel [<8006148c>] 0x8006148c 12/11/2014 07:00:46 PM kernel [<801cba88>] 0x801cba88 12/11/2014 07:00:46 PM kernel [] 0xc0081ed4 12/11/2014 07:00:46 PM kernel [] 0xc0081dcc 12/11/2014 07:00:46 PM kernel [] 0xc0082a10 12/11/2014 07:00:46 PM kernel c0082e68>] 0xc0082e68 12/11/2014 07:00:46 PM kernel [] 0xc0084478 12/11/2014 07:00:46 PM kernel [] 0xc0081f94 12/11/2014 07:00:46 PM kernel [] 0xc007f668 12/11/2014 07:00:46 PM kernel [] 0xc0080000 12/11/2014 07:00:46 PM kernel [] 0xc00f4d60 12/11/2014 07:00:46 PM kernel [] 0xc00fa6a4 12/11/2014 07:00:46 PM kernel [] 0xc007e1d0 12/11/2014 07:00:46 PM kernel [] 0xc00ece20 12/11/2014 07:00:46 PM kernel [] 0xc00f4d60 12/11/2014 07:00:46 PM kernel [] 0xc01043f0 12/11/2014 07:00:46 PM kernel [] 0xc0110000 12/11/2014 07:00:46 PM kernel [] 0xc00eede4 12/11/2014 07:00:46 PM kernel [] 0xc00f09fc 12/11/2014 07:00:46 PM kernel [] 0xc01043f0 12/11/2014 07:00:46 PM kernel [] 0xc00ed808 12/11/2014 07:00:46 PM kernel [] 0xc00f09fc 12/11/2014 07:00:46 PM kernel [] 0xc01043f0 12/11/2014 07:00:46 PM kernel [] 0xc00f3e68 12/11/2014 07:00:46 PM kernel [] 0xc0110000 12/11/2014 07:00:46 PM kernel [] 0xc0110000 12/11/2014 07:00:46 PM kernel [] 0xc00f09fc 12/11/2014 07:00:46 PM kernel [] 0xc01043f0 12/11/2014 07:00:46 PM kernel [] 0xc00f12d4 12/11/2014 07:00:46 PM kernel [] 0xc00f09fc 12/11/2014 07:00:46 PM kernel [] 0xc01043f0 12/11/2014 07:00:46 PM kernel [<80022ccc>] 0x80022ccc 12/11/2014 07:00:46 PM kernel [] 0xc0101c28 12/11/2014 07:00:46 PM kernel [] 0xc00ef5dc 12/11/2014 07:00:46 PM kernel [] 0xc01013b4 12/11/2014 07:00:46 PM kernel [] 0xc0109a78 12/11/2014 07:00:46 PM kernel [] 0xc0101c28 12/11/2014 07:00:46 PM kernel [] 0xc00f0a44 12/11/2014 07:00:46 PM kernel [] 0xc00f09fc 12/11/2014 07:00:46 PM kernel [] 0xc00f28ac 12/11/2014 07:00:46 PM kernel [] 0xc00f4d60 12/11/2014 07:00:46 PM kernel [<80010424>] 0x80010424 12/11/2014 07:00:46 PM kernel [<80033fa4>] 0x80033fa4 12/11/2014 07:00:46 PM kernel [] 0xc0100000 12/11/2014 07:00:46 PM kernel [] 0xc00ee66c 12/11/2014 07:00:46 PM kernel [] 0xc00f26cc 12/11/2014 07:00:46 PM kernel [] 0xc00ee66c 12/11/2014 07:00:46 PM kernel [] 0xc00f26cc 12/11/2014 07:00:46 PM kernel [] 0xc00f4d60 12/11/2014 07:00:46 PM kernel [] 0xc00f6a54 12/11/2014 07:00:46 PM kernel [<800323ec>] 0x800323ec 12/11/2014 07:00:46 PM kernel [<80034124>] 0x80034124 12/11/2014 07:00:46 PM kernel [<80017424>] 0x80017424 12/11/2014 07:00:46 PM kernel [<8003d920>] 0x8003d920 12/11/2014 07:00:46 PM kernel [<80017784>] 0x80017784 12/11/2014 07:00:46 PM kernel [<8003de34>] 0x8003de34 12/11/2014 07:00:46 PM kernel [<8003dc9c>] 0x8003dc9c 12/11/2014 07:00:46 PM kernel [<8003dc9c>] 0x8003dc9c 12/11/2014 07:00:46 PM kernel [<8003dc9c>] 0x8003dc9c 12/11/2014 07:00:46 PM kernel [<800504a8>] 0x800504a8 12/11/2014 07:00:46 PM kernel [<8001b25c>] 0x8001b25c 12/11/2014 07:00:46 PM kernel 12/11/2014 07:00:46 PM kernel XTM Init: 400 tx BDs at 0xa31f6000 12/11/2014 07:00:46 PM kernel bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=1011000, DS=12278000 12/11/2014 07:06:27 PM syslog RENEW IP 192.168.1.9 12/11/2014 07:06:45 PM syslog RENEW IP 192.168.1.8 12/11/2014 07:07:00 PM syslog RENEW IP 192.168.1.11 12/11/2014 07:07:03 PM syslog RENEW IP 192.168.1.11 12/11/2014 07:07:07 PM syslog RENEW IP 192.168.1.11 12/11/2014 07:07:15 PM syslog RENEW IP 192.168.1.11 12/11/2014 07:07:24 PM kernel eth1 Link UP 100 mbps full duplex 12/11/2014 07:07:24 PM kernel br0: topology change detected, propagating 12/11/2014 07:07:24 PM kernel br0: port 2(eth1) entering forwarding state 12/11/2014 07:07:36 PM syslog RENEW IP 192.168.1.12 12/11/2014 07:08:40 PM syslog RELEASE IP ,ÐZèÙ3 12/11/2014 07:10:15 PM syslog RENEW IP 192.168.1.11 12/11/2014 07:17:45 PM kernel device br0 entered promiscuous mode 12/11/2014 07:17:52 PM kernel device br0 left promiscuous mode 12/11/2014 07:19:04 PM kernel device br0 entered promiscuous mode 12/11/2014 07:19:11 PM kernel device br0 left promiscuous mode 12/11/2014 07:19:12 PM syslog RENEW IP 192.168.1.9 12/11/2014 07:19:23 PM kernel device br0 entered promiscuous mode 12/11/2014 07:19:30 PM kernel device br0 left promiscuous mode 12/11/2014 07:25:44 PM kernel Line 0: ADSL link down 12/11/2014 07:25:44 PM kernel bcmxtmcfg: XTM Link Information, port = 0, State = DOWN, Service Support = ATM 12/11/2014 07:25:44 PM kernel HOST XTM Tx ch 0 down success 12/11/2014 07:25:44 PM kernel bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0 12/11/2014 07:25:46 PM kernel Line 0: xDSL G.994 training 12/11/2014 07:25:56 PM kernel Line 0: ADSL G.992 started 12/11/2014 07:26:01 PM kernel Line 0: ADSL G.992 channel analysis 12/11/2014 07:26:05 PM kernel Line 0: ADSL G.992 message exchange 12/11/2014 07:26:05 PM kernel Line 0: ADSL link up, Bearer 0, us=1004, ds=12259 12/11/2014 07:26:05 PM kernel bcmxtmcfg: XTM Link Information, port = 0, State = UP, Service Support = ATM 12/11/2014 07:26:05 PM kernel XTM Init: 400 tx BDs at 0xa31f6000 12/11/2014 07:26:05 PM kernel bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=1004000, DS=12259000 12/11/2014 07:32:51 PM kernel Line 0: ADSL link down 12/11/2014 07:32:51 PM kernel bcmxtmcfg: XTM Link Information, port = 0, State = DOWN, Service Support = ATM 12/11/2014 07:32:51 PM kernel HOST XTM Tx ch 0 down success 12/11/2014 07:32:51 PM kernel bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0 12/11/2014 07:32:53 PM kernel Line 0: xDSL G.994 training 12/11/2014 07:33:04 PM kernel Line 0: ADSL G.992 started 12/11/2014 07:33:08 PM kernel Line 0: ADSL G.992 channel analysis 12/11/2014 07:33:13 PM kernel Line 0: ADSL G.992 message exchange 12/11/2014 07:33:13 PM kernel Line 0: ADSL link up, Bearer 0, us=997, ds=12161 12/11/2014 07:33:13 PM kernel bcmxtmcfg: XTM Link Information, port = 0, State = UP, Service Support = ATM 12/11/2014 07:33:13 PM kernel XTM Init: 400 tx BDs at 0xa31f6000 12/11/2014 07:33:13 PM kernel bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=997000, DS=12161000
Just crashed twice again. Heres a nice helping of stack trace and i can serve seconds if need to.
12/11/2014 07:43:20 PM -- MARK -- 12/11/2014 07:50:49 PM kernel Line 0: ADSL link down 12/11/2014 07:50:49 PM kernel bcmxtmcfg: XTM Link Information, port = 0, State = DOWN, Service Support = ATM 12/11/2014 07:50:49 PM kernel HOST XTM Tx ch 0 down success 12/11/2014 07:50:49 PM kernel bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0 12/11/2014 07:50:51 PM kernel Line 0: xDSL G.994 training 12/11/2014 07:51:01 PM kernel Line 0: ADSL G.992 started 12/11/2014 07:51:06 PM kernel Line 0: ADSL G.992 channel analysis 12/11/2014 07:51:10 PM kernel Line 0: ADSL G.992 message exchange 12/11/2014 07:51:10 PM kernel Line 0: ADSL link up, Bearer 0, us=993, ds=12086 12/11/2014 07:51:10 PM kernel bcmxtmcfg: XTM Link Information, port = 0, State = UP, Service Support = ATM 12/11/2014 07:51:10 PM kernel XTM Init: 400 tx BDs at 0xa31f6000 12/11/2014 07:51:10 PM kernel bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=993000, DS=12086000 12/11/2014 07:52:49 PM kernel Line 0: ADSL link down 12/11/2014 07:52:49 PM kernel bcmxtmcfg: XTM Link Information, port = 0, State = DOWN, Service Support = ATM 12/11/2014 07:52:49 PM kernel HOST XTM Tx ch 0 down success 12/11/2014 07:52:49 PM kernel bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0 12/11/2014 07:52:51 PM kernel Line 0: xDSL G.994 training 12/11/2014 07:53:01 PM kernel Line 0: ADSL G.992 started 12/11/2014 07:53:06 PM kernel Line 0: ADSL G.992 channel analysis 12/11/2014 07:53:10 PM kernel Line 0: ADSL G.992 message exchange 12/11/2014 07:53:11 PM kernel Line 0: ADSL link up, Bearer 0, us=1004, ds=12154 12/11/2014 07:53:11 PM kernel bcmxtmcfg: XTM Link Information, port = 0, State = UP, Service Support = ATM 12/11/2014 07:53:11 PM kernel XTM Init: 400 tx BDs at 0xa31f6000 12/11/2014 07:53:11 PM kernel bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=1004000, DS=12154000
I would like to apologize for the amount of updates that i've done and will be doing. Here is my first update for the day.
Its' currently 10:38am EST and i've been up since 7am. The internet has not dropped once today and surprisingly its' slightly faster than usual too. I'm getting an extra 0.1mbps. I know, nothing too considerable but its' noteable. I've been the only one on the internet too.
Traffic Summary:
Lots of downloading for the past 3.5 hours. So far i've done 7GB of downloading. 5.8GB of that was from steam client games & 1.2GB of that is from downloading Unity3D 4.6.1.
This proves that high traffic, what websites i visit, and the games I play are NOT the cause of my drops.
I need to conduct more personal tests with other computers. I have a slight feeling another PC in the house may be causing the drops but I have no fool proof way of testing it. I've had viruses in the past drop my connection so this might be it.
_________________________________________________
Average Speed:
The speed stays absolutely solid at either 1.2MB/s or 1.3MB/s with this replacement router. The previous router (Netgear n600 DualBand) was very unstable and would range from 16kbps to the full 1.2MB/s.
Firefox downloads: 1.3MB/s
Steam Client Downloads: 1.2MB/s
_________________________________________________
Router Logs:
For some reason my connection dropped at 6am but has been fine ever since. Ok, so my connection is fine from 6am to 5pm but then is faulty from 5pm to 6am. There shouldn't be that much more traffic at night to cause the drop.
12/12/2014 05:23:16 AM kernel XTM Init: 400 tx BDs at 0xa31f6000 12/12/2014 05:23:16 AM kernel bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=979000, DS=12267000 12/12/2014 05:43:20 AM -- MARK -- 12/12/2014 05:58:34 AM kernel Line 0: ADSL link down 12/12/2014 05:58:34 AM kernel bcmxtmcfg: XTM Link Information, port = 0, State = DOWN, Service Support = ATM 12/12/2014 05:58:34 AM kernel HOST XTM Tx ch 0 down success 12/12/2014 05:58:34 AM kernel bcmxtmcfg: Connection DOWN, LinkActiveStatus=0x0 12/12/2014 05:58:36 AM kernel Line 0: xDSL G.994 training 12/12/2014 05:58:46 AM kernel Line 0: ADSL G.992 started 12/12/2014 05:58:51 AM kernel Line 0: ADSL G.992 channel analysis 12/12/2014 05:58:55 AM kernel Line 0: ADSL G.992 message exchange 12/12/2014 05:58:56 AM kernel Line 0: ADSL link up, Bearer 0, us=1007, ds=12259 12/12/2014 05:58:56 AM kernel bcmxtmcfg: XTM Link Information, port = 0, State = UP, Service Support = ATM 12/12/2014 05:58:56 AM kernel XTM Init: 400 tx BDs at 0xa31f6000 12/12/2014 05:58:56 AM kernel bcmxtmcfg: Connection UP, LinkActiveStatus=0x1, US=1007000, DS=12259000 12/12/2014 06:03:10 AM syslog RENEW IP 192.168.1.8 12/12/2014 06:15:12 AM syslog RENEW IP 192.168.1.9 12/12/2014 06:43:20 AM -- MARK -- 12/12/2014 06:59:13 AM kernel eth0 Link DOWN. 12/12/2014 06:59:13 AM kernel br0: port 1(eth0) entering disabled state 12/12/2014 06:59:16 AM kernel eth0 Link UP 100 mbps full duplex 12/12/2014 06:59:16 AM kernel br0: topology change detected, propagating 12/12/2014 06:59:16 AM kernel br0: port 1(eth0) entering forwarding state 12/12/2014 06:59:18 AM syslog RENEW IP 192.168.1.2 12/12/2014 06:59:21 AM syslog RENEW IP 192.168.1.2 12/12/2014 07:09:05 AM syslog RENEW IP 192.168.1.9 12/12/2014 07:16:39 AM syslog RENEW IP 192.168.1.9 12/12/2014 07:17:59 AM syslog RENEW IP 192.168.1.9 12/12/2014 07:40:48 AM syslog RENEW IP 192.168.1.9 12/12/2014 07:43:19 AM -- MARK -- 12/12/2014 08:43:20 AM -- MARK -- 12/12/2014 09:25:34 AM syslog RENEW IP 192.168.1.6 12/12/2014 09:43:20 AM -- MARK --
As usual, ill report back with more findings.