Internet intermittentlly stops working for apps - Ping still functions.

L

LikeitornotYT

Greetings all. I was hoping someones google-foo is a little stronger than mine. Here is the scenario:

ScenarioSetup:

Lenovo W540 laptop with no docking station. (Issue also occurred with docking station)
Windows 10 Pro 64Bit, Version 1909 Build 18363.815 (Fully Updated)
Ethernet cable connected to Netgear R8500 and then Motorola Surfboard Cable Modem on Spectrum Cable (Issue also occurs using both the built in WiFi adapter as well as a Netgear A6100 adapter)
Laptop normally not rebooted and currently set to not go to sleep.
Default install, fully activated and registered. While purchased with Win 7 and updated to 10 previously this is currently a fresh Win 10 install from media.


Observation:

System will work perfectly fine for about 2 days normally, although some days the issue occurs 2-3 times in one day.
The issue starts with certain webpages not loading correctly. Missing images, page not formatted correctly, etc.
Within a few minutes all webpages fail. This is seen in Chrome, Firefox and Edge all at the same time. Even 192.1.68.1.1 will not load.
But it isn't just the browsers. Windows update, Issue Reporter and every single app that uses the Network stack fails to connect.
EXCEPT: Using a cmd window, ping and nslookup still work perfectly fine testing out google.com, microsoft.com, facebook.com and etc. All pages resolve and ping without issue.
Closing out browsers does not help. Re-seating Ethernet cable does not help. Rebooting router and modem does not help. Switching back and froth from Ethernet to wireless does not help. Rebooting the laptop fixes it 100% of the time.
Going into the Task Manager didn't show any obvious issues. CPU/Memory/Network and everything else was in the 0%-5% range.
No obvious failed services but I haven't done a complete stare and compare of every single one either.


So anyone out there have any ideas? Basically it appears that all GUI based applications lose connectivity to the networking stack even though the basic networking stack is still functioning. I checked the event logs and there does appear to be one error that I thought was the culprit:


Warning 5/1/2020 9:47:00 AM Tcpip 4231 None A request to allocate an ephemeral port number from the global TCP port space has failed due to all such ports being in use.

This error led me down the path of port exaustion: https://deploymentresearch.com/fix-for-windows-10-exhausted-pool-of-tcpip-ports/


But as far as I can tell netstat isn't showing it. unless I am just missing it.

I checked the netstat output the next time it happened and it didn't seem to be exhausted but maybe I just don't know what I am looking at.

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:623 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5040 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING
TCP 0.0.0.0:7040 0.0.0.0:0 LISTENING
TCP 0.0.0.0:7041 0.0.0.0:0 LISTENING
TCP 0.0.0.0:16992 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49664 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49665 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49666 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49667 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49670 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49823 0.0.0.0:0 LISTENING
TCP 0.0.0.0:50128 0.0.0.0:0 LISTENING
TCP 127.0.0.1:4343 0.0.0.0:0 LISTENING
TCP 127.0.0.1:4343 0.0.0.0:0 LISTENING
TCP 127.0.0.1:50006 0.0.0.0:0 LISTENING
TCP 192.168.1.21:139 0.0.0.0:0 LISTENING
TCP 192.168.1.21:49806 52.179.224.121:443 ESTABLISHED
TCP 192.168.1.21:49970 23.196.35.33:443 CLOSE_WAIT
TCP 192.168.1.21:49971 23.196.35.33:443 CLOSE_WAIT
TCP 192.168.1.21:49978 23.196.34.104:80 CLOSE_WAIT
TCP 192.168.1.21:49979 23.196.34.104:80 CLOSE_WAIT
TCP 192.168.1.21:49980 23.196.34.104:80 CLOSE_WAIT
TCP 192.168.1.21:49981 23.196.34.104:80 CLOSE_WAIT
TCP 192.168.1.21:49982 23.196.34.104:80 CLOSE_WAIT
TCP 192.168.1.21:49983 23.196.34.104:80 CLOSE_WAIT
TCP 192.168.1.21:49984 23.63.244.41:443 CLOSE_WAIT
TCP 192.168.1.21:49985 72.21.91.29:80 CLOSE_WAIT
TCP 192.168.1.21:49990 23.196.35.33:443 CLOSE_WAIT
TCP 192.168.1.21:50675 199.127.204.100:443 FIN_WAIT_2
TCP 192.168.1.21:50692 199.127.204.100:443 FIN_WAIT_2
TCP 192.168.1.21:57469 199.127.204.100:443 FIN_WAIT_2
TCP 192.168.1.21:64000 23.196.32.144:443 CLOSE_WAIT
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:623 [::]:0 LISTENING
TCP [::]:5357 [::]:0 LISTENING
TCP [::]:16992 [::]:0 LISTENING
TCP [::]:49664 [::]:0 LISTENING
TCP [::]:49665 [::]:0 LISTENING
TCP [::]:49666 [::]:0 LISTENING
TCP [::]:49667 [::]:0 LISTENING
TCP [::]:49670 [::]:0 LISTENING
TCP [::]:49823 [::]:0 LISTENING
TCP [::]:50128 [::]:0 LISTENING
TCP [::1]:50005 [::]:0 LISTENING
TCP [::1]:50009 [::1]:50011 ESTABLISHED
TCP [::1]:50011 [::1]:50009 ESTABLISHED
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:5050 *:*
UDP 0.0.0.0:5353 *:*
UDP 0.0.0.0:5353 *:*
UDP 0.0.0.0:5353 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:59109 *:*
UDP 0.0.0.0:59115 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:49952 *:*
UDP 127.0.0.1:59117 *:*
UDP 192.168.1.21:137 *:*
UDP 192.168.1.21:138 *:*
UDP 192.168.1.21:1900 *:*
UDP 192.168.1.21:49951 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:5353 *:*
UDP [::]:5353 *:*
UDP [::]:5355 *:*
UDP [::]:59110 *:*
UDP [::]:59116 *:*
UDP [::1]:1900 *:*
UDP [::1]:49950 *:*
UDP [fe80::4df9:1e21:25b:9cca%12]:1900 *:*

UDP [fe80::4df9:1e21:25b:9cca%12]:4


The AB output also didn't seem to show any obvious programs sucking down ports:


I attempted to manually clear the ports using netsh and seemed to get a possible error that suggested a reboot. Which we know the reboot fixes it. The CMD windows was run as admin so should have had all needed rights.


Resetting Compartment Forwarding, OK!
Resetting Compartment, OK!
Resetting Control Protocol, OK!
Resetting Echo Sequence Request, OK!
Resetting Global, OK!
Resetting Interface, OK!
Resetting Anycast Address, OK!
Resetting Multicast Address, OK!
Resetting Unicast Address, OK!
Resetting Neighbor, OK!
Resetting Path, OK!
Resetting Potential, OK!
Resetting Prefix Policy, OK!
Resetting Proxy Neighbor, OK!
Resetting Route, OK!
Resetting Site Prefix, OK!
Resetting Subinterface, OK!
Resetting Wakeup Pattern, OK!
Resetting Resolve Neighbor, OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , failed.
Access is denied.

Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Restart the computer to complete this action.

So if anyone out there has any additional suggestions of what to check they would be greatly appreciated.


So

Continue reading...
 

Similar threads

I
Replies
0
Views
249
Intr0v3rt
I
A
Replies
0
Views
244
AlanBargender
A
M
Replies
0
Views
192
MarsForever
M
Back
Top Bottom