dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1417
share rss forum feed

Dmaineminent

join:2013-08-23
Saint Augustine, FL

1 edit

[Connectivity] Losing connection multiple times a day

I can't seem to catch a break here. I've only had Comcast for ~3 weeks. It cuts out, and I can't seem to reconnect without doing a power cycle of the modem and router.

Here are my signal logs on my modem as of now...please request more info if you need it.

Modem is a SB6121, router is a n300 netgear. I have Comcast 25/5

Downstream Bonding Channel Value
Channel ID 5 6 7 8
Frequency 651000000 Hz 657000000 Hz 663000000 Hz 669000000 Hz
Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
4 dBmV 5 dBmV 3 dBmV 3 dBmV
Upstream Bonding Channel Value
Channel ID 11 10
Frequency 27900000 Hz 34800000 Hz
Ranging Service ID 12989 12989
Symbol Rate 5.120 Msym/sec 5.120 Msym/sec
Power Level 42 dBmV 43 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[3] 64QAM

Ranging Status Success Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 5 6 7 8
Total Unerrored Codewords 1515375858 1514457526 1514457263 1514457793
Total Correctable Codewords 11 0 0 0
Total Uncorrectable Codewords 809 629 759 526

andyross
Premium,MVM
join:2003-05-04
Schaumburg, IL

Re: Losing connection multiple times a day

Can you post the logs, too?

Dmaineminent

join:2013-08-23
Saint Augustine, FL
said by andyross:

Can you post the logs, too?

Sure, but the error does not appear in any my logs, the errors you'll see here are from me power cycling the modem and router and from the area outage the other day. My router deletes all logs when I power cycle it, so it's all recent.

MODEM LOGS -

Aug 30 2013 00:47:41 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2013 23:17:18 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2013 22:51:23 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2013 22:49:04 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to IP loss ;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2013 22:48:04 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to IP loss ;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2013 22:40:59 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to IP loss ;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2013 22:39:57 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to IP loss ;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2013 22:08:46 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 29 2013 16:51:19 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 27 2013 02:36:08 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;

ROUTER LOGS -

