×

Switch Account

Intermittent Internet Connection-Replaced Router But Still Same Issues

Intermittent Internet Connection-Replaced Router But Still Same Issues

Reply
Highlighted
Copper Contributor venigall
Copper Contributor
Posts: 8
Registered: ‎07-11-2011
Message 1 of 12
(5,259 Views)

Hi Everbody,

 

My FIOS internet is very intermittent and i frequently get the "connection timed out" messages. The problems exist for both wired and wireless computers.

 

 I already had a technician visit my house and say everything was fine.

 Waited for a week and called a second time since the issues were repeating and then the customer service representative sent a new router and the problem still exists using the new router.

 

I am in an apartment and my internet connection is through the telephone jack --> ZYXEL modem --> ACTIONTEC wireless router (MI424WR-GEN2, Revision E).

 

I wanted to get some suggestion before calling verizon again. Thanks everybody for your time.

 

 

 

Here is a copy of the tracert to google.

 

Tracing route to www.l.google.com [74.125.93.104]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2    21 ms    20 ms    20 ms  L100.WASHDC-VFTTP-86.verizon-gni.net [173.66.91.1]
  3    22 ms    22 ms    21 ms  G0-9-3-1.WASHDC-LCR-21.verizon-gni.net [130.81.109.154]
  4    23 ms    23 ms    50 ms  so-13-1-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.22.54]
  5    24 ms    24 ms    86 ms  0.so-6-0-3.XL3.IAD8.ALTER.NET [152.63.32.133]
  6    25 ms    25 ms    25 ms  TenGigE0-4-0-0.GW7.IAD8.ALTER.NET [152.63.37.150]
  7     *       54 ms    52 ms  google-gw.customer.alter.net [152.179.50.62]
  8    25 ms     *       25 ms  216.239.46.250
  9    31 ms    31 ms    31 ms  209.85.248.75
 10   133 ms    31 ms    31 ms  209.85.254.237
 11    36 ms     *        *     216.239.46.78
 12     *      115 ms     *     qw-in-f104.1e100.net [74.125.93.104]
 13    31 ms     *        *     qw-in-f104.1e100.net [74.125.93.104]
 14    31 ms    33 ms    31 ms  qw-in-f104.1e100.net [74.125.93.104]

Trace complete.

 

Also are the ping data to google.com

 

Pinging google.com [74.125.93.147] with 32 bytes of data:
Request timed out.
Reply from 74.125.93.147: bytes=32 time=32ms TTL=252
Reply from 74.125.93.147: bytes=32 time=31ms TTL=252
Reply from 74.125.93.147: bytes=32 time=31ms TTL=252
Reply from 74.125.93.147: bytes=32 time=31ms TTL=252
Request timed out.
Request timed out.
Reply from 74.125.93.147: bytes=32 time=31ms TTL=252
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.93.147: bytes=32 time=53ms TTL=252
Reply from 74.125.93.147: bytes=32 time=32ms TTL=252
Reply from 74.125.93.147: bytes=32 time=31ms TTL=252
Reply from 74.125.93.147: bytes=32 time=31ms TTL=252
Reply from 74.125.93.147: bytes=32 time=32ms TTL=252
Reply from 74.125.93.147: bytes=32 time=31ms TTL=252
Request timed out.
Reply from 74.125.93.147: bytes=32 time=31ms TTL=252
Request timed out.

