Updating problem on Port 5033

Avast Business Avast Distributed Network Manager
1

Hi,

I can’t find a solution to this problem so I hope you guys can give me a pointer in the right direction.

I have set up ADNM on our network with server ‘ntserver3’ (192.168.1.65) and about 15 PCs. remote deployment works Ok but the update isn’t working as either a scheduled task from the server or as a request from any of the PCs.

There is no firewall on the server (Windows Server 2003) and disabling the firewall on the PC makes no difference.

The error reported in the logs is Err:Cannot connect to 192.168.1.65:5033 (unknown:5033)

I can’t find a setting to change port 5033 though I see it’s in the mirror .ini file.

Should I change the .ini file (to what?) or is there a better option?

Thanks.

2

in the installation package there is a port that you can set. standard this is 16111.
edit the installation package of your clients and look for the page where you can see the servername, above the servername you can also see the port that is used for communications.

maybe this helps

3

Thanks but I have found this page and the communications port is already set to 16111.

4

are all your avast services running on the server?

5

They are all started or on a manual start

avast! Antivirus Started Automatic Local System
avast! iAVS4 Control Service Started Automatic Local System
avast! iAVS4 Mirror HTTP Server Started Automatic Local System
avast! Mail Scanner Manual Local System
avast! Management Server Started Automatic Local System
avast! NetAgent Started Automatic Local System
avast! Web Scanner Manual Local System

6

i noticed that my clients update over the same port as the port you experience problems with…

possible to post the complete log?

can you check the server in the eventviewer for any errors or warnings?

7

The updates are now working OK.

I have removed avast completely from the server and reinstalled it, which has cured the problem.

During my evaluation stage I did try out the server version and also the pro version on a PC and then realised that ADNM was the version I needed so put that on as well. Obviously (with hind sight) I should have gone straight for the ADNM version.

I was also a bit unsure about the SQL as we already had MSDE on the server and one of the programs using it broke when I first put on ADNM. But that is OK now, having fixed the other program and used the with MSDE package.

8

good to hear, the previous installations would have been useful to solve the problem faster :wink:

have fun with the product