[DHCP IP: 192.168.1.2] to MAC address 00:22:fa:f0:23:98, Friday, August 30, 2013 10:25:43
[DHCP IP: 192.168.1.6] to MAC address 00:0f:66:7a:46:30, Friday, August 30, 2013 10:25:42
[WLAN access rejected: incorrect security] from MAC address 00:0f:66:7a:46:30, Friday, August 30, 2013 10:25:38
[LAN access from remote] from 151.77.8.238:34475 to 192.168.1.4:17145, Friday, August 30, 2013 10:22:00
[LAN access from remote] from 124.95.156.3:20453 to 192.168.1.4:17145, Friday, August 30, 2013 10:17:13
[LAN access from remote] from 218.166.158.59:25944 to 192.168.1.4:17145, Friday, August 30, 2013 10:12:11
[LAN access from remote] from 123.88.84.230:9905 to 192.168.1.4:17145, Friday, August 30, 2013 10:04:54
[DoS Attack: ACK Scan] from source: 184.26.138.130, port 80, Friday, August 30, 2013 09:59:37
[UPnP set event: add_nat_rule] from source 192.168.1.6, Friday, August 30, 2013 09:56:40
[LAN access from remote] from 31.169.97.168:15035 to 192.168.1.4:17145, Friday, August 30, 2013 09:53:38
[LAN access from remote] from 124.95.156.3:20453 to 192.168.1.4:17145, Friday, August 30, 2013 09:47:30
[LAN access from remote] from 81.37.22.85:4665 to 192.168.1.4:17145, Friday, August 30, 2013 09:44:50
[LAN access from remote] from 219.134.13.130:17519 to 192.168.1.4:17145, Friday, August 30, 2013 09:43:26
[LAN access from remote] from 218.26.232.172:23401 to 192.168.1.4:17145, Friday, August 30, 2013 09:35:18
[LAN access from remote] from 79.40.75.215:4672 to 192.168.1.4:17145, Friday, August 30, 2013 09:29:20
[LAN access from remote] from 31.169.97.168:15035 to 192.168.1.4:17145, Friday, August 30, 2013 09:12:30
[LAN access from remote] from 221.232.135.51:59749 to 192.168.1.4:17145, Friday, August 30, 2013 09:10:43
[LAN access from remote] from 221.232.135.51:30214 to 192.168.1.4:17145, Friday, August 30, 2013 08:55:39
[LAN access from remote] from 31.169.97.168:15035 to 192.168.1.4:17145, Friday, August 30, 2013 08:46:19
[DoS Attack: TCP/UDP Chargen] from source: 94.102.51.229, port 55450, Friday, August 30, 2013 08:43:49
[DoS Attack: SYN/ACK Scan] from source: 182.140.245.250, port 80, Friday, August 30, 2013 08:42:44
[LAN access from remote] from 180.158.16.134:49848 to 192.168.1.4:17145, Friday, August 30, 2013 08:42:32
[LAN access from remote] from 221.232.135.51:61031 to 192.168.1.4:17145, Friday, August 30, 2013 08:34:04
[LAN access from remote] from 183.160.249.107:19494 to 192.168.1.4:17145, Friday, August 30, 2013 08:26:19
[LAN access from remote] from 118.186.141.64:22034 to 192.168.1.4:17145, Friday, August 30, 2013 08:19:08
[LAN access from remote] from 84.127.206.93:4672 to 192.168.1.4:17145, Friday, August 30, 2013 08:17:42
[LAN access from remote] from 183.240.202.235:2661 to 192.168.1.4:17145, Friday, August 30, 2013 08:14:56
[LAN access from remote] from 62.99.27.236:4672 to 192.168.1.4:17145, Friday, August 30, 2013 08:12:27
[LAN access from remote] from 79.147.65.180:1985 to 192.168.1.4:17145, Friday, August 30, 2013 08:09:11
[LAN access from remote] from 218.64.36.85:25357 to 192.168.1.4:17145, Friday, August 30, 2013 08:06:59
[DoS Attack: SYN/ACK Scan] from source: 198.100.146.142, port 80, Friday, August 30, 2013 08:02:36
[LAN access from remote] from 83.50.83.233:71 to 192.168.1.4:17145, Friday, August 30, 2013 08:02:07
[LAN access from remote] from 119.84.114.8:16695 to 192.168.1.4:17145, Friday, August 30, 2013 07:57:02
[LAN access from remote] from 111.250.226.145:5628 to 192.168.1.4:17145, Friday, August 30, 2013 07:56:22
[LAN access from remote] from 114.80.189.188:18512 to 192.168.1.4:17145, Friday, August 30, 2013 07:52:52
[LAN access from remote] from 95.239.162.220:39252 to 192.168.1.4:17145, Friday, August 30, 2013 07:52:47
[LAN access from remote] from 94.65.97.22:13143 to 192.168.1.4:17145, Friday, August 30, 2013 07:52:22
[LAN access from remote] from 151.51.28.254:33308 to 192.168.1.4:17145, Friday, August 30, 2013 07:51:51
[LAN access from remote] from 85.50.89.252:59277 to 192.168.1.4:17145, Friday, August 30, 2013 07:50:13
[LAN access from remote] from 88.15.229.220:1024 to 192.168.1.4:17145, Friday, August 30, 2013 07:48:16
[LAN access from remote] from 46.120.250.99:4672 to 192.168.1.4:17145, Friday, August 30, 2013 07:46:41
[LAN access from remote] from 14.153.114.90:3307 to 192.168.1.4:17145, Friday, August 30, 2013 07:45:45
[LAN access from remote] from 125.110.110.177:5029 to 192.168.1.4:17145, Friday, August 30, 2013 07:42:56
[LAN access from remote] from 90.21.104.91:4673 to 192.168.1.4:17145, Friday, August 30, 2013 07:42:44
[LAN access from remote] from 123.123.96.140:42142 to 192.168.1.4:17145, Friday, August 30, 2013 07:40:48
[LAN access from remote] from 112.24.247.181:18414 to 192.168.1.4:17145, Friday, August 30, 2013 07:35:23
[LAN access from remote] from 68.148.49.25:4676 to 192.168.1.4:17145, Friday, August 30, 2013 07:34:58
[LAN access from remote] from 119.84.114.8:16695 to 192.168.1.4:17145, Friday, August 30, 2013 07:34:52
[LAN access from remote] from 184.173.3.14:52749 to 192.168.1.4:17145, Friday, August 30, 2013 07:33:08
[LAN access from remote] from 81.39.252.207:5613 to 192.168.1.4:17145, Friday, August 30, 2013 07:33:04
[LAN access from remote] from 189.124.181.147:14187 to 192.168.1.4:17145, Friday, August 30, 2013 07:32:53
[LAN access from remote] from 2.138.66.179:10254 to 192.168.1.4:17145, Friday, August 30, 2013 07:27:56
[LAN access from remote] from 62.18.49.220:29870 to 192.168.1.4:17145, Friday, August 30, 2013 07:26:57
[LAN access from remote] from 88.185.111.161:1024 to 192.168.1.4:17145, Friday, August 30, 2013 07:25:37
[LAN access from remote] from 123.123.96.140:42142 to 192.168.1.4:17145, Friday, August 30, 2013 07:25:35
[LAN access from remote] from 177.117.32.136:38972 to 192.168.1.4:17145, Friday, August 30, 2013 07:25:02
[LAN access from remote] from 27.190.94.35:21062 to 192.168.1.4:17145, Friday, August 30, 2013 07:24:29
[LAN access from remote] from 79.40.56.45:4672 to 192.168.1.4:17145, Friday, August 30, 2013 07:23:15
[LAN access from remote] from 2.137.221.119:38964 to 192.168.1.4:17145, Friday, August 30, 2013 07:22:13
[LAN access from remote] from 89.73.218.0:37114 to 192.168.1.4:17145, Friday, August 30, 2013 07:21:39
[LAN access from remote] from 222.188.209.234:28162 to 192.168.1.4:17145, Friday, August 30, 2013 07:21:39
[LAN access from remote] from 121.225.233.197:20184 to 192.168.1.4:17145, Friday, August 30, 2013 07:18:12
[LAN access from remote] from 183.141.116.144:18096 to 192.168.1.4:17145, Friday, August 30, 2013 07:16:02
[LAN access from remote] from 177.156.158.206:50493 to 192.168.1.4:17145, Friday, August 30, 2013 07:15:30
[LAN access from remote] from 187.23.89.122:1820 to 192.168.1.4:17145, Friday, August 30, 2013 07:15:14
[LAN access from remote] from 62.57.61.53:8733 to 192.168.1.4:17145, Friday, August 30, 2013 07:14:21
[LAN access from remote] from 87.21.248.180:8806 to 192.168.1.4:17145, Friday, August 30, 2013 07:14:13
[LAN access from remote] from 183.208.12.17:22407 to 192.168.1.4:17145, Friday, August 30, 2013 07:11:34
[LAN access from remote] from 111.225.231.174:24106 to 192.168.1.4:17145, Friday, August 30, 2013 07:07:19
[LAN access from remote] from 60.177.222.43:39817 to 192.168.1.4:17145, Friday, August 30, 2013 07:07:13
[LAN access from remote] from 180.158.16.134:28165 to 192.168.1.4:17145, Friday, August 30, 2013 07:07:12
[LAN access from remote] from 101.70.12.66:17357 to 192.168.1.4:17145, Friday, August 30, 2013 07:07:04
[LAN access from remote] from 115.135.244.182:20766 to 192.168.1.4:17145, Friday, August 30, 2013 07:06:56
[LAN access from remote] from 24.230.242.244:22810 to 192.168.1.4:17145, Friday, August 30, 2013 07:06:06
[LAN access from remote] from 36.48.237.105:24830 to 192.168.1.4:17145, Friday, August 30, 2013 07:05:16
[LAN access from remote] from 183.94.84.10:4619 to 192.168.1.4:17145, Friday, August 30, 2013 07:05:14
[LAN access from remote] from 121.225.233.197:20184 to 192.168.1.4:17145, Friday, August 30, 2013 07:05:12
[admin login] from source 192.168.1.6, Friday, August 30, 2013 07:05:11
[LAN access from remote] from 175.155.224.117:10424 to 192.168.1.4:17145, Friday, August 30, 2013 07:05:08
[LAN access from remote] from 218.26.232.172:23401 to 192.168.1.4:17145, Friday, August 30, 2013 07:05:01
[LAN access from remote] from 183.208.12.17:10218 to 192.168.1.4:17145, Friday, August 30, 2013 07:05:00
[LAN access from remote] from 183.178.26.207:23133 to 192.168.1.4:17145, Friday, August 30, 2013 07:04:44
[LAN access from remote] from 117.88.130.5:1228 to 192.168.1.4:17145, Friday, August 30, 2013 07:03:12
[LAN access from remote] from 113.224.156.6:21522 to 192.168.1.4:17145, Friday, August 30, 2013 07:03:10
[LAN access from remote] from 27.154.166.106:11078 to 192.168.1.4:17145, Friday, August 30, 2013 07:03:09
[LAN access from remote] from 112.5.234.247:34247 to 192.168.1.4:17145, Friday, August 30, 2013 07:03:01
[LAN access from remote] from 113.109.25.34:3255 to 192.168.1.4:17145, Friday, August 30, 2013 07:02:54
[LAN access from remote] from 122.227.205.222:1257 to 192.168.1.4:17145, Friday, August 30, 2013 07:02:52
[LAN access from remote] from 116.25.89.16:42695 to 192.168.1.4:17145, Friday, August 30, 2013 07:02:43
[LAN access from remote] from 124.95.156.3:20453 to 192.168.1.4:17145, Friday, August 30, 2013 07:01:43
[LAN access from remote] from 202.99.52.170:32671 to 192.168.1.4:17145, Friday, August 30, 2013 07:01:26
[LAN access from remote] from 27.105.29.62:17965 to 192.168.1.4:17145, Friday, August 30, 2013 07:01:09
[LAN access from remote] from 58.216.252.162:12947 to 192.168.1.4:17145, Friday, August 30, 2013 07:01:06
[LAN access from remote] from 60.0.135.193:57737 to 192.168.1.4:17145, Friday, August 30, 2013 07:00:50
[LAN access from remote] from 85.50.89.252:59277 to 192.168.1.4:17145, Friday, August 30, 2013 07:00:20
[LAN access from remote] from 95.22.72.141:1756 to 192.168.1.4:17145, Friday, August 30, 2013 07:00:12
[LAN access from remote] from 186.125.155.25:56737 to 192.168.1.4:17145, Friday, August 30, 2013 06:59:52
[LAN access from remote] from 115.206.178.43:5576 to 192.168.1.4:17145, Friday, August 30, 2013 06:59:26
[LAN access from remote] from 218.29.108.6:13751 to 192.168.1.4:17145, Friday, August 30, 2013 06:59:20
[LAN access from remote] from 125.110.110.177:5839 to 192.168.1.4:17145, Friday, August 30, 2013 06:59:15
[LAN access from remote] from 14.153.114.90:2334 to 192.168.1.4:17145, Friday, August 30, 2013 06:59:09
[LAN access from remote] from 123.112.148.82:11280 to 192.168.1.4:17145, Friday, August 30, 2013 06:59:08
[LAN access from remote] from 183.160.249.107:19494 to 192.168.1.4:17145, Friday, August 30, 2013 06:59:07
[LAN access from remote] from 221.232.135.51:29143 to 192.168.1.4:17145, Friday, August 30, 2013 06:59:01
[LAN access from remote] from 24.55.29.239:1795 to 192.168.1.4:17145, Friday, August 30, 2013 06:57:30
[LAN access from remote] from 177.143.140.249:16918 to 192.168.1.4:17145, Friday, August 30, 2013 06:57:19
[LAN access from remote] from 183.219.185.41:27134 to 192.168.1.4:17145, Friday, August 30, 2013 06:57:14
[LAN access from remote] from 183.195.58.55:25502 to 192.168.1.4:17145, Friday, August 30, 2013 06:57:08
[LAN access from remote] from 183.12.6.82:23529 to 192.168.1.4:17145, Friday, August 30, 2013 06:57:08
[LAN access from remote] from 123.126.82.64:47010 to 192.168.1.4:17145, Friday, August 30, 2013 06:57:04
[LAN access from remote] from 180.113.36.24:25091 to 192.168.1.4:17145, Friday, August 30, 2013 06:56:58
[LAN access from remote] from 221.178.41.76:15270 to 192.168.1.4:17145, Friday, August 30, 2013 06:56:58
[LAN access from remote] from 27.17.78.4:23309 to 192.168.1.4:17145, Friday, August 30, 2013 06:56:56
[LAN access from remote] from 95.240.59.249:14450 to 192.168.1.4:17145, Friday, August 30, 2013 06:56:15
[LAN access from remote] from 189.47.126.40:19796 to 192.168.1.4:17145, Friday, August 30, 2013 06:53:16
[LAN access from remote] from 83.32.24.96:1985 to 192.168.1.4:17145, Friday, August 30, 2013 06:53:14
[LAN access from remote] from 114.89.139.2:35793 to 192.168.1.4:17145, Friday, August 30, 2013 06:50:52
[LAN access from remote] from 124.51.203.65:23047 to 192.168.1.4:17145, Friday, August 30, 2013 06:50:38
[LAN access from remote] from 85.247.79.133:51925 to 192.168.1.4:17145, Friday, August 30, 2013 06:50:36
[LAN access from remote] from 218.29.108.6:20025 to 192.168.1.4:17145, Friday, August 30, 2013 06:48:09
[LAN access from remote] from 1.165.194.66:55339 to 192.168.1.4:17145, Friday, August 30, 2013 06:46:45
[LAN access from remote] from 177.140.126.228:28350 to 192.168.1.4:17145, Friday, August 30, 2013 06:46:17
[admin login] from source 192.168.1.6, Friday, August 30, 2013 06:46:12
[LAN access from remote] from 218.201.101.9:26840 to 192.168.1.4:17145, Friday, August 30, 2013 06:44:13
[LAN access from remote] from 122.227.205.222:1257 to 192.168.1.4:17145, Friday, August 30, 2013 06:44:00
[LAN access from remote] from 189.47.126.40:19796 to 192.168.1.4:17145, Friday, August 30, 2013 06:43:38
[LAN access from remote] from 1.165.194.66:55339 to 192.168.1.4:17145, Friday, August 30, 2013 06:41:32
[LAN access from remote] from 189.72.59.129:19652 to 192.168.1.4:17145, Friday, August 30, 2013 06:40:16
[LAN access from remote] from 218.29.12.152:13804 to 192.168.1.4:17145, Friday, August 30, 2013 06:37:58
[LAN access from remote] from 116.25.89.16:42695 to 192.168.1.4:17145, Friday, August 30, 2013 06:37:40
[LAN access from remote] from 95.23.104.110:23466 to 192.168.1.4:17145, Friday, August 30, 2013 06:35:46
[DoS Attack: ACK Scan] from source: 209.197.6.231, port 80, Friday, August 30, 2013 06:34:32
[LAN access from remote] from 213.122.135.138:22446 to 192.168.1.4:17145, Friday, August 30, 2013 06:33:40
[LAN access from remote] from 1.34.158.93:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:32:41
[LAN access from remote] from 189.55.90.110:32333 to 192.168.1.4:17145, Friday, August 30, 2013 06:32:38
[LAN access from remote] from 190.155.142.34:27732 to 192.168.1.4:17145, Friday, August 30, 2013 06:32:34
[LAN access from remote] from 180.73.7.200:32014 to 192.168.1.4:17145, Friday, August 30, 2013 06:32:16
[LAN access from remote] from 88.219.56.151:27392 to 192.168.1.4:17145, Friday, August 30, 2013 06:32:03
[LAN access from remote] from 121.8.20.38:12034 to 192.168.1.4:17145, Friday, August 30, 2013 06:31:49
[LAN access from remote] from 189.76.66.10:23573 to 192.168.1.4:17145, Friday, August 30, 2013 06:30:57
[LAN access from remote] from 109.93.65.190:28439 to 192.168.1.4:17145, Friday, August 30, 2013 06:30:52
[LAN access from remote] from 86.101.207.141:27506 to 192.168.1.4:17145, Friday, August 30, 2013 06:30:21
[LAN access from remote] from 172.250.106.212:33337 to 192.168.1.4:17145, Friday, August 30, 2013 06:29:52
[LAN access from remote] from 85.57.206.98:12723 to 192.168.1.4:17145, Friday, August 30, 2013 06:29:52
[LAN access from remote] from 95.90.169.204:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:29:39
[DoS Attack: SYN/ACK Scan] from source: 50.57.31.181, port 80, Friday, August 30, 2013 06:29:23
[LAN access from remote] from 2.101.231.183:41912 to 192.168.1.4:17145, Friday, August 30, 2013 06:29:18
[LAN access from remote] from 79.101.241.94:4205 to 192.168.1.4:17145, Friday, August 30, 2013 06:29:16
[LAN access from remote] from 80.119.210.95:13935 to 192.168.1.4:17145, Friday, August 30, 2013 06:28:58
[LAN access from remote] from 114.89.139.2:35793 to 192.168.1.4:17145, Friday, August 30, 2013 06:28:50
[LAN access from remote] from 87.9.164.15:21135 to 192.168.1.4:17145, Friday, August 30, 2013 06:28:18
[LAN access from remote] from 211.176.108.31:10640 to 192.168.1.4:17145, Friday, August 30, 2013 06:28:14
[LAN access from remote] from 59.66.207.228:5156 to 192.168.1.4:17145, Friday, August 30, 2013 06:27:50
[LAN access from remote] from 223.206.152.81:11979 to 192.168.1.4:17145, Friday, August 30, 2013 06:27:45
[admin login] from source 192.168.1.6, Friday, August 30, 2013 06:27:36
[LAN access from remote] from 201.25.160.188:63601 to 192.168.1.4:17145, Friday, August 30, 2013 06:27:32
[DHCP IP: 192.168.1.6] to MAC address 00:0f:66:7a:46:30, Friday, August 30, 2013 06:27:14
[Access Control] Device unknown with MAC address 00:0F:66:7A:46:30 is allowed to access the network, Friday, August 30, 2013 06:
[LAN access from remote] from 79.40.56.45:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:27:09
[Access Control] Device unknown with MAC address 00:25:B3:5A:EE:98 is allowed to access the network, Friday, August 30, 2013 06:
[DHCP IP: 192.168.1.5] to MAC address 00:25:b3:5a:ee:98, Friday, August 30, 2013 06:26:20
[LAN access from remote] from 91.91.247.109:28803 to 192.168.1.2:8988, Friday, August 30, 2013 06:25:56
[LAN access from remote] from 91.91.247.109:50208 to 192.168.1.2:8988, Friday, August 30, 2013 06:25:56
[LAN access from remote] from 92.82.204.25:8732 to 192.168.1.7:16254, Friday, August 30, 2013 06:25:54
[UPnP set event: add_nat_rule] from source 192.168.1.2, Friday, August 30, 2013 06:25:52
[DHCP IP: 192.168.1.2] to MAC address 00:22:fa:f0:23:98, Friday, August 30, 2013 06:25:42
[Access Control] Device unknown with MAC address 00:22:FA:F0:23:98 is allowed to access the network, Friday, August 30, 2013 06:
[DoS Attack: SYN/ACK Scan] from source: 50.57.31.181, port 80, Friday, August 30, 2013 06:25:22
[LAN access from remote] from 2.236.9.109:28908 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:55
[LAN access from remote] from 78.236.172.233:7671 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:26
[LAN access from remote] from 90.34.3.196:61340 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:25
[LAN access from remote] from 79.26.131.136:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:21
[LAN access from remote] from 81.48.29.89:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:21
[LAN access from remote] from 81.137.229.177:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:21
[LAN access from remote] from 24.52.225.135:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:20
[LAN access from remote] from 190.193.62.56:1755 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:20
[LAN access from remote] from 111.252.53.194:57981 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:17
[LAN access from remote] from 151.27.178.144:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:16
[LAN access from remote] from 83.152.197.11:23339 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:14
[LAN access from remote] from 82.83.85.59:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:14
[LAN access from remote] from 183.178.197.44:9005 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:14
[LAN access from remote] from 79.25.88.13:21946 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:14
[LAN access from remote] from 95.253.188.33:56670 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:14
[LAN access from remote] from 86.68.205.49:15896 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:14
[LAN access from remote] from 213.233.38.59:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:14
[LAN access from remote] from 190.155.142.34:27732 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:14
[LAN access from remote] from 183.136.156.9:20598 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:03
[LAN access from remote] from 87.146.101.122:28996 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:03
[LAN access from remote] from 220.98.133.97:14963 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:02
[LAN access from remote] from 121.8.20.38:12034 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:02
[LAN access from remote] from 122.234.138.244:18808 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:02
[LAN access from remote] from 79.41.244.119:30185 to 192.168.1.4:17145, Friday, August 30, 2013 06:24:00
[LAN access from remote] from 88.219.56.151:27392 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:59
[LAN access from remote] from 84.120.38.174:55548 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:57
[LAN access from remote] from 76.179.103.101:14245 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:56
[LAN access from remote] from 2.231.222.169:22190 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:56
[LAN access from remote] from 95.246.107.134:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:55
[LAN access from remote] from 79.155.134.85:52778 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:55
[LAN access from remote] from 112.23.165.178:20189 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:54
[LAN access from remote] from 58.35.216.7:23050 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:53
[LAN access from remote] from 223.83.168.14:24734 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:52
[LAN access from remote] from 114.33.112.227:40597 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:52
[LAN access from remote] from 108.70.62.221:14605 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:50
[LAN access from remote] from 90.162.105.247:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:50
[LAN access from remote] from 115.43.139.4:20382 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:50
[LAN access from remote] from 95.23.104.110:23466 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:45
[LAN access from remote] from 83.27.157.9:16863 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:45
[LAN access from remote] from 85.57.206.98:12723 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:45
[LAN access from remote] from 99.178.135.60:56975 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:45
[LAN access from remote] from 77.175.46.205:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:45
[LAN access from remote] from 84.26.0.165:8080 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:44
[LAN access from remote] from 111.165.214.35:17513 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:41
[LAN access from remote] from 72.11.36.17:11835 to 192.168.1.7:16254, Friday, August 30, 2013 06:23:40
[LAN access from remote] from 83.77.93.160:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:40
[LAN access from remote] from 114.95.190.59:16875 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:37
[LAN access from remote] from 187.14.87.106:26630 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:27
[LAN access from remote] from 62.167.48.51:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:26
[LAN access from remote] from 77.127.165.79:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:21
[LAN access from remote] from 87.4.115.30:11746 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:21
[LAN access from remote] from 78.129.22.233:7000 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:21
[LAN access from remote] from 36.224.180.66:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:20
[LAN access from remote] from 81.202.159.234:32405 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:20
[LAN access from remote] from 77.164.68.220:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:20
[LAN access from remote] from 123.192.103.53:10470 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:14
[LAN access from remote] from 88.121.5.64:5661 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:14
[LAN access from remote] from 172.250.106.212:33337 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:14
[LAN access from remote] from 195.208.161.21:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:14
[LAN access from remote] from 201.231.4.134:29853 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:14
[LAN access from remote] from 84.58.209.50:4673 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:14
[LAN access from remote] from 5.39.89.189:33833 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:14
[LAN access from remote] from 83.6.2.117:33570 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:03
[LAN access from remote] from 24.145.87.183:36024 to 192.168.1.4:17145, Friday, August 30, 2013 06:23:01
[LAN access from remote] from 87.9.164.15:21135 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:58
[LAN access from remote] from 1.34.158.93:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:51
[LAN access from remote] from 77.92.36.122:34724 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:51
[LAN access from remote] from 78.160.115.198:10893 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:49
[LAN access from remote] from 220.133.9.209:12345 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:46
[LAN access from remote] from 88.24.253.111:1985 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:45
[LAN access from remote] from 77.229.196.7:4333 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:45
[LAN access from remote] from 59.66.207.228:5156 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:44
[LAN access from remote] from 189.55.90.110:32333 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:44
[LAN access from remote] from 95.39.129.193:5672 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:43
[LAN access from remote] from 79.23.103.22:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:41
[LAN access from remote] from 62.83.213.94:41811 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:28
[LAN access from remote] from 79.146.231.54:47015 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:26
[LAN access from remote] from 79.36.235.128:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:22
[LAN access from remote] from 76.102.50.125:4672 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:21
[LAN access from remote] from 80.24.101.46:2626 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:21
[LAN access from remote] from 180.73.7.200:32014 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:17
[LAN access from remote] from 113.142.10.43:4106 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:14
[LAN access from remote] from 58.27.56.162:64571 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:14
[LAN access from remote] from 190.122.29.212:37829 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:14
[LAN access from remote] from 78.242.132.100:14672 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:14
[LAN access from remote] from 190.161.137.85:59710 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:14
[LAN access from remote] from 89.133.182.13:41607 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:14
[LAN access from remote] from 98.226.156.226:38147 to 192.168.1.4:17145, Friday, August 30, 2013 06:22:13

