Avast WEBforum

Business Products => Avast Business => Topic started by: Lt Lemming on March 21, 2019, 06:42:22 AM

Title: Documentation Lacking for Remote Deployment
Post by: Lt Lemming on March 21, 2019, 06:42:22 AM

I've been scouring the documentation but am unable to find an answer to this one.

What interface/protocol does Avast use to query AD for the remote deployment?

Every time I try to do it on our network I just get "The Master Agent can not connect to Active Directory" but it doesn't tell me why it's failing.

Is there a log I can check to see where the error is?

Title: Re: Documentation Lacking for Remote Deployment
Post by: andrey.01015 on March 21, 2019, 04:07:25 PM

ActiveDirectory by Microsoft or Samba server?

Title: Re: Documentation Lacking for Remote Deployment
Post by: Lt Lemming on March 22, 2019, 03:34:09 AM

Both.

Title: Re: Documentation Lacking for Remote Deployment
Post by: Gombos on April 18, 2019, 08:42:44 AM

Same problem here.... Do you have any solution yet?

Title: Re: Documentation Lacking for Remote Deployment
Post by: .: Mac :. on April 24, 2019, 12:49:05 PM

Can you provide more detail about your network? Are the console and the AD Controller on the same subnet? Is there any intra-VLAN routing happening? Often times there is an issue with firewalls or ACLs blocking access between the two.

Title: Re: Documentation Lacking for Remote Deployment
Post by: Lt Lemming on May 28, 2019, 05:08:43 AM

Quote from: .: Mac :. on April 24, 2019, 12:49:05 PM

Can you provide more detail about your network?

I'd rather not post details about our network in a public forum.

Quote from: .: Mac :. on April 24, 2019, 12:49:05 PM

Are the console and the AD Controller on the same subnet?

Yes, but this is still the sort of information that should be included in the documents surrounding this.

Quote from: .: Mac :. on April 24, 2019, 12:49:05 PM

Is there any intra-VLAN routing happening?

Lots, the domain controller and the master agent and clients all share one vlan though.

Quote from: .: Mac :. on April 24, 2019, 12:49:05 PM

Often times there is an issue with firewalls or ACLs blocking access between the two.

Great! What ports? what protocols? in which directions?

NONE of this is documented besides one mention of port 7074 on the console page where it tries to connect to the domain controller.

In short, the documentation is as I've said. Severely lacking.

Title: Re: Documentation Lacking for Remote Deployment
Post by: mickey.b on June 11, 2019, 05:21:44 PM

Quote from: Lt Lemming on March 21, 2019, 06:42:22 AM

Every time I try to do it on our network I just get "The Master Agent can not connect to Active Directory" but it doesn't tell me why it's failing.

If you haven't already, please submit a case at https://www.avast.com/business-support-contact (https://www.avast.com/business-support-contact)

Most likely, we will need to collect debug logs. Please also see How To Submit Avast Business Log Files (https://kb.support.business.avast.com/GetPublicArticle?title=Using-The-Avast-Support-Tool) for more information.