I am testing and learning how to work with the AVG Business ISE combined with the remote admin console. My local network is not on a domain controller, just a straight forward home LAN. For the purpose of testing I installed the AVG on 2 VMware VMs.
VM1 = Win7, AVG server + admin console + AVG locally installed VM2 = Win7 (waiting to get AVG installed)
On both VMs I have 1 user account "Joe". This account is an adminstrator account. The VMs are vissible in File explorer. In File Explorer from VM1 I can access VM2/users, and from VM2 I can access VM1/users.
I followed the installation guide, but what ever I am trying, the login fails. I also turned off both firewalls, but I still get the message "wrong username or password". On both VMs DCOM and RDP services are running. When the Windows firewall is activated, it seems to me that all settings are correct.
From the manual: 1.6.1. Ports to be allowed on stations RPC: Remote Procedure Call To be able to launch the AVG installation on the remote station, you need to allow the following ports in the firewall on the station – TCP and UDP port 135.
On VM2: Windows Firewall with advanced Security >> inbound rules: Remote Assistance DCOM-In port TCP 135 allowed for Domain + Private
From the manual: Distributed Component Object Model (DCOM) For proper functioning of WMI (Windows Management Instrumentation) used by the AVG Network Installer, you have to open the DCOM port. The DCOM port is TCP 135.
On VM2: I do believe this is ok, see the above.
From the manual: 1.6.2. Ports to be Allowed for Remote Administration Ports that need to be allowed for remote administration are listed below:
Communication on TCP port number 80 For downloading AVG updates from the internet to the AVG Admin Server UpdateProxy, it is necessary to permit outgoing communication for these components on TCP port 80.
On VM1: I see downloads are stored, so I guess that this is OK then.
TCP Port 4158 For basic communication between the AVG Admin Server and the AVG stations and the AVG Admin console, you need to allow TCP port 4158 (predefined by default). This port can be changed in the AVG Admin Server configuration and in the AVG User Interface on the station (via upper menu Options/Advanced Settings – Remote Administration).
TCP Port 6051 This port is used for direct messages from AVG Admin Server to the AVG Station. This port can be changed within the AVG User Interface on the station (via upper menu Options/ Advanced Settings – Remote Administration).
TCP Port 6054 This port is used for direct messages from the AVG Admin Server to the AVG Admin Console. This port is not configurable. AVG Admin Console tries to open this port automatically for listening, if the port is not available, it tries to open subsequent ports (6055, 6056, …) until it successfully finds an available one.
On VM1: In Windows firewall >> allowed programs ... I see that AVG has been added with all modules (Admin console, admin server, admin update assistant, diagnostics 2013, installer, network installer, remote administration, server deployment wizard, server monitor). Is there any thing else I need to change?
On VM2: I added and allowed incoming TCP traffic on ports 4158, 6051 and 6054.
What am I doing wrong here? Many thanks in advance.
This page is for Business Customers only please click here for home user support. I am a home user with the intention to learn how to use the SMB remote module. This new knowledge can be a valuable asset on my resume. So I am depending on the home user support group.
Basically the message means that the installer does not have permission to login to the machine. This FAQ should help in troubleshooting the issue.http://www.avg.com/gb-en/faq.num-5386
The installer uses WMI to install so WMI (Windows Management Instrumentation) must be allowed through any internal firewalls and it must be possible for the network installer to log in to the target machine using WMI.
AVG Guru
AVG Guru
AVG Guru
Thank you for your email.
Basically the message means that the installer does not have permission to login to the machine. This FAQ should help in troubleshooting the issue.http://www.avg.com/gb-en/faq.num-5386
The installer uses WMI to install so WMI (Windows Management Instrumentation) must be allowed through any internal firewalls and it must be possible for the network installer to log in to the target machine using WMI.
Best Regards,
David Phillips.
AVG Technical Support.