Reboot. When avast tries to connect (to update itself), the firewall might ask you for permissions. whether the firewall reacts or not, wait 10 minutes after the reboot and review avast → maintenance → updates. Are avast definitions updated? Is the “Last update (attempt)” info just some minutes old? Was the update successful?
If the update was successful, you may try adding the specific IP address of the NAS in avast → settings → troubleshooting → redirect settings.
ady4um note that the OP has stated there using the windows firewall, there are no entries or any exclusions necessary for avast in the windows firewall unless outbound protection has been enabled.
Understood. My comment was more of “just in case”, “might”. I don’t have a crystal ball to know exactly what could happend in each and every case :). So I try to write as general as I can, while sometimes I go first for the most common and yet simple solutions.
Now we need to wait for feedback about the troubleshooting redirect settings, and if that is not good enough, then we’ll see.
Just for a test, please change web shield → expert settings → “well known browsers only”, save changes and test. If it doesn’t work, please return back the setting as it was before.
In theory, this has nothing to do, and you already said that disabling the shields completely doesn’t work either, but it is simply enough to test, so please do.
Besides the redirect settings and the firewall (whether hardware or software or both types) are the ones I can think about having some influence here. If those are not solving your problem, then someone else might have some other idea (in addition to a cleanup / removal of older versions and clean install anew).
I have the same problem since I installed Avast Security Premium. When I disable the Avast firewall all works fine like "\NASNAME". Enabling the firewall again blocks the path to the NAS