Client can't connect after upgrade to 1.1.132.15

So upgrading to the latest version (1.1.132.15) seems to have at least gotten the console and mirror running again. See http://forum.avast.com/index.php?topic=89585.0 for the original problem if it matters.

However, while client computers seem to be able to download updates from the mirror, most can apparently not “log in” to report their status. My own computer from which I run the avast SBC console (hence showing the connectivity is there) is not reporting its status. I even tried removing my computer from the console and letting it be rediscovered. That happened, but still no status report after restarting my computer. It did update the program and defs though… very strange.

So I tried removing and re-installing from the latest package on the server, but still can’t connect and now showing unlicensed because it can’t connect.

There is a firewall in between. It’s logging an allowed connect on port 25322, so it’s not being blocked by the firewall. But for some reason, it’s not connecting. Nothing shows in the service log on the server for the connection attempt either. Very strange…

Any ideas?

AvastNet.log on the client says this (in case it’s helpful):

12/05/2011, 14:19:07 avast! NetService identified as prom-6
12/05/2011, 14:19:37 Server didn’t respond in time! Trying to wait a little longer.
12/05/2011, 14:20:07 Server didn’t respond in time! Will Restart NetPump.

Never mind. Avast 1.1.132.15 changes the Windows firewall rule for port 25322 to “Local Subnet Only” which for me pretty well hoses it since 95% of the clients are not on the local subnet. Fixed the rule. Hopefully the next version won’t break it again…

Hi Brett,

Is it mean that the problem was solved by yourself?

Please changes the status with “Solved” if this cases has been solved.