Intermittent loss of connection
Joey3155
Newbie

For about a week now I have been suffering from a intermittent loss of connection to the internet the internet will be fine until it randomly decides to drop out. Usually I'll be surfing the website and go to navigate to another webpage when it times out and tells me it couldn't find the website in question. My games seems to be affected as well though it is more common for me to observe this in my browser the problem occurs in Firefox and I loaded Chrome as well one day and the problem appears there as well. I need some line quality tests with dslreports.com's line quality test and I did four of them they all reported intermittent packet loss the odd thing I noticed is in all four tests I did the same node suffered a varying amount of packet loss (ae-1-60.edge1.SanJose3.Level3.net) I have been trying to get some info on this server but I can't seem to find any info on it whatsoever I have included all four tests in the zip archive attached to this post.

I also did a fifth test which I included as well I did this test after resetting the router and did another test but it was much of the same. Please tell me how to troubleshoot this problem I am losing my mind and patience.

Line Quality Test 1

Line Quality Test 2

Line Quality Test 3

Line Quality Test 4

Line Quality Test 5

0 Likes
Re: Intermittent loss of connection
smith6612
Community Leader
Community Leader

The line quality test is designed to try to narrow down where a problem may be when you're dealing with issues such as packet loss and congestion. If what you're seeing is an intermittent connectivity issue where the connection itself drops out then most likely the line quality test will not detect that.

The Level3 hop is a router owned by Level3 Communications. Even though the router is dropping packets, they can be programmed to have ICMP traffic dropped or set to a low priority that causes the latency measurement to be measured higher, or even not respond to pings all together. This is normal for many routers when they are under larger loads, as such is the case with Backbone routers. What matters is how the trace looks going forward. As you are not losing traffic beyond that Level3 router and latency looks fine at least into the Verizon network, it is not the problem.

I do see your fast ping graphs are showing some variances in latency. When running the line quality tests, is anything or anyone using any sort of data on your Internet connection? The line quality tests can be skewed too by extra traffic on the connection. When running it make sure nothing is using the connection. If this is the case where the line IS idle when runnin those tests, then we have something to consider.

When your connection drops out, what are the modem lights doing? Is the DSL light flashing or is the Internet light Red or Out, or is the Internet light flashing with the DSL light solid?

0 Likes
Re: Intermittent loss of connection
Joey3155
Newbie

The only thing I can imagine would be my Vonage phone, the browser itself, my firewall, and Mumble/Yahoo Messenger. But since none of those consume alot of bandwidth I didn't think they would affect the test.

When the drops occur the modem lights usually stay solid green, all of them. Only one time did I look over and see the internet light turn orange and then back to green.

What can potentially cause a intermittent drop in the first case. It's like a partial drop the phone, if in use, may drop the call, the browser fails to load new pages the only thing that doesn't seem affected at least not that I've seen are my games like Mass Effect 3 and Planetside 2.

0 Likes
Re: Intermittent loss of connection
thefranchise237

I'm having a similar issue.  But the kicker is that it's not just websites timing out, it's everything -- even the router interfaces slow themselves down to a crawl.  It's random, and it's persisted through two MI424 routers of different revisions, plus an old Netgear I put in as well, and across a plethora of different IPs (forced release/renewals to make sure the router wasn't being attacked).  The MI424s had relatively clean firewall logs as well, so I can't even blame it on a DDoS.

I'm beyond clueless here.  Even on a wired connection, the behavior persists.  And the routers don't indicate any sort of connection loss or trouble condition. 

0 Likes
Re: Intermittent loss of connection
TSPerkins
Enthusiast - Level 2

I've been having this same problem for about 3 weeks now. Router light turns solid green and I get no data. Everything times out and nothing moves. I normally lose my VPN connection to work and it seems like it is getting worse. I'm very unhappy with this because I just paid more for a 75/35 line due to work data transfer requirements. I'm paying for twice the speed I had and I'm now getting 1/10 the speed. Something just does not compute.

Also, in the last 3 weeks I have to turn off my router, go to the garage, unplug the AC and Battery cords, wait 2 to 5 minutes then plug everything back in at least once a day. Most of the time my router light turns orange and my connection is completely off. I work from home and absolutely cannot tolerate this level of service. I'm very busy in the day and don't have time to wait 30 minutes on the phone to get help. I'm no dummy when it comes to computers so if anyone has suggestions please let me know.

I checked my speed at sites not related to Verizon and I show 8.5 mbps down, 5.4 Mbps up, and a 41% quality of service. 2 seconds later I can run tests at SpeedTest.net and I get what my line should be on download 75 Mbps and I get 23 Mbps on upload. I think the big speed test sites are in cahoots with the big ISPs.

