Hi,
The system blocked incoming connections requests from Comodo sDNS. Why Comodo sDNS trying to establish an incoming connection on my system?
see image
[attachment deleted by admin]
It seems to me they are ‘DNS answers’ that no local listener is waiting for.
What happens is the following, Windows service initiates a DNS query to Comodo servers and if the process that does that no longer listens but there is still incoming traffic for it Windows doesn’t know where to ‘deliver’ this packet to (the DNS app that started the query), therefore it ends up on the ‘WOS/Windows Operating System’ rule as blocked seemingly ‘incoming’ but instead it’s a reply.
Did you happen to put WOS on the Firewall policy and block traffic to it?
Hi Ronny,
Thanks for your explanation,
Did you happen to put WOS on the Firewall policy and block traffic to it?
No, but because there is a global rule “block all incoming connections” in the my firewall policy (image#1)
So according to this rule, firewall block it. Firewall does not block the total its traffic (image#2), only block incoming requests it.
[attachment deleted by admin]
Then it’s just the return traffic that can’t be delivered to the service that started the request.
Are you having issues with slow DNS resolving? and does anything speed up if you use your local DNS servers from ISP?
Are you having issues with slow DNS resolving? and does anything speed up if you use your local DNS servers from ISP?
NO,
Then it's just the return traffic that can't be delivered to the service that started the request.
I agree, probably due to long ping, Right?
If the time is to long for dns-client to resolve this issue could occur, but I can’t easily find the time-out for the socket on Windows.
What’s the ping time from the PC to the DNS servers?
What's the ping time from the PC to the DNS servers?