Ping statistics for 74.125.93.147:
    Packets: Sent = 20, Received = 12, Lost = 8 (40% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 53ms, Average = 33ms

 

 

Ping data to Verizon.net

 

Pinging verizon.net [206.46.232.39] with 32 bytes of data:
Reply from 206.46.232.39: bytes=32 time=61ms TTL=246
Reply from 206.46.232.39: bytes=32 time=62ms TTL=246
Reply from 206.46.232.39: bytes=32 time=62ms TTL=246
Reply from 206.46.232.39: bytes=32 time=61ms TTL=246
Reply from 206.46.232.39: bytes=32 time=61ms TTL=246
Reply from 206.46.232.39: bytes=32 time=62ms TTL=246
Reply from 206.46.232.39: bytes=32 time=62ms TTL=246
Reply from 206.46.232.39: bytes=32 time=62ms TTL=246
Reply from 206.46.232.39: bytes=32 time=61ms TTL=246
Reply from 206.46.232.39: bytes=32 time=61ms TTL=246
Reply from 206.46.232.39: bytes=32 time=62ms TTL=246
Reply from 206.46.232.39: bytes=32 time=61ms TTL=246
Reply from 206.46.232.39: bytes=32 time=62ms TTL=246
Reply from 206.46.232.39: bytes=32 time=62ms TTL=246
Reply from 206.46.232.39: bytes=32 time=67ms TTL=246
Reply from 206.46.232.39: bytes=32 time=69ms TTL=246
Reply from 206.46.232.39: bytes=32 time=71ms TTL=246
Reply from 206.46.232.39: bytes=32 time=62ms TTL=246
Reply from 206.46.232.39: bytes=32 time=62ms TTL=246
Reply from 206.46.232.39: bytes=32 time=62ms TTL=246

Ping statistics for 206.46.232.39:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 61ms, Maximum = 71ms, Average = 62ms

 

 

11 REPLIES 11
Highlighted
Silver Contributor III
Silver Contributor III
Posts: 398
Registered: ‎10-09-2008
Message 2 of 12
(5,247 Views)

You  posted in the forum for Verizon FiOS, but you have DSL.   Perhaps DSL is a better forum?   Have them run a test on your DSL line.

 

cjacobs001
Highlighted
Silver Contributor III
Silver Contributor III
Posts: 398
Registered: ‎10-09-2008
Message 3 of 12
(5,244 Views)

DSL is not FiOS.

cjacobs001
Highlighted
Bronze Contributor I
Bronze Contributor I
Posts: 62
Registered: ‎05-22-2011
Message 4 of 12
(5,238 Views)

Actually, not everybody knows about it, but many people in apartments or MDUs (multi-dwelling units) get their FIOS internet in the manner the original poster described, myself included and I have 20/5 FIOS internet. I had the same problem as the original poster. For me it occurred mainly when my landline was picked up or a number was dialed. A tech came out and put a filter on the side of the phone outlet that leads to the landline and this solved the problem for me. I think it is some form of DSL filter. From what I understand technically what comes over my phone line is something termed VDSL but because it reaches FIOS speeds Verizon classifies it as FIOS Internet.

Highlighted
Copper Contributor venigall
Copper Contributor
Posts: 8
Registered: ‎07-11-2011
Message 5 of 12
(5,216 Views)

Thanks for the clarification/response.

 

My internet is FIOS in an MDU.  It is correctly termed as VDSL

 

I spoke again to the customer service representative yesterday night and will call them again today based on your suggestions.  IT is so bad that i always keep getting timed out and have dropped calls on vonage.

 

I will ask verizon to send some one  to check the filter and if they resist i have to look for other ISPs

 

 

Highlighted
Copper Contributor venigall
Copper Contributor
Posts: 8
Registered: ‎07-11-2011
Message 6 of 12
(5,208 Views)

Just got in touch with the Verizon Customer Service who confirmed via a network technician some bad wiring that needs to be replaced. 

 

Also have a network technician coming over to check the local wiring.

 

Hope the problems get resolved soon.

 

 

 

 

Highlighted
Platinum Contributor III Platinum Contributor III
Platinum Contributor III
Posts: 7,391
Registered: ‎12-15-2010
Message 7 of 12
(5,187 Views)

This would require a tech roll to solve if nothing looks wrong on your end of things. Treat FiOS Internet over VDSL (MDU installs) the same as any other DSL line. It needs to be running over a clean pair of copper wiring, and it must have filters. VDSL isn't as tolerant to noise as typical ADSL is due to the higher speeds (also the same reason it's got a much shorter range!), so sometimes some special care is needed to find what is going on. None the less, let us know how the tech visit goes!

Highlighted
Copper Contributor venigall
Copper Contributor
Posts: 8
Registered: ‎07-11-2011
Message 8 of 12
(5,125 Views)

Two technician visits

 

A couple of hours on the phone with verizon customer care.

  

Result, my internet is as bad as it was.

 

Pinging to google.com still get a packet loss of around 52%.

-----------------------------------------------------------------------------------------------------------------------------------

Pinging google.com [74.125.91.103] with 32 bytes of data:
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Request timed out.
Request timed out.
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Reply from 74.125.91.103: bytes=32 time=32ms TTL=252
Request timed out.
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Request timed out.
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Request timed out.
Reply from 74.125.91.103: bytes=32 time=32ms TTL=252
Request timed out.
Reply from 74.125.91.103: bytes=32 time=32ms TTL=252
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Request timed out.
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Reply from 74.125.91.103: bytes=32 time=30ms TTL=252
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.91.103: bytes=32 time=32ms TTL=252
Request timed out.
Request timed out.
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Reply from 74.125.91.103: bytes=32 time=31ms TTL=252
Reply from 74.125.91.103: bytes=32 time=30ms TTL=252
Reply from 74.125.91.103: bytes=32 time=174ms TTL=252