Anyway, I guess I'm stuck in a 2 year contract but if something doesn't change soon I'll just cancel my service and try to file a claim for a refund of the termination fee. I've been with Verizon about 7 years and I'm very sad right now. I used to love FIOS but lately it's been horrible.

I'm in Tampa in case that matters.

0 Likes
Re: Intermittent loss of connection
igorman64
Enthusiast - Level 2

I've been having a simliar issue as well for about a month now where my internet drops out every now and then for several seconds and then comes back up. This only started happening after Hurricane Sandy in Staten Island, NY when my ONT had to be replaced after being flooded. Since then, I have already had my ONT replaced twice and was given a new REV I router and told to not send back my old REV D router which never had any problems before. I have even tried putting back the REV D router and I still kept losing internet every now and then. After multiple chats with Verizon, they seem to have pinpointed the problem to be a physical issue in my house. So, I tried connecting the REV I router directly to the ONT, via coax, and I still noticed the internet dropping. Looking at the router logs, I noticed the following entries every now and then (usually multiple times a day):

Jan 10 00:29:15 2013System LogWAN ETHWAN Ethernet Link Up
Jan 10 00:29:14 2013System LogWAN CoaxWAN Coax Link Up
Jan 10 00:29:10 2013System LogWAN ETHWAN Ethernet Link Down
Jan 10 00:29:10 2013System LogWAN CoaxWAN Coax Link Down

and

Jan 8 04:35:26 2013System LogWAN CoaxWAN Coax Link Up
Jan 8 04:35:26 2013System LogWAN ETHWAN Ethernet Link Up
Jan 8 04:33:42 2013System LogWAN ETHWAN Ethernet Link Down
Jan 8 04:33:41 2013System LogWAN CoaxWAN Coax Link Down

Looking at the advanced logs I ocassionally find the following entries associated with the link flapping:

