- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I see many posts on this issue as far back as 2011, but no fixes other than a replacement router which doesn't appear to fix the problem. I'm hoping you will see something below which can help me. The only connection to the Verizon router is an Asus RT-AC66U which recently replaced a DLINK DIR-655. My PC is cable connectec to the Asus and other devices (2 iMacs, 2 ROKUs, a laptop, iPhones, a printer, iPad) connect wirelessly. My sevice is 50/25. TV service and ROKU streaming seem unaffected. When things are at their worst, it takes many seconds to reach the Verizon router admin interface and once there, clicking "Go to Internet Now" results in "Cannot Connect" message.
I'm here after running FIOS optimizer, NDT, tracert, speed test, etc.. Lots of output but I want to start showing just a bit of it. The first two items were pulled 22 hours after a power recycle. The last entry in the log (third item) is a from a few minutes after power cycle to 22 hours later. True enough, the power cycle got me back in business, but as is shown, the symptoms come back immediately. Surely I don't have to do power cycles several times daily.
On preview, I get the message about a 20,000 character length limit, but no hint as to whether I've exceeded it. Aha, trying to post, I see that I have exceeded it, but it's left to me to figure out by how much. I'll just keep making the third item shorter, cutting out the most recent entries - but trust me on this, it's verrrry repetitious.
Thank you for any assistance/advice.
Router Status |
Firmware Version: |
|
||
Model Name: |
A90-9100EM15-10 |
||
Hardware Version: |
A |
||
Serial Number: |
08AK07034648 |
||
INI File Name: |
096-900205-02 |
||
INI File Version: |
A |
||
Physical Connection Type: |
Multimedia over Coax (MOCA) |
||
Broadband Connection Type: |
DHCP |
||
Broadband Connection Status: |
Connected |
||
Broadband IP Address: |
{edited for privacy} |
||
Subnet Mask: |
255.255.255.0 |
||
Broadband MAC Address: |
00:18:3a:a3:e3:15 |
||
Default Gateway: |
{edited for privacy} |
||
DNS Server(s): |
68.238.96.12 |
||
Active Status(Router Has Been Active For): |
22 hrs 23 mins 46 secs |
Full Status/System wide Monitoring of Connections |
Name |
WAN PPPoE |
||||||
Status |
Connected |
1 Ports Connected |
Disabled |
Connected |
Connected |
Disabled |
Disabled |
Network |
Network (Home/Office) |
Network (Home/Office) |
WAN |
Network (Home/Office) |
WAN |
Network (Home/Office) |
|
Underlying Device |
|||||||
Connection Type |
Bridge |
Hardware Ethernet Switch |
Ethernet |
Multimedia over Coax (MOCA) |
Multimedia over Coax (MOCA) |
802.11b/g Mixed |
PPPoE |
MAC Address |
00:18:3a:a3:e3:14 |
00:18:3a:a3:e3:14 |
00:18:3a:a3:e3:15 |
00:18:3a:a3:e3:15 |
00:00:00:00:00:00 |
||
IP Address |
192.168.1.1 |
{edited for privacy} |
{edited for privacy} |
||||
Subnet Mask |
255.255.255.0 |
255.255.255.0 |
255.255.255.0 |
||||
Default Gateway |
{edited for privacy} |
{edited for privacy} |
|||||
DNS Server |
68.238.96.12 |
68.238.96.12 |
|||||
DHCP Server |
Disabled |
Disabled |
Disabled |
||||
Received Packets |
1736132 |
1741626 |
0 |
56401 |
3846528 |
||
Sent Packets |
3833861 |
3946752 |
0 |
126178 |
1596427 |
||
Time Span |
22:25:01 |
22:24:41 |
22:24:31 |
||||
Channel |
15(1150 MHz) |
9(1000 MHz) |
Time |
Event |
Event-Type |
Details |
Sep 11 13:35:52 2013 |
System Log |
Message |
daemon.err estream: socket 45: timed out 15000 ms on data |
Sep 11 13:35:52 2013 |
System Log |
Message |
daemon.err estream: socket 43: timed out 15000 ms on data |
Sep 11 13:35:52 2013 |
System Log |
Message |
daemon.err estream: socket 37: timed out 15000 ms on data |
Sep 11 13:35:52 2013 |
System Log |
Message |
daemon.err estream: socket 35: timed out 15000 ms on data |
Sep 11 13:35:52 2013 |
System Log |
Message |
daemon.err estream: socket 34: timed out 15000 ms on data |
Sep 11 13:35:22 2013 |
System Log |
Message |
daemon.err estream: socket 31: timed out 15000 ms on data |
Sep 11 13:35:22 2013 |
System Log |
Message |
daemon.err estream: socket 34: timed out 15000 ms on data |
Sep 11 13:35:07 2013 |
System Log |
Message |
daemon.err estream: socket 37: timed out 15000 ms on data |
Sep 11 13:35:07 2013 |
System Log |
Message |
daemon.err estream: socket 34: timed out 15000 ms on data |
Sep 11 13:35:07 2013 |
System Log |
Message |
daemon.err estream: socket 31: timed out 15000 ms on data |
Sep 11 13:35:07 2013 |
System Log |
Message |
daemon.err estream: socket 45: timed out 15000 ms on data |
Sep 11 13:35:07 2013 |
System Log |
Message |
daemon.err estream: socket 43: timed out 15000 ms on data |
Sep 11 13:31:18 2013 |
System Log |
Message |
daemon.warn DNS: unknown PTR name format |
Sep 11 13:21:06 2013 |
System Log |
Message |
kern.warn DIAGNOSTIC LOG: Traceroute test for dest: ,Status= , 0 |
Sep 11 12:51:21 2013 |
System Log |
Message |
daemon.warn DNS: unknown PTR name format |
Sep 11 12:42:49 2013 |
System Log |
Message |
daemon.info Deleting Lease Entry |
Sep 11 12:18:23 2013 |
System Log |
Message |
daemon.warn DNS: unknown PTR name format |
Sep 11 12:16:51 2013 |
System Log |
Message |
daemon.info CWMP: IGMP data could not be retrieved due to socket status failure. |
Sep 11 12:14:33 2013 |
System Log |
Message |
daemon.warn DNS: unknown PTR name format |
Sep 11 12:14:32 2013 |
System Log |
Message |
daemon.info DHCP LAN Connection IP:192.168.1.22, DNS:192.168.1.1, GTW:192.168.1.1, Subnet:255.255.255.0 |
Sep 11 11:22:13 2013 |
System Log |
Message |
daemon.warn DNS: unknown PTR name format |
Sep 11 11:21:00 2013 |
System Log |
Message |
kern.warn DIAGNOSTIC LOG: Traceroute test for dest: ,Status= , 0 |
Sep 11 11:15:33 2013 |
System Log |
Message |
daemon.warn DNS: unknown PTR name format |
Sep 11 11:13:58 2013 |
System Log |
Message |
daemon.info DHCP LAN Connection IP:192.168.1.21, DNS:192.168.1.1, GTW:192.168.1.1, Subnet:255.255.255.0 |
Sep 11 11:06:30 2013 |
System Log |
Message |
daemon.warn DNS: unknown PTR name format |
Sep 11 11:05:59 2013 |
System Log |
Message |
kern.warn DIAGNOSTIC LOG: Traceroute test for dest: ,Status= , 0 |
Sep 11 10:58:34 2013 |
System Log |
Message |
daemon.warn DNS: unknown PTR name format |
Sep 11 10:55:59 2013 |
System Log |
Message |
kern.warn DIAGNOSTIC LOG: Traceroute test for dest: ,Status= , 0 |
Sep 11 10:53:01 2013 |
System Log |
Message |
daemon.warn DNS: unknown PTR name format |
Sep 11 10:50:54 2013 |
System Log |
Message |
daemon.err estream: socket 34: timed out 15000 ms on data |
Sep 11 10:47:40 2013 |
System Log |
Message |
kern.warn DIAGNOSTIC LOG: Traceroute test for dest: ,Status= , 0 |
Sep 11 10:42:21 2013 |
System Log |
Message |
daemon.warn DNS: unknown PTR name format |
Sep 11 10:39:24 2013 |
System Log |
Message |
daemon.err estream: socket 35: timed out 15000 ms on data |
Sep 11 10:38:21 2013 |
System Log |
Message |
daemon.err estream: socket 44: timed out 15000 ms on data |
Sep 11 10:38:21 2013 |
System Log |
Message |
daemon.err estream: socket 46: timed out 15000 ms on data |
Sep 11 10:38:21 2013 |
System Log |
Message |
daemon.err estream: socket 37: timed out 15000 ms on data |
Sep 11 10:37:46 2013 |
System Log |
Message |
daemon.err estream: socket 45: timed out 15000 ms on data |
Sep 11 10:32:11 2013 |
System Log |
Message |
daemon.warn DNS: unknown PTR name format |
Solved! Go to Correct Answer
Correct answers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't see another way to update this, so I will reply to it.
Thank you Elizabeth for the edit. I knew some IP addresses should be hidden, but I didn't know which ones.
I didn't know how long to wait for an answer, and even after router power-off cycle there were many many time-outs and other errors being written to the log, so I initiated a chat with Verizon Tech Support. Praveen was very helpful, was able to see pretty quickly the need to re-set the ONT (and maybe other things on the "Verizon side"), did so with only a couple of minutes interruption (TVs stayed on), and I'll assume I'm back in error-free business.
How can I close this?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't see another way to update this, so I will reply to it.
Thank you Elizabeth for the edit. I knew some IP addresses should be hidden, but I didn't know which ones.
I didn't know how long to wait for an answer, and even after router power-off cycle there were many many time-outs and other errors being written to the log, so I initiated a chat with Verizon Tech Support. Praveen was very helpful, was able to see pretty quickly the need to re-set the ONT (and maybe other things on the "Verizon side"), did so with only a couple of minutes interruption (TVs stayed on), and I'll assume I'm back in error-free business.
How can I close this?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After continuous wireless crashes they are replacing my router. I have a Blu Ray wired to the router one adroid phone and a laptop and a wired computer. My wireless signal is constantly crashing and none of the fixes seem to be working. Never had problems like this with comcast. I also have a Polycom IP phone hooked to the network. after long debates and only my IT guy figured out that "FIOS blocks any inbound traffic so I could never get inbound phone calls that has been resolved no thanks to FIOS tech support. Interested to see if this router swap is going to work
. Any bets?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To make the issue manageble and less frustrating for our household, I've been performing the following procedure every morning (sometimes twice a day) for the last couple of months.
I shut down my wireless router, then I un-plug the Verizon router. I turn on my PC (it's off at night) and let it do its startup stuff. I plug the Verizon router back in after it's been unplugged 10-20 minutes. Once its lights indicate it's ready, and when the PC is ready to go, I turn on the wireless router. After it powers up and some additional hand-shaking occurs between my PC and the Wireless router, things are "normal" again.
I'm the only one in the house who is ethernet attached, everybody else is wireless. Phones, laptops, desktops, Rokus, iPhones, etc. The only thing connected to the Verizon router is the wireless router. Wireless is not the issue - at least not in my home. The Verizon router just seems to clog up, time out, stop functioning, whatever you want to call it. I don't spend any more time looking at the router logs because nobody seems to know what the messages mean, but DNS errors are always there. If you look through these forums you will see the same story over and over. Poor function and loss of connectivity - ONT bounced/replaced, router bounced/replaced - problem remains. That's why I haven't asked that my router be replaced. My next step will be to bounce the router twice a day, I guess. Everyone depends on connectivity and we're not a happy household when that connnectivity is lost or lags badly. I may try to find a moca router made by another vendor. Right now I've made my peace with the workaround - one of the many foced on humanity by technology that almost works.
Good luck with the replacement router.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Why put up with all that when a call to VZ will get you a replacement router?
The Westells were a good router in their day, but are now obsolete and no longer issued by VZ.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've seen too many forum posts in which (1) a replacement router didn't help or (2) Verizon wanted the customeer to spend $100 or so for a replacement. I'm sure the new routers do a better job of wireless, but my problem isn't wireless. I may eventually ask for a replacement - right now the anticipated pain of engaging Verizon again is higher than the pain of the daily work around. I don't mean to badmouth the Verizon service folks - the issues just seem beyond their training and/or limits to what they are allowed to do. Thanks.