edit: I should note that my downstream power levels used to hang around ~7, they are slowly getting lower and lower.

Dmaineminent

join:2013-08-23
Saint Augustine, FL

1 edit
The downstream levels are back up to 5-7.

Yesterday there were no outages, I did see these in the logs though, around the time I saw a couple Comcast techs out at a box nearby.

Aug 30 2013 15:03:31 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Aug 30 2013 15:03:26 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;

No outages yesterday, as I said before. But I did just experience another outage a few minutes ago, nothing in the logs.

Any tips would be greatly appreciated at this point? what could cause this sort of random outages?

n_w95482
Premium
join:2005-08-03
Ukiah, CA
reply to Dmaineminent

Re: [Connectivity] Losing connection multiple times a day

Looking over your other thread, I saw a couple of times where you mentioned just power cycling the router got things up and running, and no mentions of trying it with just the modem (no router). If power cycling the router by itself is getting it running again, it's likely that the problem lies there. The only effect it would have on the modem would be re-establishing the Ethernet connection. That can be tested by leaving the modem and router on when the problem occurs and unplugging the cable between them for a minute or so.

I know it's very inconvenient to bypass the router and connect just one PC to the modem, especially if it's for a couple of days, but it's an important step from a troubleshooting perspective. I'm not yet convinced that the longer-term issue lies with the modem or Comcast.
--
KI6RIT

