hi,
I have installed avast business protection on a server in domain A. I need it to protect a few PCs in domain A and domain B.
I can push the install from the console to the PCs in domain B, but they do not check in. They keep saying they are in trial mode.
domain A pcs work fine.
I have also tried installing via the link provided by the admin console. It will install, but still will not “check in”.
In both instances I have verified the correct admin server is listed in the settings tab on the client. I have also tried replacing the name with the IP address.
Pinging resolves the correct name and the DNS settings appear to be correct as they match the other PCs.
Firewalls are disabled.
I feel as if I am missing somthing obvious.
Any ideas.
Hi, would you consider posting the steps you took to resolve your issue?
I am having a similar problem. I can resolve the name of my server so also don’t see a DNS problem. However, you stated DNS was not an issue in your first post but then said it was?
I have the Business Console running at our main office on the 192.168.16.0 IP subnet, we then have five other sites each on a different IP subnet. The sites are linked by an MPLS circuit, all systems at main office seem to work OK, all sites can talk to each other.
BC can see systems at the other offices via computer discovery job, the deployment works and the client installs fine but it installs in trial mode. I experience the same problem if I used the separate managed exe install.
I can ping and resolve the BC server from the clients by hostname and IP.
I have tried changing the BC server settings on the client from hostname to IP and then restarted the Avast net client service to force it to communicate, does not work.
I can browse the C$ share of one of the client PC’s in question
I spent two hours on the phone with tech support but they were stumped. They tried things such as putting an entry in hosts file for the server, which seemed irrelevant as I can resolve it just fine.
Firewalls are successfully passing traffic on port 25322, ruled out Windows firewall as an issue also.
If I need to provide anything else let me know, any ideas welcome. Thanks.
Usually the Business Protection is used only at one location and ADNM is used with multiple sites. Each site can have its own second level mirror to avoid using your bandwidth on the slower MPLS circuit for the updates.
With that said I believe that it should still work. I have a deployment with two locations running the SBC. Is it possible to have a common DNS server for all the sites? Where I have seen this work the remote sites connect back over a site to site VPN to access a file server or Domain Controller, not much different than your MPLS setup. Try using a Static DNS entry on one of your clients at the remote site that points to your DNS server at the main site. I am assuming this is likely what dferguson293 discovered in the Original post in this thread.
Can you see that client attempting to communicate on port 25322 on the machine running the SBC, just to make sure that the firewall is not blocking any of the communication?
I think I might have resolved it, or at least moved forward.
To be honest I feel like a bit of an idiot, whilst I checked that the relevant ports were in the Windows firewall on the SBC (I assume the avast install places these in here automatically) I did not actually switch off the firewall. After switching it off my clients started to connect successfully, however it does mean there is something odd with either Windows firewall not passing the traffic or an underlying issue in Avast?
If they did report in after the firewall was disabled I would point to the firewall. Instead of relying on Avast to make the exception in the firewall rule (Not even sure if it does?) perhaps you could create the exception to be push out using Group Policy?