This post was really hard to understand. Also, why wasn’t his dns resolving the default test domain ok? Wouldn’t an easier (and more correct) fix have been to address that? That way any other people on his network wouldn’t have a problem, either.
Maybe it's a cheap (laborwise) and dirty solution if you don't want to muck about with networking too much. I set up my own subdomain for replacing msftconnecttest because I had similar troubles with Windows 10 showing not connected in task tray, but was actually connected. Maybe that's what he means by 'got flaky'?
That has happened to me as well. This was different. The system would go through connect/disconnect cycles and then disable the card etc.
I thought it was a driver issue because every search resulted in people claiming to have solved their problems using older drivers etc, but I had no real luck with that.
The true cause of the problem is still a mystery to me, but pointing the test to my own server gave me control over both ends and has worked fine for weeks now. Yes, it is trivial, but it is a much more preferable outcome than trying to figure out the real problem/solution using search results like this: https://www.google.com/search?q=7260+connection+problems
Try "7260 connection problems" under Duckduckgo and results are much less spammy.
> That way any other people on his network wouldn’t have a problem, either.
Given that he's setting DNS servers statically on his own clients and has working DNS resolution on the DHCP-provided DNS server(s), that shouldn't really be an issue for other people.