Dmaineminent

join:2013-08-23
Saint Augustine, FL
said by n_w95482:

I know it's very inconvenient to bypass the router and connect just one PC to the modem, especially if it's for a couple of days, but it's an important step from a troubleshooting perspective. I'm not yet convinced that the longer-term issue lies with the modem or Comcast.

Would I have to set up a different network to connect to the modem directly? I can connect and get internet access from the router immediately, but when I try to directly connect to the modem, nothing happens.


nerdburg
Premium
join:2009-08-20
Schuylkill Haven, PA
kudos:1
Anytime you connect via ethernet to the modem, you'll have to powercycle it. What are the lights on your modem doing when you have problems?

Dmaineminent

join:2013-08-23
Saint Augustine, FL
said by nerdburg:

Anytime you connect via ethernet to the modem, you'll have to powercycle it. What are the lights on your modem doing when you have problems?

I'll give that a shot next time, anytime I've noticed the internet going out, there is nothing abnormal about the modem or router lights.

Dmaineminent

join:2013-08-23
Saint Augustine, FL
Happened again earlier, and once again a few minutes ago. This was almost a week without any disrupted connection. No abnormalities regarding the lights on the modems or routers.

Hypothetically, if the downstream power level was messed up in a modem, what would happen? and how would it happen? exactly?

