Windows 10: Ping OK but HTTP/HTTPS (mostly) failing

For what it is worth - I've just rolled back to the cumulative update KB3206632 installed 14/12/2016 and (currently) have full access to the web (indeed I am typing this on my desktop PC).

I'm not sure what to do now. Clearly I don't want any further fixpacks installed until the next one!

 

For those who have issues with the December cumulative updates who were working OK beforehand, a rollback to "the last known good working update" might be a temporary solution. If you have something like that available to you dated early December (before the 10th) that might do the trick. I'm very, very sorry for your trouble: networking is like a utility for computing. It really should "just work." I'm appalled at your troubles and woes, not just for your sake but because it reflects a situation much too common among Windows 10 users. Keep at it though, I'm sure we can help you get it sorted.
--Ed--

 

Thanks, Ed. Fingers crossed KB3206632 will remain stable for now. Given how it "just went wrong whilst I was working" initially I fear it may do it again - at least I can either roll-back or turn off updates for a while. Not ideal but it's a workaround.

I'll open a fresh thread for the NAS access or this one will get very messy.
Mark

 

Again, very sorry for your troubles. Glad you found a workable installation configuration. Makes me feel like witch doctor sometimes, trying to get Win10 working properly. There's too much art (and luck) involved, and not enough science. Sigh.
--Ed--

 

aaaaaaaargh.

On this thread NAS not visible to my PCs any more Sys 53 path not found I changed to untick IP6 on the adapter, re-booted, and the problem came back. I've gone and ticked IP6 again on the adapter but despite a hard boot it is still erroring.

I can wander aimlessly around Facebook but no other URL is responding to me.

That's it. I'm done with PCs for the night! *Sad

 

You may try this troubleshooting steps:

- write down and then disable performance settings of your network adapter (checksum offloads, large send offloads, jumbo packets etc), this may improve reliability
- at command prompt type "ipconfig /all" and check results
- find some web sites which you cannot reach
- try the command "nslookup <web_site>"; can website name be translated to ip address?
- at command prompt run "tracert <web_site>" and save all traversed ip addresses; can you reach the target?
- for each ip address run "ping -n 20 -l 1400 -f <ip_address>", this should test real size of packets; are all the responses correct?
- use firefox (not IE/Edge) for opening web site; which error message you get if any?
- repeat for more web sites; are the problems related to ssl/tls?

Furthermore, if you can please test using different network adapters (ethernet, wifi). And last but not least, you may check your event logs for errors related to ssl/tls, tcpip and other network components. Please let us know the results.

 

Good morning Valihrach, I took the day off yesterday rather than destroy my PC with a hammer ;0)

The above - I've no idea how I am meant to adjust those (or what "etc" may mean). Whilst I did used to do technical stuff that was 20+ years ago so my knowledge of settings in Win10 is limited.

Ipconfig /all - results look as expected to me.
NSLOOKUP works just fine for any site. bbc.co.uk for example resolves so 212.58.246.78 and tracert will reach it just fine.
The ping that you suggest throws up no errors.
I use firefox as my default and get NO errors. The thing just sits there spinning.
I've tried for quite a few websites and can not get any sense of problems being restricted to a particular type. As I said above I've previously managed to "reach" an https connection and then it has bombed later. Most of the time I can reach nothing at all.

I've not got the ability to try other adapters than wifi. I use wifi because the desktop machine is some way from the router (in a different part of the house) so moving it to try a cabled connection isn't going to happen.

As for event logs - I'm not suer what I am looking for. I see a number of errors this morning from DistributedCom most of which are that one server or another didn't register with DCOM within the required timeout.

Does that help?

 

As the actual network infrastructure appears to be operating correctly

A few Questions are maybe relevant here

Have you tried disabling all add-ons in Firefox?
Have you tried using an alternative browser to Firefox?
What Security software are you running?
Are you running a 3rd Party (non Microsoft) Firewall?

If you can answer the above it could help get to the bottom of things *Smile

 

Barman58,

I've tried Firefox, Edge and Chrome. Whilst there may be add-ons in Firefox I've added nothing to Edge or Chrome.
I can't FTP either.
I'm running AVG Internet Security (and yup, I've tried disabling it all and no change).

 

I should also mention (I don't think I've said before) - I can't get to Outlook either. Essentially, anything web based other than pinging from the command line is stuck.

 

I've known AVG to cause issues even when disabled. maybe a full removal for testing is called for

AVG Remover 2012 Download

The symptoms you are showing suggest the presence of an over zealous firewall or AV closing Ports that are needed for web Access (80), FTP (21), and email (993? but others are used), Ping is allowed as it does not use the ports, (lower network layer)

 

Barman58, that was where I was heading myself. It's got to be a blocked port. I just didn't think AVG might be doing it when disabled. I'll try removing it completely and see what I get.

 

Interesting result, Barman58. Removing AVG Internet Security and I got full access to the web back - I knew I'd got it back before boot finished when I got a Dropbox notification pop up for a file that a friend had modified.

Now I'll try re-installing - if it breaks again I'll be over to AVG to ask them how to resolve their software conflict!

 

Thank you, by the way!!!

I couldn't see wood for trees. I knew the stack was being blocked higher up but wasn't seeing that AVG was only "partially" turned off.

Fingers crossed it will still work when I reinstall.

 

Keeping everything crossed for the rest of the day - but AVG is installed and I am typing this from my desktop PC. All seems working.

Now I'll see if I can see my NAS again!