2013/01/08 04:33:44.12 M mt_igmp_params_init:223: reconf: new lan interface: br0, ver 3
2013/01/08 04:33:44.12 M mt_igmp_params_init:235: reconf: new wan interface: eth1
2013/01/08 04:33:44.20 M clink1: link down, device will be down
2013/01/08 04:33:44.24 M lan if uninit br0
2013/01/08 04:33:44.24 M removing multicast group 224.0.0.1 from device br0 port 16
2013/01/08 04:33:44.24 M removing multicast group 224.0.0.1 from device br0 port 8
2013/01/08 04:33:44.24 M removing multicast group 224.0.0.1 from device br0 port 4
2013/01/08 04:33:44.24 M removing multicast group 224.0.0.1 from device br0 port 2
2013/01/08 04:33:44.24 M removing multicast group 224.0.0.1 from device br0 port 1
2013/01/08 04:33:44.24 M removing multicast group 224.0.0.1 from device br0 port 0
2013/01/08 04:33:44.24 M uninit igmp proxy module
2013/01/08 04:33:44.24 M init igmp proxy module
2013/01/08 04:33:44.24 M lan if init br0
2013/01/08 04:33:44.24 M adding multicast group 224.0.0.1 to device br0 port 0
2013/01/08 04:33:44.24 M adding multicast group 224.0.0.1 to device br0 port 1
2013/01/08 04:33:44.24 M adding multicast group 224.0.0.1 to device br0 port 2
2013/01/08 04:33:44.24 M adding multicast group 224.0.0.1 to device br0 port 4
2013/01/08 04:33:44.24 M adding multicast group 224.0.0.1 to device br0 port 8
2013/01/08 04:33:44.24 M adding multicast group 224.0.0.1 to device br0 port 16
2013/01/08 04:33:44.31 M jan  8 04:33:43 syslog: check_exit: exiting
2013/01/08 04:33:45.10 M igmprx_lan_port_add_single: ifname=br0  ifindex=9
2013/01/08 04:33:45.10 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:33:45.10 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:33:45.10 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:33:45.10 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:33:45.10 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:33:45.10 M @@ setting new value completed, it should show new value in proc/proxy
2013/01/08 04:33:45.12 M mt_igmp_params_init:223: reconf: new lan interface: br0, ver 3
2013/01/08 04:33:45.20 M eth1: link down, device will be down
2013/01/08 04:33:45.26 M lan if uninit br0
2013/01/08 04:33:45.28 M removing multicast group 224.0.0.1 from device br0 port 16
2013/01/08 04:33:45.28 M removing multicast group 224.0.0.1 from device br0 port 8
2013/01/08 04:33:45.28 M removing multicast group 224.0.0.1 from device br0 port 4
2013/01/08 04:33:45.28 M removing multicast group 224.0.0.1 from device br0 port 2
2013/01/08 04:33:45.28 M removing multicast group 224.0.0.1 from device br0 port 1
2013/01/08 04:33:45.28 M removing multicast group 224.0.0.1 from device br0 port 0
2013/01/08 04:33:45.28 M uninit igmp proxy module
2013/01/08 04:33:45.28 M init igmp proxy module
2013/01/08 04:33:45.28 M lan if init br0
2013/01/08 04:33:45.28 M adding multicast group 224.0.0.1 to device br0 port 0
2013/01/08 04:33:45.28 M adding multicast group 224.0.0.1 to device br0 port 1
2013/01/08 04:33:45.28 M adding multicast group 224.0.0.1 to device br0 port 2
2013/01/08 04:33:45.28 M adding multicast group 224.0.0.1 to device br0 port 4
2013/01/08 04:33:45.28 M adding multicast group 224.0.0.1 to device br0 port 8
2013/01/08 04:33:45.28 M adding multicast group 224.0.0.1 to device br0 port 16
2013/01/08 04:33:46.10 M igmprx_lan_port_add_single: ifname=br0  ifindex=9
2013/01/08 04:33:46.10 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:33:46.10 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:33:46.10 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:33:46.10 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:33:46.10 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:33:46.10 M eth1: stopped
2013/01/08 04:33:46.10 M eth1: mac address changed
2013/01/08 04:33:46.10 M port 0: setting mac to 0x1, status: 0x2c3d
2013/01/08 04:33:46.10 M eth1: link up
2013/01/08 04:33:46.10 M eth1: started
2013/01/08 04:35:27.24 M eth1: link up, device will be up
2013/01/08 04:35:27.54 M clink1: lof 1000mhz
2013/01/08 04:35:27.55 M mt_igmp_params_init:223: reconf: new lan interface: br0, ver 3
2013/01/08 04:35:27.63 M clink1: link up, device will be up
2013/01/08 04:35:27.63 M lan if uninit br0
2013/01/08 04:35:27.63 M removing multicast group 224.0.0.1 from device br0 port 16
2013/01/08 04:35:27.63 M removing multicast group 224.0.0.1 from device br0 port 8
2013/01/08 04:35:27.63 M removing multicast group 224.0.0.1 from device br0 port 4
2013/01/08 04:35:27.63 M removing multicast group 224.0.0.1 from device br0 port 2
2013/01/08 04:35:27.63 M removing multicast group 224.0.0.1 from device br0 port 1
2013/01/08 04:35:27.63 M removing multicast group 224.0.0.1 from device br0 port 0
2013/01/08 04:35:27.63 M uninit igmp proxy module
2013/01/08 04:35:27.63 M init igmp proxy module
2013/01/08 04:35:27.63 M lan if init br0
2013/01/08 04:35:27.63 M adding multicast group 224.0.0.1 to device br0 port 0
2013/01/08 04:35:27.63 M adding multicast group 224.0.0.1 to device br0 port 1
2013/01/08 04:35:27.63 M adding multicast group 224.0.0.1 to device br0 port 2
2013/01/08 04:35:27.63 M adding multicast group 224.0.0.1 to device br0 port 4
2013/01/08 04:35:27.63 M adding multicast group 224.0.0.1 to device br0 port 8
2013/01/08 04:35:27.63 M adding multicast group 224.0.0.1 to device br0 port 16
2013/01/08 04:35:28.10 M igmprx_lan_port_add_single: ifname=br0  ifindex=9
2013/01/08 04:35:28.10 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:35:28.12 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:35:28.12 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:35:28.12 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:35:28.12 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:35:36.79 M mt_igmp_params_init:223: reconf: new lan interface: br0, ver 3
2013/01/08 04:35:36.79 M mt_igmp_params_init:235: reconf: new wan interface: eth1
2013/01/08 04:35:36.85 M dhcp client: wan ethernet renew ip address: 173.56.37.223
2013/01/08 04:35:36.85 M dhcp client: wan ethernet renew netmask: 255.255.255.0
2013/01/08 04:35:36.85 M dhcp client: wan ethernet renew gateway: 173.56.37.1
2013/01/08 04:35:36.85 M dhcp client: wan ethernet renew dns server: 208.67.222.222 208.67.220.220
2013/01/08 04:35:36.90 M lan if uninit br0
2013/01/08 04:35:36.90 M removing multicast group 224.0.0.1 from device br0 port 16
2013/01/08 04:35:36.90 M removing multicast group 224.0.0.1 from device br0 port 8
2013/01/08 04:35:36.90 M removing multicast group 224.0.0.1 from device br0 port 4
2013/01/08 04:35:36.90 M removing multicast group 224.0.0.1 from device br0 port 2
2013/01/08 04:35:36.90 M removing multicast group 224.0.0.1 from device br0 port 1
2013/01/08 04:35:36.90 M removing multicast group 224.0.0.1 from device br0 port 0
2013/01/08 04:35:36.90 M uninit igmp proxy module
2013/01/08 04:35:36.90 M init igmp proxy module
2013/01/08 04:35:36.90 M lan if init br0
2013/01/08 04:35:36.90 M adding multicast group 224.0.0.1 to device br0 port 0
2013/01/08 04:35:36.90 M adding multicast group 224.0.0.1 to device br0 port 1
2013/01/08 04:35:36.90 M adding multicast group 224.0.0.1 to device br0 port 2
2013/01/08 04:35:36.91 M adding multicast group 224.0.0.1 to device br0 port 4
2013/01/08 04:35:36.91 M adding multicast group 224.0.0.1 to device br0 port 8
2013/01/08 04:35:36.91 M adding multicast group 224.0.0.1 to device br0 port 16
2013/01/08 04:35:36.91 M out: [62] nat error: no free nat ip ([62] nat error: no free nat ip: )
2013/01/08 04:35:37.19 M igmprx_lan_port_add_single: ifname=br0  ifindex=9
2013/01/08 04:35:37.19 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:35:37.19 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:35:37.19 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:35:37.19 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:35:37.19 M igmprx_lan_port_add_single: ifname=eth0  ifindex=2
2013/01/08 04:35:37.19 M @@ setting new value completed, it should show new value in proc/proxy
2013/01/08 04:35:47.83 M acs ack: event = 4 value change