Dmaineminent

join:2013-08-23
Saint Augustine, FL
Sep 08 2013 07:57:57 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 08 2013 06:44:26 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:d6:24:24;CMTS-MAC=00:01:5c:3c:96:4c;CM-QOS=1.1;CM-VER=3.0;

Some log messages from this morning

Also, a capture of my levels

Downstream Bonding Channel Value
Channel ID 1 2 3 8
Frequency 627000000 Hz 633000000 Hz 639000000 Hz 669000000 Hz
Signal to Noise Ratio 37 dB 36 dB 37 dB 37 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
6 dBmV 7 dBmV 6 dBmV 4 dBmV
Upstream Bonding Channel Value
Channel ID 11 10
Frequency 27900000 Hz 34800000 Hz
Ranging Service ID 11675 11675
Symbol Rate 5.120 Msym/sec 5.120 Msym/sec
Power Level 42 dBmV 42 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[3] 64QAM

Ranging Status Success Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 1 2 3 8
Total Unerrored Codewords 446343876 446343881 446343970 446343971
Total Correctable Codewords 14 13 55 16
Total Uncorrectable Codewords 730 728 597 635


Alcohol
Premium
join:2003-05-26
Climax, MI
kudos:4
reply to Dmaineminent
I had similar problems that i couldn't figure out (no logs) Turned it out was the dlink router i was using. Replaced it with asus ac66u and it's been solid.

