F
FrancisMonteiro
I come to you to report that many forums and communities on the Web have been encountering connections with varied IP addresses, originating from our desktop PCS (including notebooks) with Windows 10 installed, and they're linked by "netstat -abn" to the system's utilities, or apps, such as svchost, lsass.exe, ismagent.
Please heed that many different IP addresses are used everytime, even during one single session of logon, with a continuous use of the same protocol TCP or UDP port 443. It does seem that Microsoft Azure is put into use for whatever these software application perform, but we in the several communities just can't fathom why and what. Here's what would change it all and help us allow such connections with peace of mind: are all connections to and from Microsoft Azure using port 443 licensed services within Windows 10? And why is it that many IPs make use of the same port, and by different executables that Windows actually has?
Among many users in the community, no member actually wields exact information to clarify, so I thought up of asking Microsoft. Information shared on websites, forums and communities point to a diagnosis of suspicious binaries and a suspicious connection in each case. Could we clarify some technical opinions as they're provided here, so we can start ruling out the diagnosis of malware and trojans with port 443? (some users and forum members claim "https - that is, services in 443 mostly often" is one way to circumvent security screening, so the reports in these claims are driven towards malware and whatnot) I wish we knew what this all is ... we surefire become wary of online threats and we strive to maintain the Operating System.
If need be, let us know also on the official Microsoft forums and knowledge base sites, because search results do not suffice with the appropriate authoritative answers. And we apologize if this inquiry turns out to be needles with the May Updates. People seem to not truly figure out why IPs and ports are so recurrent links even without network applications running, pretty much like none, and we indeed find out many either in the background or within the assortment of Windows' own executables.
Yours thankful.
Continue reading...
Please heed that many different IP addresses are used everytime, even during one single session of logon, with a continuous use of the same protocol TCP or UDP port 443. It does seem that Microsoft Azure is put into use for whatever these software application perform, but we in the several communities just can't fathom why and what. Here's what would change it all and help us allow such connections with peace of mind: are all connections to and from Microsoft Azure using port 443 licensed services within Windows 10? And why is it that many IPs make use of the same port, and by different executables that Windows actually has?
Among many users in the community, no member actually wields exact information to clarify, so I thought up of asking Microsoft. Information shared on websites, forums and communities point to a diagnosis of suspicious binaries and a suspicious connection in each case. Could we clarify some technical opinions as they're provided here, so we can start ruling out the diagnosis of malware and trojans with port 443? (some users and forum members claim "https - that is, services in 443 mostly often" is one way to circumvent security screening, so the reports in these claims are driven towards malware and whatnot) I wish we knew what this all is ... we surefire become wary of online threats and we strive to maintain the Operating System.
If need be, let us know also on the official Microsoft forums and knowledge base sites, because search results do not suffice with the appropriate authoritative answers. And we apologize if this inquiry turns out to be needles with the May Updates. People seem to not truly figure out why IPs and ports are so recurrent links even without network applications running, pretty much like none, and we indeed find out many either in the background or within the assortment of Windows' own executables.
Yours thankful.
Continue reading...