Ping statistics for 74.125.91.103:
    Packets: Sent = 50, Received = 24, Lost = 26 (52% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 174ms, Average = 37ms

------------------------------------------------------------------------------------------------------------------------------

 

 Here are the logs from Router if any body can help decipher. The same messages keep repeating over again and again in the log. Are they something that effect the performance?

 

Jul 18 21:05:28 2011 System Log Message Too many forwarded messages
[repeated 40
times, last time on Jul 18 21:06:35 2011] Jul 18 20:55:10 2011

System Log Message Unable to change DSCP of icmp socket to
value 0 for ping Socket operation on non-socket Jul 18 20:55:10 2011

 

System Log Message Cannot find cache entry for mac
00:00:00:00:00:00 ret=-1 Jul 18 20:54:09 2011

 

System Log Message Too many forwarded messages
[repeated 19 times, last time on Jul 18 20:54:45 2011] Jul 18 20:23:32 2011

 

System Log Message Unable to change DSCP of icmp socket to
value 0 for ping Socket operation on non-socket
[repeated 2 times, last time on Jul 18 20:23:44 2011]

Copper Contributor venigall
Copper Contributor
Posts: 8
Registered: ‎07-11-2011
Message 9 of 12
(5,116 Views)

Results of path ping to google.com, Looks like the most packet loss is at alter.net

 

Tracing route to google.com [74.125.91.105]
over a maximum of 30 hops:
  0  Venkata-i7.home [192.168.1.5]
  1  192.168.1.1
  2  L100.WASHDC-VFTTP-86.verizon-gni.net [173.66.91.1]
  3  G3-0-0-886.WASHDC-LCR-08.verizon-gni.net [130.81.110.128]
  4  so-3-1-0-0.RES-BB-RTR2.verizon-gni.net [130.81.151.232]
  5  0.so-2-1-0.XL4.IAD8.ALTER.NET [152.63.32.161]
  6  TenGigE0-7-0-0.GW7.IAD8.ALTER.NET [152.63.32.198]
  7  google-gw.customer.alter.net [152.179.50.106]
  8     *     216.239.46.248
  9  209.85.248.73
 10  209.85.254.235
 11  209.85.240.57
 12  qy-in-f105.1e100.net [74.125.91.105]

Computing statistics for 300 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Venkata-i7.home [192.168.1.5]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2   20ms     0/ 100 =  0%     0/ 100 =  0%  L100.WASHDC-VFTTP-86.verizon-gni.net [173.66.91.1]
                                0/ 100 =  0%   |
  3   22ms     0/ 100 =  0%     0/ 100 =  0%  G3-0-0-886.WASHDC-LCR-08.verizon-gni.net [130.81.110.128]
                                0/ 100 =  0%   |
  4   26ms     0/ 100 =  0%     0/ 100 =  0%  so-3-1-0-0.RES-BB-RTR2.verizon-gni.net [130.81.151.232]
                                0/ 100 =  0%   |
  5   25ms     0/ 100 =  0%     0/ 100 =  0%  0.so-2-1-0.XL4.IAD8.ALTER.NET [152.63.32.161]
                                0/ 100 =  0%   |
  6   25ms     0/ 100 =  0%     0/ 100 =  0%  TenGigE0-7-0-0.GW7.IAD8.ALTER.NET[152.63.32.198]
                               22/ 100 = 22%   |
  7   60ms    22/ 100 = 22%     0/ 100 =  0%  google-gw.customer.alter.net [152.179.50.106]
                                6/ 100 =  6%   |
  8   32ms    30/ 100 = 30%     2/ 100 =  2%  216.239.46.248
                                0/ 100 =  0%   |
  9   33ms    31/ 100 = 31%     3/ 100 =  3%  209.85.248.73
                                0/ 100 =  0%   |
 10   31ms    34/ 100 = 34%     6/ 100 =  6%  209.85.254.235
                                0/ 100 =  0%   |
 11   35ms    35/ 100 = 35%     7/ 100 =  7%  209.85.240.57
                                0/ 100 =  0%   |
 12   31ms    28/ 100 = 28%     0/ 100 =  0%  qy-in-f105.1e100.net [74.125.91.105]

Trace complete.

Highlighted
Contributor VerizonUser78
Contributor
Posts: 7
Registered: ‎07-20-2011
Message 10 of 12
(5,091 Views)

This is occuring with me as well. I'm pretty sure the wiring from our condo box has gone bad. Wonder if Verizon will acnowldge this and post some type of response as to what's occuring. If it's happening to all these people on this forum??????

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.


Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.