I agree with the guy above, try connecting directly to modem.
--
I found the key to success but somebody changed the lock.

Dmaineminent

join:2013-08-23
Saint Augustine, FL
What exactly was happening in your situation, Alcohol ?


Alcohol
Premium
join:2003-05-26
Climax, MI
kudos:4
internet was going out every time i used anything that used up a lot of bandwidth (but it would also happen overnight and at random times) The router would then auto reset and i would lose connection for about 45 seconds.
--
I found the key to success but somebody changed the lock.

Dmaineminent

join:2013-08-23
Saint Augustine, FL

3 edits
Mine requires a full power cycle, so I don't think we have the same issue. Here are the logs from my router, as it just happened a minute ago, and just power cycling the Modem did not fix the issue. I have got a replacement router though in the past and the issue persists.

[admin login] from source 192.168.1.6
[DHCP IP: 192.168.1.3] to MAC address 84:29:99:50:dc:bf
[Access Control] Device E007350S-IPAD with MAC address 84:29:99:50:DC:BF is allowed to access the network.
[WLAN access rejected: incorrect security] from MAC address 84:29:99:50:dc:bf
[Access Control] Device ANDROID_2918E1345A930D94 with MAC address 8C:E0:81:FE:F7:E8 is allowed to access the network.
[DHCP IP: 192.168.1.2] to MAC address 8c:e0:81:fe:f7:e8
[Access Control] Device ADMIN-PC with MAC address 00:0F:66:7A:46:30 is allowed to access the network.
[DHCP IP: 192.168.1.6] to MAC address 00:0f:66:7a:46:30
[Internet connected] IP address: 69.180.87.93
[Initialized, firmware version: V1.0.0.40]

