I had this problem for a while and I thought there was just a software glitch when it updated to Windows 10.
My Brother MFC-J625DW WiFi printer would not work in WiFi mode in my home network so for a long time I was using my USB cable. PS/Bonus Q: Does anyone know how much snooping etc. So I'm left to conclude that PeerBlock is somehow getting in its way, in some other way that is not packet blocking. But anyway, when I do the repair, having white-listed everything that looks like it might be infrastructure, I get nothing in the logs, but the Window's automatic repair step still fails. I don't know if those are secret handshakes. The new list I used, blocks much more than the old ones. Except that there is nothing in the PeerBlock log suggesting that the repair process was blocked by PeerBlock. In which case, it will not repair, unless PeerBlock is disabled. To repair it, the right-click, troubleshoot option must be used. When I "wake up" the computer, on Windows, the Internet connection is said to be severed. I recently enabled updates, and aside from the I-blocklist issue, I seem to have problem: Was wondering if anybody here observed similar behaviours from their OSes and what to expect, or if I should maybe just let it connect.
#Peerblock windows 10 startup upgrade#
Now, although it could be something related to the windows 10 upgrade fuss, I find rather strange and very aggressive on ms part to try establishing a connection in that way, especially if encrypted. In regards to the process opening the connection, I tried Process Monitor to observe which one is, but could not see anything peculiar - I'm kinda sure though that it's a windows component (btw, I have w7 64bit).
I also read that firewalls don't block outgoing traffic to remote 443 ports, so I forced my comodo pw to block the traffic to said ip range / port, just in case. Also kinda alarming (at least to me, I'm not very versed in networks), the remote port is always 443, which from what I gather is the one used for encrypted TCP traffic. What's strange, is that whichever process (more on that following) tries to connect said server, starts trying from local port 1052 (as soon as I boot the OS), and then proceeds to try the connection over every single following port, until I log out of the computer. Pb did not detect much activity initially, but then it started blocking an outgoing TCP connection, to a server with IP 13.88.144.248.Īlthough the pb interface reports the ip belonging to a "Xerox corporation", a whois search actually revealed that the ip actually pertains to Microsoft. I've been using peerblocker for a couple of months, and since last week I observed something strange going on.
0 kommentar(er)