I setup syslog on the router which feeds it to the WallWatcher application and this is all the details I get duing the flap. I'm really stumped by this and can't figure out what the problem is. Could it be a bad PON card? I noticed that the logs show only the WAN Coax going down without the LAN Coax which leads me to believe in a faulty connection between the router and the ONT. I've already tried connecting both routers directly to the ONT to no avail. The only changes that I can think of since Sandy are the electrical outlets that were replaced. Could they be causing some kind of interference? I've tried running the coax with and without the ground block, but that didn't help either. The only thing that was not replaced since the first post-Sandy installation is the ONT battery system, only the battery itself was replaced once. Could that be it? Just to be clear, I have always been connected via coax and I have tried testing with different cables.

0 Likes
Re: Intermittent loss of connection
vovka77
Enthusiast - Level 2

I am having the same issue in Staten Island, NY, for about a month I loose network connectivity in the morning. I have been contacting FIOS but they are not being helpful and point the finger at me and my devices. I know that my pc/laptop is fine and its a FIOS problem. I even had the Actiontec router replaced to no avail.

One thing I noticed, that its a DNS issue. I can't ping major websites like CNN, Yahoo, etc. requests time out.

0 Likes
Re: Intermittent loss of connection
igorman64
Enthusiast - Level 2

I just tried pinging CNN and i get the same time out, but I can access the website fine. Google and Yahoo, however do not timeout, so not sure what is going on there. When you ping, does the web address resolve to an IP? Usually a DNS issue results in a destination not reachable error instead of a timeout which usually occurs when the destination does not accept pings or is offline or there is no route to it. Try looking at the router logs when this happens to see if you might be having the WAN connection drop like me. Here are the instructions:

1) Go to 192.168.1.1, by default, in your web browser.

2) Login with User: admin and Passwrod: password or password1. The password might also be located on a sticker on the Actiontec depending on its revision.

3) Click on the System Monitoring icon on the top right.

4) Click on Advanced Status on the left side menu, and click Yes to proceed.

5) Click System Logging.

6) Now you should be able to see the logs and you can switch between Basic View and Advanced View via a button on the bottom of the page.

Post some sections of the log where you see anything going down or anything that doesn't look right. By the way, how do you resolve the network connectivity issue? Does it come back with time or do you have to restart the router or even reset the ONT?

0 Likes
Re: Intermittent loss of connection
vovka77
Enthusiast - Level 2

To answer your last question, the connectivity issue is resolves on its own. I was on the phone with VZ tech support and the tech was first stating that it was my issue with my devices, but than he noticed packet loss between the unit outside the house and the router. A tech is coming tomorrow, and I am going to at least request they provide me with the latest Wireless N router that VZ has. I am still noticing intermittent issues. I have a laptop and desktop both connected to the Actiontec router via WIFI and my desktop has DNS lookup issues at times. I tried to do NSLOOOKUP on sites like yahoo.com, cnn.com, ny1.com and on occasion the lookups fail. This generally happens when I see latency while browsing the web. The tech said it could be a faulty wire that is causing this problem.

