7 replies to this topic

[akira1313]

I've been hammering at this issue for almost five months now.  I am subscribed to the 3/768 package with Verizon Online DSL.  I get very good results from the up and down testmy.net tool..  The problem I am having is the supplied Westell 2200 modem is dropping its connection to the Internet, but only for a few of seconds, and then reconnects as if nothing happened.  This interruption in service will happen three or more times in any given hour, for a few hours, randomly but quite frequently every day.  Reseting the modem does not clear it up.  Reseting my Linksys router does not help.  I've called Verizon Tech support numours times about this but they have been all but useless with troubleshooting the issue.  I've begged and pleaded to get a service call to come out to my house and physically inspect the phone lines but all they do is run their line tests and say the "connection is good and a onsite visit is not necessary.".  I've tried to explain that their line tests will not catch this problem.  I've tried to connect directly to the Westell with my PC but I can't access the configuration page with my browser, and Verizon tech support refuses to divulge the information needed for accessing the modem.  During one call, the tech said the Field engineers suggested a downgrade in sevice to the 1/512 package which is unacceptable. ( I'll go back to Cox Commo before that!)  The thought behind that suggestion was that the modem can handle the data when it is coming in, but when it sends out it crashes, thus interrupting the flow of traffic.  This makes it sound like a hardware issue, right?  I tried updating the firmware for the modem, but again, Verizon refuses to divulge the needed encryption keys that the Update Tool asks for when it tries to write to the modem.  My apologies for the long-winded post, but I am detailed and meticulous desktop support technician during the day and documenting all facts and chain of events of an issue is a force of habit.  I will welcome any and all feedback from anyone if they think they can help.  This ia very informative site BTW.  I've learned many  new things the few days I've been pouring over the forum.

[xs1]

- Try setting your NIC card to 10mbs full duplex.

- Also in the router /modem settings , if theirs this option, use this

" Client Lease Time: [ 32040]  minutes (0 means one day) "

[edit after reading other's posts]

Try this first before getting confused... Sometimes a simple fix, sometimes not.

[/edit]

[DaveMan]

There might just be one problem, it might be your modem try replacing the modem if you are using the company's modem. Thats what I am thinking.

[av3ng3r85]

I think I know exactly what you're talking about. I've been having this problem for several months now even since I upgraded to the 3/768 package.Before this I actually had to have a Verizon tech come out the house and install a splitter in the NID because I was having connectivity issues.This signal would drop out whenever I picked up the phone even though all in-line splitters were installed properly.Anyway I have doing a lot of research trying to find out why the modem disconnects randomly.I checked the logs by first opening a browser and typing in "dslrouter" (no quotes).I have the Westell 327W.It's a black wireless modem/router.I'm not sure if that will work if you have another model.Look under the troubleshooting menu in the diagnostic log section.You may have to type in your router password.It will have a drop-down to select a log.Select all logs from the drop-down.Now here's what my log says:

---------------------------------BEGIN LOG TEXT------------------------------------------

MON APR 18 15:41:02 2005
    Setting System clock to Local time MON APR 18 15:41:02 2005


MON APR 18 15:41:01 2005
    PPP CONNECTED on VPI 0 VCI 35

MON APR 18 15:41:01 2005
    Connecting session(0): Verizon Online due to AlwaysOn

MON APR 18 15:37:07 2005
    PPP CONNECTION ERROR on VPI 0 VCI 35 : Could not establish Link

MON APR 18 15:37:07 2005
    Received PADT before PPP stack complete

MON APR 18 15:37:07 2005
    Received PADT for session id 40307

MON APR 18 15:36:27 2005
    Connecting session(0): Verizon Online due to AlwaysOn

MON APR 18 15:31:52 2005
    PPP CONNECTION ERROR on VPI 0 VCI 35 : Could not establish Link

MON APR 18 15:31:51 2005
    PPP DISCONNECTED on VPI 0 VCI 35 : PPP link layer failure

MON APR 18 11:01:06 2005
    Setting System clock to Local time MON APR 18 11:01:06 2005

MON APR 18 11:01:05 2005
    PPP CONNECTED on VPI 0 VCI 35

MON APR 18 11:01:05 2005
    Connecting session(0): Verizon Online due to AlwaysOn

MON APR 18 10:55:31 2005
    PPP CONNECTION ERROR on VPI 0 VCI 35 : Could not establish Link

MON APR 18 10:55:30 2005
    PPP CONNECTION ERROR on VPI 0 VCI 35 : Could not establish Link

MON APR 18 10:55:30 2005
    Disconnecting session(0): Verizon Online due to PADT received

MON APR 18 10:55:30 2005
    Received PADT for session id 15119

--------------------------------END OF LOG TEXT---------------------------------------

This is a fairly recent entry because they happen so frequently I was able to gather a fresh one.In the 18:06:50 that my connection was "UP" I've had 53 disconnects.Most I didn't even know about because it will reconnect automatically but occasionaly I'll be at my computer and the internet will go down for no reason and I look over and the internet light on the modem is red.It doesn't lose sync though just the internet is inaccesible.Anyway from analyzing the logs I've found out that  "PADT" is PPPoE active discovery termination packet.It has to be sent from Verizon's servers I'm assuming.Once the modem receives that packet it shuts down the connection with the internet called a "session".Keep in mind I'm reading from the end of the log entry to the top because that's the cron order.So, the modem detects an error that it can't establish a link.Because my settings are "always on" it tries to reconnect.It tries and finally succeeds 5 minutes later.Later on that same day it has a PPP link failure out of the blue.Before it even has a chance to re-open the session it receives a PADT packet.Protocol says it must terminate the session whenever a packet like that is received.So it shuts down the session with an error complaining that it "received a PADT before PPP was complete".It again notices it can't connect to the internet, tries to log back on and finally connects.Link failed at 15:31 and reconnected at 15:41.So 10 minutes have passed while I wait for my modem to sort out the issue.In conclusion, something is causing PADT packets to be sent instantly killing my connectionI'm still not sure why this happens but I posted this becasue maybe it can help you figure out what's going on.Sorry for the long post but I'm a tech too and we have to keep logs of what we do.It's just a habit.Everybody have a good day.

[DaveMan]

Have u tried replacing your modem at all? And how old is your modem?

[akira1313]

Verizon did send me a new modem and I just received it today.  I hooked it up and will begin monitoring.  I am crossing my fingers and hoping this is the fix.

[elraymundo]

Hi akira1313,

I've been having identical issues with my Verizon DSL here in Northern VA - same log file entires and everything. I know it's been quite a while since you wrote this post, but I wanted ot ask anyway - did replacing the DSL modem ultimately fix the issue? Did you ever get consistent and reliable DSL service from Verizon?

[akira1313]

Yes, this was an old issue I was dealing with almost 2 years ago back when I was living in another county and Verizon was my ISP.  I had to be persistent with Verizon's tech support team to get them to realize the DC issues were not being caused by their modem (they did send me a replacement modem but the disconnects were still occuring) or any of my equipment.  I had to cover all the network troubleshooting procedures I could possibly do on my end, but I was finally able to convince the support technician that the problem was definitely originating on their end.  After a couple more weeks (and playing a few rounds of phone tag), a Verizon Support technician reported back to me that they were able to trace it to a wiring issue or a hardware issue involving their equipment so they replaced both components.  Whatever repairs the technician had to do at the substation, it seemed to have resolved my DC issues almost immediately, and I never had an issue since. 

I would advise you to continue to work with their tech support till they are able to resolve your issue.  It can get a little frustrating and repetitive having to explain your issue to a different support tech each time you call to report the same issue, but eventually the number of calls from you should spark them to fully investigate what is causing your disconnects.  Good luck!