Tech Support Forum banner
Status
Not open for further replies.

Wired internet disconnects briefly when under load

3K views 11 replies 3 participants last post by  Deleted 03/18/17 
#1 · (Edited)
Issue : Internet will disconnect when streaming, downloading or using any kind of bandwidth. Disconnects are no longer than 45 seconds and are intermittent. Sometimes it's three disconnects in a two hour netflix video. Other times it's five disconnects in a two minute period when streaming live videos. Websites will be slow to load, sometimes graphics will not load at all.

Two smart phones, one smart TV and one Roku are connected to the modem through a wireless connection. All devices experience this disconnect under load, not all devices are active at the same time when this occurs. Often times, the main desktop is the only active connection and disconnects still happen.

Internet details: ATT U-Verse (DSL)
Modem: ARRIS NVG589 (Provided by ATT. Hardwired connection to PC)

OS: Windows 7, SP 1

Anti-Virus/Firewall: Windows firewall has been off for months before the problem occured. Have Eset Smart security installed before problems occured but is now outdated.

IPConfig/ All :

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : attlocal.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : attlocal.net
Description . . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connectio
n
Physical Address. . . . . . . . . : 38-60-77-29-F8-84
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2602:306:cfe7:4080::48(Preferred)
Lease Obtained. . . . . . . . . . : Tuesday, January 31, 2017 7:41:36 AM
Lease Expires . . . . . . . . . . : Wednesday, March 01, 2017 2:11:02 AM
IPv6 Address. . . . . . . . . . . : 2602:306:cfe7:4080:45eb:252b:bef6:16b5(Pr
eferred)
Temporary IPv6 Address. . . . . . : 2602:306:cfe7:4080:408d:659f:e8fe:f27(Pre
ferred)
Link-local IPv6 Address . . . . . : fe80::45eb:252b:bef6:16b5%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.64(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, January 31, 2017 7:41:39 AM
Lease Expires . . . . . . . . . . : Wednesday, February 01, 2017 9:14:33 AM
Default Gateway . . . . . . . . . : fe80::923e:abff:fec2:86e0%11
192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 238575735
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-31-5B-4B-38-60-77-29-F8-84

DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.attlocal.net:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : attlocal.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Windows\system32>
 
See less See more
#2 ·
Is the modem losing connectivity to the ISP? Are all of the devices losing connectivity to the wifi router? When was the last time the modem/router were power cycled?

If all of the devices are staying connected to the router, then as the hardware is supplied by AT&T, you should contact their tech support.
 
#3 ·
How can I tell if the modem is losing connection to the ISP? I'm here because I am terrible at troubleshooting when it comes to networking.

The disconnects happen so fast that I can't tell if the phones and printers lose connection. It's only down for two to three seconds at a time before it reconnects. The modem/router was power cycled last week.

I changed the modem channel from 9 to 11. Switched ports the Ethernet cable was plugged into. Turned off IPv6 and tweaked a couple more settings. Nothing works. Just today I tried streaming something and as soon as the video loaded, I disconnected four times in a row.
 
#5 ·
2017-02-22T08:04:18-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T08:04:18-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T08:23:42-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T08:24:14-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T08:50:35-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T08:50:38-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T09:26:36-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T09:26:40-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T09:29:31-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T09:29:34-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T09:43:01-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T09:43:04-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T09:51:20-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:20-05:00 L3 sdb[330]: TCPPROXY: failed to send reply (errno 32 - Broken pipe).
2017-02-22T09:51:20-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:20-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:20-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:24-05:00 L3 sdb[330]: TCPPROXY: failed to receive the header message.
2017-02-22T09:51:24-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:24-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:24-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:25-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:25-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:27-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:27-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:28-05:00 L3 sdb[330]: TCPPROXY: failed to receive the header message.
2017-02-22T09:51:28-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:28-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:28-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:31-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:31-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:34-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:34-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:36-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:36-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:37-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:37-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:38-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:38-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:39-05:00 L3 sdb[330]: TCPPROXY: failed to receive the header message.
2017-02-22T09:51:39-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:39-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:39-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:41-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:41-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:43-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:43-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:44-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:44-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:45-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:45-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:46-05:00 L3 sdb[330]: TCPPROXY: failed to receive the header message.
2017-02-22T09:51:46-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:46-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:46-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:48-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:48-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:48-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:48-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:50-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:50-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:51-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:51-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:52-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:52-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:53-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:53-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:54-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:54-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:54-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:54-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:55-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:55-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:55-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:55-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:56-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:56-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:51:56-05:00 L3 sdb[330]: TCPPROXY: bad header message magic.
2017-02-22T09:51:56-05:00 L3 sdb[330]: TCPPROXY: failed to decode header message.
2017-02-22T09:58:50-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T09:58:53-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T10:04:58-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T10:05:00-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T10:05:07-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T10:05:09-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T10:13:42-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T10:13:45-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T10:28:59-05:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 4
2017-02-22T10:34:06-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T10:34:09-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T10:35:52-05:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 3
2017-02-22T10:41:10-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T10:41:13-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T10:41:24-05:00 L4 cwmp[1725]: Resolving ACS URL - Retry 0
2017-02-22T10:41:24-05:00 L5 cwmp[1725]: Connect to https://cwmp.c01.sbcglobal.net/cwmp/services/CWMP [144.160.58.42] Retry 0
2017-02-22T10:41:24-05:00 L5 cwmp[1725]: (SSL) Connect Success: cwmp.c01.sbcglobal.net
2017-02-22T10:41:24-05:00 L5 cwmp[1725]: (SSL) Certificate Verify Success: cwmp.c01.sbcglobal.net
2017-02-22T10:41:28-05:00 L5 cwmp[1725]: Post Inform - reason 2 PERIODIC
2017-02-22T10:41:28-05:00 L5 cwmp[1725]: Receive InformResponse
2017-02-22T10:41:28-05:00 L5 cwmp[1725]: Post 0
2017-02-22T10:41:28-05:00 L5 cwmp[1725]: next Periodic Inform after 86396 s
2017-02-22T10:41:28-05:00 L5 cwmp[1725]: Receive GetParameterValues
2017-02-22T10:41:29-05:00 L5 cwmp[1725]: Post GetParameterValuesResponse (chunk-length - 5069)
2017-02-22T10:41:29-05:00 L5 cwmp[1725]: Continue GetParameterValuesResponse (chunk-length - 0)
2017-02-22T10:41:29-05:00 L5 cwmp[1725]: Receive SetParameterValues
2017-02-22T10:41:29-05:00 L5 cwmp[1725]: Post SetParameterValuesResponse
2017-02-22T10:41:29-05:00 L5 cwmp[1725]: Receive GetParameterValues
2017-02-22T10:41:29-05:00 L5 cwmp[1725]: Post GetParameterValuesResponse (chunk-length - 5377)
2017-02-22T10:41:29-05:00 L5 cwmp[1725]: Continue GetParameterValuesResponse (chunk-length - 0)
2017-02-22T10:41:30-05:00 L5 cwmp[1725]: Closing connection on HTTP 204
2017-02-22T10:41:30-05:00 L5 cwmp[1725]: (SSL) Closing Connection: cwmp.c01.sbcglobal.net
2017-02-22T11:18:22-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T11:18:57-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T11:20:52-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T11:22:36-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T11:25:12-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T11:25:12-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T11:25:34-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T11:27:58-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T11:28:51-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T11:32:38-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T11:37:29-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T11:37:49-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T11:37:51-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T11:37:51-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T11:44:18-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T11:44:18-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T11:49:33-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T11:52:56-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T11:56:00-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T11:56:53-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T11:58:23-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T11:58:23-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T12:01:05-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T12:02:50-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T12:06:59-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T12:07:23-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T12:08:32-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T12:12:56-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T12:14:41-05:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 4
2017-02-22T12:19:12-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T12:19:12-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T12:30:26-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T12:30:29-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T12:54:52-05:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 4
2017-02-22T13:06:22-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T13:06:25-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T13:37:14-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T13:37:14-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T13:52:53-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T13:52:53-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T14:13:30-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T14:13:33-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T14:17:22-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T14:17:24-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T14:17:24-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T14:17:24-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T14:35:08-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T14:35:11-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T14:35:26-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T14:35:28-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T14:36:02-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T14:36:05-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T14:36:25-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T14:36:28-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T14:37:16-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T14:37:20-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T14:37:55-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T14:37:58-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T14:51:25-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T14:51:28-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T15:04:09-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T15:04:12-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T15:07:52-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T15:07:55-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T15:25:05-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T15:25:07-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T15:28:22-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T15:28:25-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-22T15:29:45-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T15:30:16-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T15:32:58-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T15:33:00-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 10 duplex full
2017-02-22T15:33:01-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-22T20:35:55-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T20:37:51-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T20:39:39-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T20:39:39-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T20:40:01-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T20:40:01-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T20:40:27-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T20:40:41-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T20:41:36-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T20:41:42-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T20:43:05-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T20:43:05-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T20:47:18-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T20:47:27-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T20:48:07-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T20:48:07-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T20:48:25-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T20:48:25-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T20:50:32-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T20:51:08-05:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 6
2017-02-22T20:53:06-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T20:55:14-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T21:02:13-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T21:32:43-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T21:32:43-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T22:44:47-05:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 6
2017-02-22T22:49:39-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T22:49:51-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T22:50:31-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T22:50:34-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T22:51:53-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T22:54:35-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T22:55:15-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T22:55:24-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T23:04:36-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T23:09:57-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T23:10:44-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-22T23:18:06-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T23:28:11-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T23:29:57-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-22T23:32:25-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-22T23:32:27-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-22T23:51:12-05:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 8
2017-02-23T00:05:03-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-23T00:05:05-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-23T00:22:19-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-23T00:29:46-05:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 7
2017-02-23T00:29:58-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-23T00:32:29-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-23T00:34:31-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-23T00:53:24-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-23T01:04:28-05:00 L3 dnsmasq[1578]: nameserver '68.94.156.10' is now responding
2017-02-23T01:07:55-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.157.10'
2017-02-23T01:09:59-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-23T01:13:28-05:00 L3 dnsmasq[1578]: no responses from nameserver '68.94.156.10'
2017-02-23T01:13:51-05:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 6
2017-02-23T02:11:38-05:00 L3 dnsmasq[1578]: nameserver '68.94.157.10' is now responding
2017-02-23T03:50:46-05:00 L3 sdb[330]: Wi-Fi: Number of clients associated on 2.4GHz radio 6
2017-02-23T06:29:17-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 10 duplex full
2017-02-23T06:29:18-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:29:20-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 1000 duplex full
2017-02-23T06:29:45-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:29:48-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-23T06:30:53-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:30:56-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-23T06:31:31-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:31:34-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-23T06:31:36-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:31:39-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-23T06:33:24-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:33:27-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-23T06:33:29-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:33:32-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-23T06:33:36-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:33:39-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-23T06:33:48-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:33:51-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-23T06:34:27-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:34:29-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-23T06:34:57-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:34:59-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
2017-02-23T06:35:00-05:00 L4 mcp[1518]: mcp: received invalid V3 group record type (1)
Here's a bit of the log. I disconnected twice while loading this website just now.
 
#8 · (Edited)
Ethernet port 2 is unoccupied. The computer plugs in to Ethernet port 3. The internet disconnects, seemingly, when there is a surge in bandwidth.

There's no specific time of day that it goes down. Loading a picture has caused the internet to disconnect. Live streams are the worst, I've sat and watched the quickbar networking icon go from red X to normal ten times if a row, all within three minutes.

Oddly enough, if I open ten live streams it doesn't disconnect. When it's one or two, it's down constantly. It could just by my imagination or timing but I don't understand it.

This happens every day, without fail.
 
#9 · (Edited)
Move the PC to another port.

If the errors in the log continue, there is an issue with the cable or the NIC in your computer. If the errors stop, the router port is faulty.

2017-02-23T06:34:57-05:00 L3 sdb[330]: ELAN: Port lan-3 (eth2) is DOWN
2017-02-23T06:34:59-05:00 L3 sdb[330]: ELAN: Port lan-3 is UP. (eth2) speed 100 duplex full
 
#10 ·
Oops. I confused the interface with the port. If you rule out the port and go to try a new ethernet, make sure it is a stock CAT5e or above in case duplexing is an issue. I notice the interface is only connecting at 100Mbps while the ISP gateway has all 10/100/1000Mbps ports. Does your computer have a gigabit NIC adapter?
 
#11 ·
I switched the cable to port 4 and everything was fine for awhile. Maybe two disconnects a week but it started happening more frequently.

I took a look in device manager and my network adapter is a Intel(R) 82579V Gigabit Network Connection. Under 'link speed', the speed and duplex was set to 100Mpbs full duplex. I switched it to auto negotiation, the speed is now listed at 1.0Gbps/Full duplex and some of my tests are showing that it's working pretty well. No disconnects yet.

I have no idea why the adapter was set to 100Mpbs/full duplex. I haven't installed a new cable yet, I don't think I have any lying around. I would assume if it was a proper cat5e cable, it would be printed on the cable itself, right?
 
#12 ·
The type of wire, and specifically damage to it, can effect how your computer negotiates the link speed. If it finds it can't properly send the packets, it will sometimes lower the rate to improve the connection. However there can also be compatibility issues between the router and your computer that can have nothing to do with the ethernet wire. I would still say replace the ethernet when you get around to it, but if changing the duplex seemed to improve things, then the next step is to run tests and see if you can replicate the issue under the new conditions. If you can't, I would say your issue is solved. If the problem still happens, just less, I would then replace the ethernet.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top