Blocking domain controller?

system · 2017-03-30T22:54:10.000Z

So I just swapped out a domain controller, rejoined machines to the domain but following re-joining, randomly Avast starts blocking connections from the workstations to the domain controller which also contains the shares.
It seems to be the firewall blocking the connections as when we disabled the firewall things seemed to get better but I am not seeing a way to add a exception for the local network via the web manager and I don’t see in the interface the logs where it tells why it’s blocking connections.
I looked through the text logs, some accessible, some not and I didn’t see anything in there either that says why the connections to the domain controller are being blocked.
Any help would be appreciated.

SMPlante · 2017-04-03T02:06:51.000Z

Hi Visseroth,

You can find Avast Network Shield Statistic in "Security Tab ; Icon “Network Sheild”

https://forum.avast.com/index.php?action=dlattach;topic=199865.0;attach=190892;image

I think you will find what you are looking for in there:

https://forum.avast.com/index.php?action=dlattach;topic=199865.0;attach=190894;imagee

If you moved your machine from an AD (Active Directory) to a new one, you probably have old GPO still in the Workstation.
You need to load the new GPO, from AD, when the machine is connected to the good network (Admin CMD dos command : gpupdate /force
Make sure your machine Network connexion is showing the same name then your AD DNS system.

https://forum.avast.com/index.php?action=dlattach;topic=199865.0;attach=190898;image

system · 2017-04-06T22:30:01.000Z

Thank you ;D

Any idea how I can set new rules via the web management for the firewall?

SMPlante · 2017-04-08T02:31:35.000Z

Are we talking about “New rules” for Avast or Active Directory GPO ?

Two Completly different things / tasks …

If I’m refering to your original text (request), you say that you moved some PC from a AD Domain to a new one.

As an IT consultant, every time I do that on a PC with Windows’s Operating System, I clean lot of things, before joining the new AD Domain.

Otherwise, you will end up with many problems.

Here a summary of the task I do:

[ol]- Activate and give a new password (one I will remember for step 3 & 7) to the Local Administrator account

Quit the AD Domain and just put the PC on his own Workgroup
Restart the PC and log using the Local Administrator account
Rename all OLD AD Domain users folder
Delete all Local Adminitrators Group user entry that was related with the Old AD Domain (S1xxxxxxx account)
Delete all ProfileList Registry Key related with Old AD Domain
Restart the PC and log again using the Local Administrator account
Join the new domain and make sure you add the administrator, from the new AD Domain in the local (PC) Administrator group
Restart the PC and Log as the New AD Domain administrator
At this point, if you still see the Old share (from the old AD Domain) just disconnect them
Log Off and Log In again
If your AD Domain GPO are correctly set (for folder share) you should see them and have normal access[/ol]

I have applyied these steps to many Windows PC, I have moved from a domain to a new one, and I never had any problem related with avast not allowing me to access the share drive after the AD Domain change.

Hope it will help you

Announcements