Internet Connection Dropped - Netgear Router Settings
Is there a certain setting that needs to be enable/disabled for the Netgear Routers? I have run the setup feature using the Netgear Genie still losing the internet connection. Moved to the current house in November, used the same cox provided Netgear Router from previous address that worked great. Router at the home began to drop internet connection. Wireless devices are still connected to the router as well as hard wire computer, no internet connection. Have to reboot the router. Upgraded to a new Netgear Router. Same problem is still happening. I have to reset the router through the Netgear Genie. Cox support says the internet connection has not been lost must be the router. Make me sign up for the Networking support just to talk to a networking specialist and she offered nothing. Anyone have this same problem with the Netgear Routers?54KViews0likes24CommentsInternet Connection Drops Every Hour on The Hour for about 30 seconds
My computer uses a wired connection. This problem just started happening in the last week after doing some Windows Updates. I noticed my internet connection would drop every hour on the hour at :09. Such as 6:09, 7:09, 8:09. etc. It comes back on by itself after about 30 seconds. I did some research on Google and it said to do this: Method 2: Reset Transmission Control Protocol / Internet Protocol (TCP/IP) The reset command is available in the IP context of the NetShell utility. Follow these steps to use the reset command to reset TCP/IP manually: 1. To open a command prompt, click Start and then click Run. Copy and paste (or type) the following command in the Open box and then press ENTER: cmd 2. At the command prompt, copy and paste (or type) the following command and then press ENTER: netsh int ip reset c:\resetlog.txt Note If you do not want to specify a directory path for the log file, use the following command: netsh int ip reset resetlog.txt 3. Reboot the computer." http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/internet-disconnects-every-hour-for-a-second-then/92bb822d-112a-4c50-97e7-5f7be1152105?page=1 I followed that and it fixed the problem. However after doing another Windows Update the problem returned and I was losing the internet connection every hour at the :45 mark. I did the procedure again and it stopped losing connection at :45.However I fear it will return. I'm not looking forward to having to do this constantly every time I do a Windows Update, as you know there are almost daily Windows Updates. I logged in my Zoom Cable Modem/Router log and saw the below critical errors. What can you tell from this and what advice can you give to fix the problem?8.1KViews0likes0CommentsInternet Keeps dropping out
I have motorola surfboard sbg6580. It seem like my internet and wireless keep coming and going. I had a tech out here, but still does not seem like it has gotten any better. This is from my event log, but I do not know what this mean or if I can fix anything on my side of it. Wed Jul 24 21:05:50 2013 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Wed Jul 24 09:06:33 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Wed Jul 24 09:05:56 2013 Warning (5) Dynamic Range Window violation Wed Jul 24 09:05:52 2013 Notice (6) TLV-11 - unrecognized OID;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Wed Jul 24 09:05:51 2013 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Wed Jul 24 09:05:51 2013 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.0;CM-VER=3.0; Wed Jul 24 02:16:25 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Tue Jul 23 20:11:47 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Tue Jul 23 09:26:00 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Jul 22 16:39:49 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Jul 22 10:13:23 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Mon Jul 22 00:41:31 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Jul 20 17:11:32 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Jul 20 00:55:05 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Fri Jul 19 11:07:53 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Fri Jul 19 09:14:18 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Fri Jul 19 03:46:07 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Thu Jul 18 11:18:29 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Wed Jul 17 22:07:57 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out6.8KViews0likes4CommentsPacket Loss During Peak Times with Ultimate Tier
I've been experiencing excess packet loss during the evening for the past few weeks. This causes frequent disconnects in online games as well as excess lag. At around 7:00pm today: Tracing route to cox.net [68.99.123.161] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 10 ms 7 ms 8 ms 10.0.16.1 3 7 ms 8 ms 7 ms 68.1.8.229 4 8 ms 13 ms 9 ms 68.1.8.207 5 26 ms 8 ms 9 ms 68.1.8.86 6 16 ms 11 ms 11 ms dukedsrj02-ge210.0.rd.at.cox.net [68.1.1.123] 7 12 ms 30 ms 12 ms 68.1.15.238 8 * 11 ms 10 ms 68.99.123.4 9 12 ms 12 ms 11 ms ww2.cox.com [68.99.123.161] Trace complete. C:\Users\Matthew>ping cox.net -t Pinging cox.net [68.99.123.161] with 32 bytes of data: Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Request timed out. Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=10ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=16ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=13ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=10ms TTL=56 Reply from 68.99.123.161: bytes=32 time=13ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Request timed out. Reply from 68.99.123.161: bytes=32 time=10ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=13ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Request timed out. Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Ping statistics for 68.99.123.161: Packets: Sent = 34, Received = 31, Lost = 3 (8% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 16ms, Average = 11ms I also ran PingPlotter against the FFXIV ARR server that I play on as well as on cox.net. FFXIV ARR - http://imgur.com/nZyC6sV COX.net - http://imgur.com/ZJm4BmS I've also uploaded my signal page from my modem (SB6141). http://imgur.com/eLhW0zA5.9KViews0likes6CommentsWarcraft disconnect issues the minute I subscribed to COX in Henderson, NV
I have been a Cox customer for about 2 weeks (since moving to Henderson). Since then, World of Warcraft is unplayable for me. I cannot go 15 consecutive minutes without a disconnect or a lag spike of more than 5-15 seconds. Is anyone else having problems with WoW? It's not my computer--WoW still works perfectly fine with no issues when I drive back to Glendale, CA and use my brother's ISP, nor does it have disconnect or lag issues using my Mom's old DSL connection. It's only here in Henderson, using Cox. For example (and this is not an extreme case, but about the average experience for me): This evening, Tuesday August 13, from 9:00 pm-9:40 pm, I disconnected 4 times from WoW. I also had 4 bouts of lag/latency that had me running in place onscreen for more than 10 seconds each time. And it doesn't matter what time of day I try to play. Morning, mid-day, evenings, weekdays or weekends, it's all the same. I am a "Preferred" bundle customer, which is up to 25mbps download speeds. Should I pay extra and upgrade to 50 mbps? I wouldn't mind doing so, but the product I'm paying for now is so horrendous, I don't trust that paying extra would solve anything. Especially since my old DSL connection never had any problems like the ones I've experienced since the cable guy installed my internet and router and I plugged in two weeks ago. Everything else I do online, I can do from my smartphone--so if I can't play online, then there really is no reason to keep paying for Cox internet.Solved5.4KViews0likes5CommentsAnother multiple disconnect issue
This getting to be more than irritating as it's been going on for literally years and since the boost in speed has gotten worse. I keep getting disconnected. I'll let the current log speak as it is representative of a common disconnect. Now the apartment has had the cable coming in replaced and all of the equipment check and it's all good. This issue seems to be local to the build ing I am in. Modem i9s an SB6180 2014-02-08 12:26:52 3-Critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within ti 2014-02-08 12:26:49 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 12:26:47 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:26:43 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 12:26:41 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:26:27 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1 2014-02-08 12:26:27 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:26:11 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1 2014-02-08 12:26:10 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:26:05 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1 2014-02-08 12:26:05 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:25:39 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1 2014-02-08 12:25:22 5-Warning Dynamic Range Window violation 2014-02-08 12:25:13 6-Notice TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM 2014-02-08 12:25:13 5-Warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:7a:a4:fe:b1:2e; 2014-02-08 12:24:53 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:24:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 12:23:50 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:23:48 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 12:23:30 6-Notice Ds Lock Failed - Reinitialize MAC... 2014-02-08 12:23:30 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:23:26 6-Notice Ds Lock Failed - Reinitialize MAC... 2014-02-08 12:22:57 6-Notice TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM 1970-01-01 00:03:02 5-Warning ToD request sent - No Response received;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12: 1970-01-01 00:02:57 5-Warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:7a:a4:fe:b1:2e; 1970-01-01 00:02:39 3-Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC= 1970-01-01 00:02:26 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:02:07 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 1970-01-01 00:02:07 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:01:56 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 1970-01-01 00:01:54 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:01:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 1970-01-01 00:01:22 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:01:21 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 1970-01-01 00:01:20 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:00:14 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:44:25 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:44:22 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:43:58 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:43:56 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:43:38 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:43:34 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:43:32 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:42:36 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:42:36 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:42:21 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:42:21 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:42:19 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:42:17 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:42:13 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:42:11 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:42:11 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:41:44 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:41:40 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:41:38 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:41:34 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:41:07 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:40:59 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:40:34 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:40:16 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:39:29 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:38:49 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:38:47 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:38:38 3-Critical TFTP Request Retries exceeded, CM unable to register 2014-02-08 11:38:12 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:36:12 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:36:10 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:36:08 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:36:02 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:36:02 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:35:54 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:34:54 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:34:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:34:48 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:34:46 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:27:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:27:48 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:27:44 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:17:57 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:17:33 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:17:29 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:10:25 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:06:09 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:03:46 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:01:05 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 10:56:13 3-Critical TFTP Request Retries exceeded, CM unable to register 2014-02-08 10:55:49 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 10:52:13 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:43:32 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 10:36:57 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 10:35:49 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:35:45 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 10:35:39 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:35:37 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:20:24 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:09:41 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 10:09:37 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:09:31 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:09:26 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:09:14 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; ©2004 Motorola All rights reserved. And this is just for today. Will someone get this fixed please? or tell me what I need to do to fix it.I am tired of calling the tech support as most of them seem to be just script readers with no real knowledge of networking.3.2KViews0likes5Commentsinternet keeps losing connection
i have a SB5120 motorola modem, a few times a day i dont know if its related to my xbox running at the same time or what but randomly ill lose internet signal and when i look at my modem all the lights have restarted and the send light constantly blinks. ill unplug all wires on the modem and router and reset it. it usually comes back on but eventually it just goes out again. i got another SB5120 modem and switched it but it still has the same problem. any tips/tricks/advice?3.1KViews0likes1CommentNew Hardware, Same Disconnects
I really wish Verizon Fios was available in my area (downtown Norfolk, Virginia), because for over 5 years I've dealt with frequent disconnects from Cox, spanning two separate apartments and a fullgeneration of hardware upgrades and I'm still getting disconnects! I don't know what the issue is, but I'll tell you what it's not: anything on my end. I've had techs out multiple times checking the cable connection at the wall and they've all said the same thing, "it's fine." But never once was the line at the street checked, or any outdoor lines replaced. After recently upgrading both my modem (SB6121) and router (ASUS RT-N56U), I'm still disconnecting. I'm not even mad anymore; I've adapted. I've come to expect it. The disconnects have become ritual; the unplugging, waiting, and restarting. Yikes. Reading the forums, this seems like a massive problem for Cox and I'm just waiting for the day when Fios is available in my area, because I know Cox will never resolve this issue. I'm not even going to bother calling Cox (again), because they'll just offer to send out another tech to check the wall line. Oh, well. Guess I'm screwed until there's another cable provider in my area...2.5KViews0likes1Commenteither slow download speed 200k or intermitten connection
Starting from this weekend, I experienced either slow download speed 200-300 kbps. The modem has been reset multiple times either at my side orremotely through reps. Still slow speed.Sometimes I did get the normal download speed but within a couple of minutes, the downloadwas gone or below 1M. ping result got 100% lost, good time 10-20% or even 0%.I am suscribed to 25Mpbscombined with phone.Since I do not need phone except for security company, Iadded my Scientic Atlantic modemused to workwellwith Cox and dedicated it to internet only. I did get good download speed, at least >10M. But I got intermitten internet connection. Mostly I can not run back to back speed test (speedtest.net or speakeasy or even a single speed test. either stuck in download or upload test. My internet got disconnet within that period and then comes back. I am working at home, need stable connection. This really hurts. Will have rep come to check tomorrow morning. But any suggestion would be help. Just ran speed test and my download is 2.05Mbps and upload 14.22Mpbs. This is using SA modem. Internet got disconnected when running the second time.Back again. All these happen during the time I am writing this post.2.4KViews0likes1CommentLoss of connectivity
I recently purchased a Netgear CMD31T Cable modem and have noticed that I have to reset (by unplugging power) the modem almost daily. Really isn't a big deal but it kinda ** when you're streaming Netflix to your TV and you lose connection. I bought the modem because my old Surfboard Combo was starting to ** out on the "Wireless Side". As far as I know, the Motorola modem didn't have this issue. Ever hear of this issue with Netgear modems? Or maybe I just go a " bad" one.2.4KViews0likes2Comments