Windows 10: The device or resource www.microsoft.com is not set up to accept connections on port "The...

I am getting this error from every microsoft application when I try and sign in. My internet works fine as I am able to browse no problem. I believe this error happened after the last security update. I tried to uninstall it but it kept failing the uninstall. Not sure what to do but I can't sync at all.

:)

 

The device or resource (127.0.0.1) is not set up to accept connections

Hi

I keep getting disconnected from the internet and every time i run the network troubleshooter I get the same error: The device or resource (127.0.0.1) is not set up to accept connections on port "8446".

Can anyone help pls?

PS. I have included a screenshot in the attachments

 

The device or resource is not set up to accept connections on port "The World Wide Web service (HTTP)".

Hi,

One of my website is hosted on IIS which is working fine few days back. Suddenly, it started throwing the error 'ERR_CONNECTION_REFUSED'. After troubleshooting, got the below error message.
I have tried windows socket reset but no luck at all. Please suggest me the best troubleshooting process for this problem

The device or resource (sitecore82) is not set up to accept connections on port "The World Wide Web service (HTTP)".

Thanks,

Manideep

 

The device or resource (127.0.0.1) is not set up to accept connections

Two things:
1. Port 8446 is usually associated with the EMC2 Legato Backup system (unlikely in you case) or with iTunes (more likely)



2. Address 127.0.0.1 is the so-called "loopback address" used in IP testing mostly to ensure that the local protocol stack is working. It's very weird that a network resource would try to access a port via loopback.
From what I read online this could be indicative of several things:
(a) your hosts file may have been rewritten by malware, so you'll want to run Malwarebytes ADware or Trend Micro HouseCall to see if anything weird or unwanted turns up
(b) your ISP may be having intermittent difficulties. If that's the case, the problem should go away on its own
(c) if something in your IP stack has gotten corrupted, you could possibly find it by running sfc /scannow and then also dism /online /cleanup-image /checkhealth.
Try these suggestions in order, and let us know what you find out.
HTH,
--Ed--