Let's try this again ...
Description Count Last Occurence Target Source
TCP- or UDP-based Port Scan 5731 Mon Jan 30 22:21:40 2017 220.127.116.11:51936 18.104.22.168:53
TCP- or UDP-based Port Scan 838 Mon Jan 30 21:35:51 2017 22.214.171.124:51395 126.96.36.199:53
TCP- or UDP-based Port Scan 3 Sun Jan 08 09:59:06 2017 188.8.131.52:44904 184.108.40.206:53
TCP- or UDP-based Port Scan 1 Sun Dec 25 16:00:09 2016 220.127.116.11:2123 18.104.22.168:55555
TCP- or UDP-based Port Scan 1 Mon Dec 26 11:58:34 2016 22.214.171.124:5081 126.96.36.199:5656
TCP- or UDP-based Port Scan 1 Wed Jan 04 08:40:10 2017 188.8.131.52:9084 184.108.40.206:56934
TCP- or UDP-based Port Scan 8 Tue Jan 10 18:01:58 2017 220.127.116.11:3864 18.104.22.168:42508
TCP- or UDP-based Port Scan 1 Sun Jan 08 09:59:16 2017 22.214.171.124:58786 126.96.36.199:53
TCP- or UDP-based Port Scan 7 Mon Jan 23 18:16:52 2017 188.8.131.52:8003 184.108.40.206:47354
TCP- or UDP-based Port Scan 1 Mon Jan 16 16:26:28 2017 220.127.116.11:32619 18.104.22.168:53
TCP- or UDP-based Port Scan 1 Mon Jan 16 16:29:11 2017 22.214.171.124:56728 126.96.36.199:53
TCP- or UDP-based Port Scan 1 Sat Jan 21 08:24:11 2017 188.8.131.52:30679 184.108.40.206:53
TCP- or UDP-based Port Scan 3 Sun Jan 29 18:34:11 2017 220.127.116.11:2016 18.104.22.168:51364
TCP- or UDP-based Port Scan 1 Thu Jan 26 20:31:25 2017 22.214.171.124:3386 126.96.36.199:59804
TCP- or UDP-based Port Scan 1 Sun Jan 29 13:20:54 2017 188.8.131.52:3391 184.108.40.206:54005
From the link you posted, the signals will be under Status, then connection. I didn't see the event log in any of those pictures though.
"From the link you posted, the signals will be under Status, then connection. I didn't see the event log in any of those pictures though."
Exactly GibsonAggie. Looking online, other Ubee models have event logs easily found - not mine though ! It figures. FYI, I decided to try something. Brought out my new work laptop, connected to internet via WiFi, and ran ping -t'd google. No issues whatsoever. At the same time, I did the same thing with the computer that's wired into the new modem/router, and had a few disconnects. I'm wondering if it's a computer problem now ... although it seems a bit odd that we've had NO issues with this 5 year old Dell and at the exact moment we hooked up the new modem/router combo, we started getting these disconnects. Also, just a reminder, I had ZERO issues with my old TWC modem and my Cicso router. Sorry to all for being such a pain. I'm *this close* to calling TWC and getting a tech out here, but just wanted to post one last thing. I'll probably call them this morning, but thought I'd just try this avenue first. Thanks again.
Well, there goes my theory that it's a computer problem. When I went to shut down my work laptop, I noticed a couple "request timed out"'s on my ping -t to google.com ...
Many people have had issues with the Ubee allin one combo's over the past couple years, unknown why it can't handle your ethernet adapters settings, that may also be some of the OS/browser updates as well.
Can you tag this solution so we can find it? If not, change your original post to add in network adapter setting issue...