Resource (www.microsoft.com) is not responding
brupala Posted messages 111111 Registration date Status Member Last intervention -
Hello,
Right now my modem is having connection/synchronization issues.
The Windows network diagnostic indicates:
It seems that the computer is well-configured, but the device or resource (www.microsoft.com) is not responding.
What does it mean "the microsoft.com resource is not responding"? Microsoft
I am looking for an answer to this question.
My ISP, OVH, sees nothing on their side and cannot answer this question.
Thank you.
Windows / Firefox 114.0
2 answers
Hello,
is that it?
https://www.microsoft.com/fr-fr
you can also try:
ping 23.52.120.96
and
ping 2a02:26f0:3100:19e::356
I suppose that Windows is testing the connection on this address.
If it doesn’t indicate the type of error, we can’t say more.
And there you go, there you go, there it is ....
But goodness, how annoying those line spacings are!!
Hello to you,
I had to be tenacious and combative!
This issue from 06/2023 ended up as a synchronization problem.
The ISP resolved it by forcing the historical operator to make a plot change in December!
Thank you!
Hello,
if that was the problem, you shouldn't have just that issue, but plenty of others as well.
By the way, whose DSLAM was it, because the sockets are just one port of the DSLAM?
And it's rare for OVH to collect from Orange if they have other options on the same NRA; when I was with them having these kinds of problems, I saw an Orange technician, then an SFR technician, then another Orange technician, and it still didn't work better, because the fault wasn't on the local loop, but on the collection.
Moreover, I then switched to Sosh with the same local loop, of course, but not the same DSLAM and not the same collection, and then I had no connectivity problems for a year before I finally switched to fiber.
Hello,
I believe it's a network connection error that is ultimately independent of microsoft.com; it just happens that at startup, there is either a Microsoft account or a service that takes priority, and it is the one at the forefront.
For the rest, we indeed cannot find the source of this error in its current state, defective network card or with inappropriate cable and/or drivers, Wifi configuration issue, DHCP or DNS problems, Proxy, unexpected interference from a "security" software, a VPN...
It's the diagnosis that indicates this, apparently.
I assume that before testing this URL, it starts by pinging the default gateway and querying the DNS, so it shouldn't be a connectivity problem; otherwise, it would say incorrect configuration or no DNS response.
Apparently, it can resolve www.microsoft.com, and I don't think it's hard-coded on the PC (like in the hosts file), especially since these are addresses from AKAMAI: