One Console managing clients on multiple subnets

[dynomyte]

I have a customer that has 3 sites that are all connected with Point-to-point T1 lines.  I can ping across all 3 sites.  I have the management console on a server 08 box at one site.  I set up a deployment on a few client at each site.  Deployment went fine, but now the remote clients are not talking to the server and they say they are in trial mode even though they all have the correct license info and admin console server address.  I have enabled file and printer sharing across the network and set up an exception for port 25322 in the GPO.  But still no luck.  Does anyone have any experience with this type of a set up?  Should i just run with 3 consoles?

Thanks!
 

[lukas.hasik]

1, what console? SOA or EA?
2, Can you ping the "server" ? from computer with client.
3, Can you see the client in the console?
4, any logs from client computer?

thank you
Lukas

[dynomyte]

1. avast administrative console version 1.1.132.15 (basic BP console)
2. yes I can ping the AV server with the clients
3.  I can see the computers in the network, but they all show up as unmanaged.
4.  Where would the client logs be?

[dynomyte]

In regards to 1,  I just got an email about updating my admin consoles.  Is there a big difference between the 2?  If I am already set up with the SQL database,  is one easier to use than the other?

[Asyn]

In regards to 1,  I just got an email about updating my admin consoles.  Is there a big difference between the 2?  If I am already set up with the SQL database,  is one easier to use than the other?

https://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=1291

[avast@@dvantage77.com]

Dear Dan,

if you have multiple subnets, then you will not use SOA, you will need the AEA.  I went through this with the SBC and this issue has not changed.

[dynomyte]

Dear Dan,

if you have multiple subnets, then you will not use SOA, you will need the AEA.  I went through this with the SBC and this issue has not changed.

SOA did pick up some of the test machines at all 3 sites.  I have about 60 users total.  Should I still go with AEA just to be safe?

[nannunannu]

I have the management console on a server 08 box at one site.  I set up a deployment on a few client at each site.  Deployment went fine, but now the remote clients are not talking to the server and they say they are in trial mode even though they all have the correct license info and admin console server address.

I had this issue with multiple ip segments when installing the bp console (seems to be fixed for me at least with default settings in the new eps soa console), but you may be experiencing it as well.  Check your firewall rules on the server that runs the management console.  Go into the windows firewall with advanced security - inbound rules - and make sure that the avast! administration console rule for port 25322 is open to the wan network segments (under the scope tab)...  you might find it limited to "local subnet"

Edit:  I guess I should mention that for me the segments are still lan traffic, so I don't view this as too much of an issue, works fine...  But I would be concerned about sending management traffic like that over slow - probably already saturated T1 links...

[spi]

@ Dan Kellerrecommended using the aea, If you need more advance feature.

[Bret Miller]

SOA will manage multiple subnets and even clients connecting over the internet. So if you have few enough client machines and it has the features you want, then there's no reason you can't use it.

[dynomyte]

Here is an update as to what is going on now.
I installed SOA and it picked up my test machines at all three sites.  I spent last week removing SEP.  This past weekend I deploy to everyone on the network.  After it got done I check and it only deployed to my other servers on the network.  Not to any of the workstations.  I check a few and I am able to ping any workstation.  I have changed a few firewall settings and am trying deployment again tonight.  if it still fails I am going to install the AEA and try using that.  The errors i was getting on deployment were either [2] or [53]. 

[.: Mac :.]

We had a situation with a client running SBC/SOA on a network with 2 locations/subnets. The solution was to check the windows firewall exception on the server running the Avast console, by default it was set as an exception only for clients on the local subnet. Changing the exception to include the 2nd subnet fixed the issue.

[Robokill]

We had a situation with a client running SBC/SOA on a network with 2 locations/subnets. The solution was to check the windows firewall exception on the server running the Avast console, by default it was set as an exception only for clients on the local subnet. Changing the exception to include the 2nd subnet fixed the issue.

Same here, we had a to set the firewall to go outside the domain to all network connections. Also fixen the DNS name did alot for us.

Hope it helps.

[dynomyte]

What all DNS stuff did you change?  I have all the firewall stuff set up.  I even have a GPO so that the workstation firewalls don't block Avast.  I am still having issues with it not deploying to all my workstations and its always returning the network location is not found error, but yet I can ping from the server to that station.

[Sistema]

Hi,
I'm installing and trying to multiple ip segments, but I can't deal with it... could someone help me? I use this system: https://www.2it-crm.lt/