Take a look at my cmd prompt DNS results that I kept doing this morning, take a look at DNS timeouts. I will also post the logs from the router:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights res
 
C:\Users\user>nslookup cnn.com
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1
 
Non-authoritative answer:
Name:    cnn.com
Addresses:  157.166.255.18
          157.166.255.19
          157.166.226.25
          157.166.226.26
 
 
C:\Users\user>nslookup ny1.com
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1
 
Non-authoritative answer:
Name:    ny1.com
Address:  24.93.38.31
 
 
C:\Users\user>nslookup cnn.com
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1
 
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to Wireless_Broadband_Router.home timed-out
 
C:\Users\user>nslookup cnn.com
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1
 
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to Wireless_Broadband_Router.home timed-out
 
C:\Users\user>nslookup cnn.com
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1
 
Non-authoritative answer:
Name:    cnn.com
Addresses:  157.166.255.19
          157.166.226.25
          157.166.226.26
          157.166.255.18
 
 
C:\Users\user>nslookup ny1.com
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1
 
Non-authoritative answer:
Name:    ny1.com
Address:  24.93.38.31
 
 
C:\Users\user>nslookup cnn.com
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1
 
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to Wireless_Broadband_Router.home timed-out
 
C:\Users\user>nslookup google.com
Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1
 
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to Wireless_Broadband_Router.home timed-out
 
Jan 10 11:30:18 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.5, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
[repeated 3 times, last time on Jan 10 11:44:24 2013]
Jan 10 11:29:41 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.12, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
Jan 10 11:01:31 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.9, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
[repeated 2 times, last time on Jan 10 11:25:49 2013]
Jan 10 10:58:25 2013System LogWAN DHCPDHCP WAN connection IP:173.56.114.135,DNS:68.237.161.12 71.243.0.12 ,GTW:173.56.114.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 10 10:50:20 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.11, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Ethernet)
Jan 10 10:37:52 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.9, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
[repeated 4 times, last time on Jan 10 10:50:04 2013]
Jan 10 10:29:48 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.6, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
Jan 10 10:23:34 2013System LogCWMPConnection Request Inform 204 No Content
Jan 10 10:23:31 2013System LogCWMPConnection Request Inform challege response with 200 OK from server
Jan 10 10:23:17 2013System LogCWMPConnection Request Inform initial 401 chanllenge
[repeated 2 times, last time on Jan 10 10:23:28 2013]
Jan 10 10:18:29 2013System LogCWMPConnection Request Inform 204 No Content
Jan 10 10:18:26 2013System LogCWMPConnection Request Inform challege response with 200 OK from server
Jan 10 10:16:40 2013System LogCWMPConnection Request Inform initial 401 chanllenge
[repeated 7 times, last time on Jan 10 10:18:25 2013]
Jan 10 09:58:59 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.10, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
Jan 10 09:58:54 2013System LogCWMPConnection Request Inform 204 No Content
Jan 10 09:58:51 2013System LogCWMPConnection Request Inform challege response with 200 OK from server
Jan 10 09:58:50 2013System LogCWMPConnection Request Inform initial 401 chanllenge
Jan 10 09:58:25 2013System LogWAN DHCPDHCP WAN connection IP:173.56.114.135,DNS:68.237.161.12 71.243.0.12 ,GTW:173.56.114.1,Subnet:255.255.255.0 (WAN Ethernet)
Jan 10 09:56:41 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.6, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
Jan 10 09:51:46 2013System LogCWMPConnection Request Inform initial 401 chanllenge
[repeated 7 times, last time on Jan 10 09:54:12 2013]
Jan 10 09:38:13 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.9, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
Jan 10 09:38:11 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.6, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
Jan 10 09:34:39 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.5, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
Jan 10 09:21:22 2013System LogLAN DHCPDHCP LAN Connection IP:192.168.1.6, DNS:192.168.1.1, GTW:192.168.1.1,Subnet:255.255.255.0 (Wireless)
0 Likes
Re: Intermittent loss of connection
vovka77
Enthusiast - Level 2

Igorman, so I noticed the following in the logs

Jan 10 10:23:34 2013System LogCWMP

Connection Request Inform 204 No Content

I looked this up and got another VZ post from another user having exact same connectivity issue, identical to what we are experiencing. Take a look:

http://businessforums.verizon.net/t5/FiOS-Internet/Internet-connections-randomly-goes-out/td-p/41086...

0 Likes