Can't use network despite having connection and connected

Verify the desktop connects via wifi?

Find your public IP address (go to whatismyip.com).  The next time you lose connectivity:

Do an IPCONFIG /ALL again, and record the results.  
PING your public IP address and record the results.
TRACERT WWW.GOOGLE.COM and record those results as well.

What is your setting on your Network Adapter? Is it Public or Private? I have had issues lately with Windows 10 devices for clients that the network adapter switches to public randomly and will cause issues. It works just like you are saying, sometimes great then out of nowhere its an issue.

Also, you can try to manually set DNS on the network adapter to a different one to see if its resolving issues. If you look at the command "ipconfig /all" what is the DNS servers there? If its not 8.8.8.8 you can set that as a primary and secondary you could use 9.9.9.9 if you wish to temporarily test this. Once you are done testing and you have more info you can set it back to what it was previously or DHCP to let it go back to what it was.

Comcast has been having back-end route issues for the last two months for example, since they tried to implement slow lanes but it went south, so upstream DNS has been wonky for them for a little bit. I don't know what your provider is, but it could be something like that and you would want to test other DNS servers.

Last test idea for now: Open two command prompts, and do the following on each. "Ping 8.8.8.8 -t"  on one and on the other do "Ping Google.com -t". And leave them open while you use the device. This is creating a persistent ping to google through IP and through Name Resolution. This is very minimal traffic and shouldn't impact anything really so you can leave it up for a while. Once your computer starts to have issues again rush back to these two boxes and see if either one stops getting replies. If both, then its network, if Google breaks but 8.8.8.8 keeps going, its DNS.

@James:
Won't ping google.com -t do the name resolution just once (at the start) and then just ping the IP address after that?  That is, if DNS is working when the command is issued and then later DNS is down, I'd presume that the ping continues.

Your basic idea is sound.  Ping by IP and ping by name and see if IP works and name does not.  If my assumption is correct, he'd need to re-run ping google.com when the connection is not working.


@xchiazyx
I'd add one other test to those mentioned above.  Run ipconfig and note your Default Gateway (192.168.0.1 is common, but so are others).  Ping that IP address when the system is working and note that you get 4 good responses.  When you have lost connectivity, run the ping on the gateway again.

The tests that have been recommended are trying to identify the lower-level "break" in the system.  More specifically, is the problem in getting to your router or getting to your ISP?  Is the problem just with name resolution?

@CompProbSolv   No, that wouldn't matter. Google DNS pinging and Google.com pinging the web server will return two different addresses. So running them both at the same time or one at a time wouldn't make a difference.

Hi All,

I have set my DNS to 8.8.8.8 and secondary 9.9.9.9 and the issue still unable to resolve. Today once I started my pc have network but can't use at all, restart resolve then later 2 hours later the same thing. Once I am unable to use the network I tried Ping 8.8.8.8 -t and Ping Google.com -t and it's getting reply all the way, I am able to ping my default gateway as well.

Check my windows update history, does it cause by the security or cumulative update? No chance is my hardware issue? From my event viewer, I have this common issue "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
 and APPID
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."

But this error has been a long time already, appreciate if any expert can advise me on.

Thanks!

are the drivers up to date? if not update them

Yes, it's up to date already. Never have this issue before, new desktop only 1year build with high spec though.

maybe best to use your warranty, and have it replaced

Did hardware test all passed, I don't think Asus will replace for this reason. 

Do you have access to a USB to Ethernet or WiFi adapter to use and see if that one works to test if its is hardware issue?

Hi James,

I don't have one, I system restore back before the windows update and see if this resolve because before the update it's fine, I'll monitor for 2 days. Mine is stayed at the private network and didn't switch to public. But do you guys think will those update caused it?

Thanks!

 

They could cause driver instability, but not in general would it break it. I know you said you updated drivers on the Network Adapter but I would fully delete the driver and reinstall clean.

Make sure you have a downloaded version or two of the driver before you delete. Look up the part number or manufacturer for the Motherboard or Network card and get the latest and one previously and have it on desktop before deleting.

Go to Device manager, find your Network adapter. In there right click and uninstall device. When done, reinstall with one o your driver versions then reboot. Test, if nothing, then repeat and go to a previous version, then reboot and test.

>>   I don't think Asus will replace for this reason.   <<  why not?  i f any part fails, the whole board needs a replacement
what mobo is this?

you can also tes twhith a separate lan card