I hate these logs since they reset every freakin single time I power cycle it.

More downstream levels, what determines what Channel ID is displayed??????

Downstream Bonding Channel Value
Channel ID 1 5 6 8
Frequency 627000000 Hz 651000000 Hz 657000000 Hz 669000000 Hz
Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
6 dBmV 6 dBmV 7 dBmV 4 dBmV

Also I am using a SB6121, DOCSIS 3.0. Does Comcast need to know that I am using DOCSIS 3.0? even if I've had it since the tech came out and installed the cable services?

Dmaineminent

join:2013-08-23
Saint Augustine, FL
reply to Dmaineminent
I've had a few disconnections today, I noticed that the problem is solved by power cycling JUST the router, where should I go from here?

I had a different issue before and I ended up getting a replacement router, the one I am currently using

BeefJerky9

join:2005-05-28
Spring, TX
said by Dmaineminent:

I've had a few disconnections today, I noticed that the problem is solved by power cycling JUST the router, where should I go from here?

I had a different issue before and I ended up getting a replacement router, the one I am currently using

I'm assuming you've already tried different cables, so I'll skip that.

First thing is to get a hold of another router and try that. You can always return it if it doesn't fix the issue.

If that doesn't fix it, it is time to try a different modem. I had a weird issue with DSL modem where rebooting the router would get my connection back. However, replacing the router didn't help, so I tried another modem which solved the issue. I'm guessing something was wrong with the modem causing it to send out something that knocked out the ethernet port on the router until reboot.

So, try another router; if that doesn't fix it, try another modem. If that still doesn't fix it, well...dunno.

Dmaineminent

