Random No Internet Access, works immediately after disconnecting and reconnecting??

[Greenboy44]

My setup:
Lenovo G780 laptop
With Broadcom PCI wifi adapter Model No. BCM94313HMGB.
IPS: COX
CISCO modem Model DPQ3212
EERO wifi router Model A010001

My laptop is the only device having problem with the network. Every 3 to 5 minutes, I would loose internet access while still connected to wifi network. Internet access resumes immediately after I disconnect from the network and reconnect. The interval of the problem seems random (sometimes just 5 seconds after re-connection, sometimes after 20 minutes). It happens even when my laptop is the only device connected to the network. Internet access does not return automatically with time, only when disconnect and reconnect manually.
The problems started when I stopped using AT&T wifi modem and switch to COX using my EERO router. Every other device in my network is working fine (including a surface pro 4, another HP laptop and several mobile devices).

I have tried:
- Updating wifi adapter driver, uninstall and reinstall.
- ipconifg /flushdns -> ipconfig /release -> ipconfig /renew
- Change to google open DNS 8.8.8.8

Is there something wrong with my wireless card? Should I try replacing it?

 

[KiL3MaNjAr0W]

can you bring up your cmd and type ipconfig /all >myTCP.txt​ and copy paste your results here

 

[Greenboy44]

can you bring up your cmd and type ipconfig /all >myTCP.txt​ and copy paste your results here

Here is my results from myTCP.txt:

Windows IP Configuration

Host Name . . . . . . . . . . . . : Gren-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Qualcomm Atheros AR8162/8166/8168 PCI-E Fast Ethernet Controller (NDIS 6.30)
Physical Address. . . . . . . . . : <removed>
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 13:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Hosted Network Virtual Adapter #2
Physical Address. . . . . . . . . : <removed>
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 14:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : <removed>
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 802.11n Network Adapter
Physical Address. . . . . . . . . : <removed>
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : <removed>
IPv4 Address. . . . . . . . . . . : <removed>
Subnet Mask . . . . . . . . . . . : <removed>
Lease Obtained. . . . . . . . . . : Wednesday, April 19, 2017 1:47:39 PM
Lease Expires . . . . . . . . . . : Wednesday, April 19, 2017 10:16:22 PM
Default Gateway . . . . . . . . . : <removed>
DHCP Server . . . . . . . . . . . : <removed>
DHCPv6 IAID . . . . . . . . . . . : <removed>
DHCPv6 Client DUID. . . . . . . . : <removed>
DNS Servers . . . . . . . . . . . : <removed>
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter
Physical Address. . . . . . . . . : <removed>
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : <removed>
Link-local IPv6 Address . . . . . : <removed>
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : <removed>
DHCPv6 Client DUID. . . . . . . . : <removed>
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{D0748F2F-2548-4E15-B244-A56C11A2470D}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : <removed>
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

 

[KiL3MaNjAr0W]

You have two different issues

frequent disconnects
failure to honor a release/new cycle ( I beleive ) after your ipconfig /release, ipconfig /renew you should have followed with an ipconfig /all so try that one more time.

Your ISP connection
WHO is it and what type {Dsl, Cable, Satellite} ?

DSL has special considerations which requires a filter on every device connected to the phone line OTHER than the modem. This is a direct contributor to the disconnect problem (*IF* you're using dsl)

You ought to get the make/model number of the router and look for a firmware update (regardless of {Dsl, Cable, Satellite} as you ought to be able to renew).

Here's a test you can run to determine if your router needs to reassemble packets:

get the command line and enter:
ping -f -l 1500 google.com​
1500 because 1500 is the MTU or Maximium Transmission Unit for an Ethernet packet and -8 because 8 bits equal 1 byte

My results are:
C:\Users\Richard Franklin>ping -f -l 1500 google.com​

Pinging google.com [74.125.22.139] with 1500 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 74.125.22.139:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

Now repeat that test by reducing the 1500 by -8 until it replies
C:\Users\Richard Franklin>ping -f -l 1440 google.com

Pinging google.com [172.217.7.174] with 1440 bytes of data:
Reply from 172.217.7.174: bytes=64 (sent 1440) time=43ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1440) time=31ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1440) time=24ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1440) time=22ms TTL=53

Ping statistics for 172.217.7.174:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 43ms, Average = 30ms
My test of the value just above that produced:
​C:\Users\Richard Franklin>ping -f -l 1448 google.com

Pinging google.com [172.217.7.174] with 1448 bytes of data:
Reply from 172.217.7.174: bytes=64 (sent 1448) time=35ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1448) time=26ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1448) time=34ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1448) time=24ms TTL=53

Ping statistics for 172.217.7.174:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 35ms, Average = 29ms

When packets get fragmented, the router needs to do extra work and not only is that a performance hit, but also a vector for a network virus. you should be able to set your MTU in the router itself.

Set the MTU to the highest value that replies with times and does not timeout.

 

[Greenboy44]

You have two different issues

frequent disconnects
failure to honor a release/new cycle ( I beleive ) after your ipconfig /release, ipconfig /renew you should have followed with an ipconfig /all so try that one more time.

Let's talk about your ISP connection - -
WHO is it and what type {Dsl, Cable, Satellite} ?

DSL has special considerations which requires a filter on every device connected to the phone line OTHER than the modem. This is a direct contributor to the disconnect problem (*IF* you're using dsl)

You ought to get the make/model number of the router and look for a firmware update (regardless of {Dsl, Cable, Satellite} as you ought to be able to renew).

Here's a test you can run to determine if your router needs to reassemble packets:

get the command line and enter:
ping -f -l 1500 google.com​
1500 because 1500 is the MTU or Maximium Transmission Unit for an Ethernet packet and -8 because 8 bits equal 1 byte

My results are:
C:\Users\Richard Franklin>ping -f -l 1500 google.com​

Pinging google.com [74.125.22.139] with 1500 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 74.125.22.139:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

Now repeat that test by reducing the 1500 by -8 until it replies
C:\Users\Richard Franklin>ping -f -l 1440 google.com

Pinging google.com [172.217.7.174] with 1440 bytes of data:
Reply from 172.217.7.174: bytes=64 (sent 1440) time=43ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1440) time=31ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1440) time=24ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1440) time=22ms TTL=53

Ping statistics for 172.217.7.174:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 43ms, Average = 30ms
My test of the value just above that produced:
​C:\Users\Richard Franklin>ping -f -l 1448 google.com

Pinging google.com [172.217.7.174] with 1448 bytes of data:
Reply from 172.217.7.174: bytes=64 (sent 1448) time=35ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1448) time=26ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1448) time=34ms TTL=53
Reply from 172.217.7.174: bytes=64 (sent 1448) time=24ms TTL=53

Ping statistics for 172.217.7.174:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 35ms, Average = 29ms

When packets get fragmented, the router needs to do extra work and not only is that a performance hit, but also a vector for network virus' So you should be able to set your MTU in the router itself.

Set the MTU to the highest value that replies with times and does not timeout.

I have tried ipconfig/release, ipconfig/renew, ipconfig/all as you said but to no avail.

My IPS is Cox Communications.
The modem Cox provided is a Cisco modem Model DPQ3212
My wifi router the EERO Model A010001

From entering ping -f -l 1500 google.com, ping -f -l 1440 google.com, ping -f -l 1448 google.com, my results are similar to yours except my ping average at 68 ms and TTL = 52