Laplacian

I denied all communication on that port in ESET firewall configuration, and the scan still shows it is open. My Windows firewall machine on the other hand shows no ports open or they are blocked, so I am pretty worried that the ESET firewall is providing that information for the scanner. And I looked that there was legitimate communication on that port, which I am not really sure what the communication is needed for.

Also I forgot to mention that my network is either way a LTE/4G network and not a fiber

I now scanned the external IP from LTE/4G device and it didn't show no ports or even any host up. Then I also scanned my LAN again using NMAP and the device inside my network seems to have the port 53 open indeed, but it is TCPwrapped. I do not know why does show that one port. But I trust ESET so its all good thanks for the help

I scanned the machine inside my LAN with another LAN device. As for the public IP, I will try to scan outside my LAN. I will post when I have done that thanks.

I scanned with phone where I have paid app called Net Analyzer

Hi, So I scanned all my machines on my network, and it showed that my computer has the port 53 DNS domain port open? Is this normal, as I think that I haven't seen that being open before if I remember correctly. And even if it is open, shouldn't ESET prevent showing that it is open?

@MarcosThank you. I excluded registry from the scan and it was able to complete scan.

Hi, My ESET full scans always get stuck on this one file accwiz.dll even though nothing is using the file. I am not able to perform scheduled full scans due to this file, as I need the DLL for office products and can't delete it. I have inspected the certificates, and the object/hex dump of this file and it is a legitimate office DLL. Is it not possible to set file exceptions on ESET? Longest I waited it for to scan this file was 3 days, so it is stuck on it really.