« previous next »
Pages: [1]   Go Down

Author Topic: AEA Firewall ports.  (Read 8237 times)

0 Members and 1 Guest are viewing this topic.

Offline Infratech Solutions

  • Avast Reseller
  • Super Poster
  • *
  • Posts: 2399
  • Mayorista e integrador de Avast en España
    • Ciberseguridad Avast para empresas y MSPs en España.
AEA Firewall ports.
« on: October 17, 2012, 04:52:12 PM »
In a new AEA installation, the default firewall rules configurated automaticly are:

avast! ADNM Agent access: TCP 16111
avast! ADNM AMS discovery: UDP 6000
avast! ADNM Cisco NAC access: TCP 16103
avast! ADNM Console access: TCP 16102
avast! ADNM Mirror access: TCP 5033

But, you need:

AEA Mirror: TCP 16135
AEA Client Communication Port: TCP 16136
AEA Client Communication Port Puhs: TCP 16139

And you have to configure manually in the Windows Firewall.

Why we have the old ADNM rules instead new AEA?
Logged

MarKvi

  • Guest
Re: AEA Firewall ports.
« Reply #1 on: October 22, 2012, 08:51:05 AM »
Hi

I'm already in touch with DEV team.. I will let you know ASAP!
Logged

finalbowser

  • Guest
Re: AEA Firewall ports.
« Reply #2 on: November 14, 2012, 06:00:36 PM »
I too have wondered this many times.  I've deployed AEA to multiple servers now and find the task of manually configuring the firewall to be quite tedious.  I sure would be nice to see this fixed.
Logged

lparece

  • Guest
Re: AEA Firewall ports.
« Reply #3 on: November 15, 2012, 03:12:23 PM »
Thanks for this info, Edj. I'm sure you've saved me hours of digging to figure out what is wrong with my equipment only to learn it is an oversight on the Dev side.
 :D

Quote from: Edj on October 17, 2012, 04:52:12 PM
In a new AEA installation, the default firewall rules configurated automaticly are:

avast! ADNM Agent access: TCP 16111
avast! ADNM AMS discovery: UDP 6000
avast! ADNM Cisco NAC access: TCP 16103
avast! ADNM Console access: TCP 16102
avast! ADNM Mirror access: TCP 5033

But, you need:

AEA Mirror: TCP 16135
AEA Client Communication Port: TCP 16136
AEA Client Communication Port Puhs: TCP 16139

And you have to configure manually in the Windows Firewall.

Why we have the old ADNM rules instead new AEA?
Logged

wpn

  • Guest
Re: AEA Firewall ports.
« Reply #4 on: November 26, 2012, 04:08:30 PM »
was getting pissed of why my client didnt work when i changed server
then i remembered the firewall and this is the solution :) thnx

MAJOR issue, i expect this issue to be solved in the next release
Logged

joealbergo

  • Guest
Re: AEA Firewall ports.
« Reply #5 on: December 03, 2012, 09:41:10 PM »
I am trying to understand what does AEA stand for?
please?
thank you !
Logged

Dewg

  • Guest
Re: AEA Firewall ports.
« Reply #6 on: December 04, 2012, 12:25:26 AM »
Avast Enterprise Administration (AEA)

BTW - question for you guys... if I close port 16135 on the AEA server, will the clients be forced out to the internet for definition updates and program updates?  If so, is there a negative for doing that?  Several of my offices have slow WAN links, but fast internet access.  They can see the AEA all the time, but I want to force updates to the Internet.  Is there anything else that port 16135 does beside supplying VPS and program updates to the clients?
Logged

joealbergo

  • Guest
Re: AEA Firewall ports.
« Reply #7 on: December 04, 2012, 02:25:41 AM »
Dewg, thank you brother !


Logged

wpn

  • Guest
Re: AEA Firewall ports.
« Reply #8 on: December 11, 2012, 11:57:35 AM »
logically this would cause the client to go for internet download.
Tho it can only be confirmed by testing it out :)

Its not possible for a group tho to specifically tell it to check on internet. I smell an RFC :)
Logged
Pages: [1]   Go Up
« previous next »