Hi Joe,
I don't have any of these events on the old driver version (15.5.6.48) that I'm using. But on Saturday I had upgraded to the latest drivers (15.12.0.6) and had a really bad time - worse than normal. Absolutely would not connect after all the tricks. I now see in the event log several 5055s and 5007s. I will send you the saved events .evtx file in a private message. I believe that was a different kind of bug than the one I'm getting while on 15.5.6.48.
========
I have yet to confirm this, but while on 15.5.6.48, I'm pretty sure I can still access devices on my local network. Like, I think I can print to my Apple Airport-connected printer! But the other computers/devices don't seem to be affected at those times. And as I mentioned, I seem to experience this on other WiFi networks at different locations and different access point hardware. In those cases, I am also close to the access point so interference is not an issue. EDIT As Andrw0830 revealed, perhaps this is not to do with the locality of my networked printer, but perhaps due to my accessing it via IP address and thus no DNS. No idea how the hardware driver would interfere with a layer-specific activity like that but I thought that was a better explanation. I cannot replicate this pinging by IP to public nor local addresses.
Thanks!