join:2013-08-23
Saint Augustine, FL
It has been more than a month since I bought the modem and router from Walmart (they don't keep receipts of transactions more than a month), and I may have misplaced my receipt. Are you recommending getting the same modem, just a replacement?

medbuyer

join:2003-11-20
kudos:4
reply to Dmaineminent
said by Dmaineminent:

I've had a few disconnections today, I noticed that the problem is solved by power cycling JUST the router, where should I go from here?

I had a different issue before and I ended up getting a replacement router, the one I am currently using

did you try connecting to the modem directly?

somebody suggested that and you didn't post if you did it or not.

that's the first thing I would check...connectivity at the modem level...if that's ok...then I guess it's your N300 that's causing the issue since you mentioned rebooting it solves the issue.

BeefJerky9

join:2005-05-28
Spring, TX
reply to Dmaineminent
said by Dmaineminent:

It has been more than a month since I bought the modem and router from Walmart (they don't keep receipts of transactions more than a month), and I may have misplaced my receipt. Are you recommending getting the same modem, just a replacement?

Same model is fine. But, I would try another router before trying another modem.

As medbuyer suggests, you might try bypassing the router and testing with your PC directly connected to the modem. However, this doesn't 100% rule out the modem. In the case of my bad DSL modem, I didn't have connection problems when directly connected to the modem. I'm guessing the router's ethernet was more sensitive to whatever the bad modem was doing.


plencnerb
Premium
join:2000-09-25
Carpentersville, IL
kudos:3
reply to Dmaineminent
Below is a link to a front page news story that appeared back in March of 2012.

»Exploring DIY Linux Router Distros

In it, ryan711 See Profile talks about their reason for building their own router. The opening statements of the news story are below

quote:
Router lockups have been a problem for me ever since I got my first 802.11G Router in 2004. Since then, we've seen companies roll out supposed "power user" routers or routers meant for "gamers," but for some reason not a single one has alleviated the problem of having to reset the router after running for a few days. After my new "gaming" router locked up while refreshing a server list for a multiplayer game, it was the last straw and I began searching for something a little more robust.


In ryan711 See Profile's case, the router that was being used was just not powerful enough for the traffic that was being pushed through it. They go into more detail that when they would remove the router, they had no more lockups. Put the router back, and add all the devices in the house back, and *poof* router would lock up.

So, I don't know if building your own Linux-based firewall/router is something you would be willing to do. However, I did want to point out that as an option to solve your problem.

As a side note, I went that route using an old dell tower, and am currently running pfSense on it. For someone that knows zip about Linux, I had it up and running in just under 30 minutes.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

n_w95482
Premium
join:2005-08-03
Ukiah, CA
reply to medbuyer
I asked him that in two threads, and yet here we are. I think I'm done offering my assistance here .
--
KI6RIT

Dmaineminent

join:2013-08-23
Saint Augustine, FL
reply to Dmaineminent
said by n_w95482:

I asked him that in two threads, and yet here we are. I think I'm done offering my assistance here

The last problem I had was unrelated to this one, I solved that problem, it being a bad power outlet, the modem was actually rebooting and it showed in the logs, where as here there is nothing in the logs, and rebooting the modem alone would have fixed it before, where as rebooting the router alone fixes this problem, the two are different problems, so please don't assume I simply keep ignoring your advice, new problem, new solutions. I thank you, and everyone else, for your continued support and help on the matter.

Now, back on topic. For the last ~2 days or so, I've had the issue (again), I noticed with all the swip swapping I have done with cables, there was an older ethernet cable connected. I replaced it around ~12pm. No disconnections so far.

I will try next time to connect a laptop directly to the modem when it goes out again. As for leaving it plugged in and waiting for a disconnect, it's just not feasible, the problem went away for almost a week. Will connecting directly to the modem right after the problem has occurred (is occurring) reasonable ?

Newegg
Comcast steals modems

join:2004-11-14
Norcross, GA
reply to Dmaineminent
I have the same problem here for a 2 months now, connected directly to the modem. Connection interrupts for 10 seconds or so multiple times, but the modem doesn't disconnect and there is nothing in the log. I also reinstalled Windows and I'm running no software other than windows updates.

medbuyer

join:2003-11-20
kudos:4
reply to Dmaineminent
said by Dmaineminent:

I will try next time to connect a laptop directly to the modem when it goes out again. As for leaving it plugged in and waiting for a disconnect, it's just not feasible, the problem went away for almost a week. Will connecting directly to the modem right after the problem has occurred (is occurring) reasonable ?


why isn't it feasible? if the problem goes away, what does that tell you?

you're overthinking this....

connect a pc or laptop directly to your modem...observe for several days...if the problems goes out, IT IS your router.. IF NOT, then IT IS your modem. Period.

try it and report back here...

Dmaineminent

join:2013-08-23
Saint Augustine, FL
I meant it isn't feasible because the problem could disappear for a week again, and I could mistake that for it being solved. It's hard to pinpoint something that could easily not show itself for days at a time. I'll see what I can do.


plencnerb
Premium
join:2000-09-25
Carpentersville, IL
kudos:3
said by Dmaineminent:

I meant it isn't feasible because the problem could disappear for a week again, and I could mistake that for it being solved. It's hard to pinpoint something that could easily not show itself for days at a time. I'll see what I can do.

This goes along with the notes that I made, about the problem being with router itself if too much network traffic was hitting it at one time.

For example, lets say you have a household with 5 people (2 adults, and 3 kids). Each person has their own desktop computer, as well as a smartphone, and each kid has their own gaming system. That would be 5 desktops, 5 smartphones, and 3 gaming systems, for a total of 13 systems. Kind of extreme, but lets say for the 3 kids, they are all running file share applications like Limewire at the same time on each of their desktops. The two adults stream netflix movies 8 hours each day on both of their systems. Not to mention, the kids are using their own gaming system (for sake of argument, they all have an xbox 360 and are all playing Call of Duty Black Ops at the same time in a network game). Not to mention, all 5 smartphones are running and everyone is using them to post to facebook, update their status to Twitter, and so on.

Your router in that case may not be able to handle all that traffic at once, so it locks up.

You then go down to a single desktop, and test that for a week. The results of that test? No issues, no router lockups, no disconnects from the internet. So, you think its the router, and you go buy another one. You plug everything back in, and in a short amount of time, you have the same problem again. The problem was not resolved, as it may be the fact that you are trying to push to much traffic through the device.

Depending on what all is going on with your network at the same time, you may need to invest in a more robust router (business class comes to mind), or as I suggested build you own.

Again, this is just a suggestion, as I don't know your own network usage. But, it may be something you want to look into, and it could be the reason why a single desktop test may not find the proper problem.

--Brian
--
============================
--Brian Plencner

E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail

medbuyer

join:2003-11-20
kudos:4
reply to Dmaineminent
said by Dmaineminent:

I meant it isn't feasible because the problem could disappear for a week again, and I could mistake that for it being solved. It's hard to pinpoint something that could easily not show itself for days at a time. I'll see what I can do.

so which means the router is bad then....period...because if you drop a connection from the modem level not even a day or two with a direct connection then that tells you IT IS your modem...

and you sure that the coax line coming into your house isn't shared between your DirecTV and Comcast right? each has their own runs..

bottomline is, try a direct connection to your modem. if connection is stable for 3-5 days, go try a different router and see...