No connectivity between clients & SOA after successful deployment

system · June 21, 2012, 2:44pm

I just recently installed SOA on a Win2k8 R2 server. SOA detected all the clients and I was able to make successful deployments to a handful of Win7 Pro test machines. However, all of the clients are grey and showing no connectivity. The SOA server and all the clients are on the same subnet and domain. The clients are controlled by a GPO that allows UDP/TCP 25322 through the Windows firewall. Windows firewall has been turned off on the server. The clients can ping the SOA server and the server can ping the clients. What am I missing?

Zip file generated by the SOA’s troubleshooting section: https://docs.google.com/open?id=0B1V7Mr9BYAxVQjFMNE9QdjBtWmM

spi · June 21, 2012, 6:11pm

check the administration service is run or not, after install please restart the client.

you can upload the troubleshooting file to sharing server (mediafire, uploader, etc…) and post the link here.

system · June 21, 2012, 6:55pm

I’ve edited my first post with a link to the zip file.

What is the name of the service I’m looking for? On the clients, I have avast! Antivirus and I also have avast! Net Client Service. On the server, I have avast! Administration Console, avast! Administration Console Monitor and avast! Administration Console Website Host. All are running. The server & all the clients have been rebooted.

system · June 21, 2012, 7:28pm

On one of the clients go to settings in the upper right corner of the avast gui, then go to troubleshooting, then avast! administration console and check what happens if you change from the fqdn to the ip address of the server.

Also, I think you just need port 25322 TCP (not udp)… I think.

system · June 21, 2012, 7:38pm

Oddly enough, there was NOTHING listed in that box! I dropped the FQDN in there and restarted the avast! Antivirus service. After that, I had connectivity and I was able to see the PC turn green in SOA. So, now that we know what the issue is, how do I fix it on a grand scale? I deployed the clients from SOA so that setting should’ve been pushed out with the deployment.

system · June 21, 2012, 9:05pm

One would think.

I actually hate the push fucitonality - it assumes too much about the availability of the machines and doesn’t have an easy way to make sure the old AV was removed first, so I just built a custom install package and launched a script with elevated privladges using other tools (paid tools) that takes care of everything the way I need it to during the user login script… In the console, under admin → settings → setup there is a link to download the .exe installer which I saved to a network location and used with success to deploy wtih all settings needed to connect to the console… If you have a method of running as admin in your environment, you can just use that.

system · June 22, 2012, 10:23am

nannunannu post:6:

HomeNet post:5:

I deployed the clients from SOA so that setting should’ve been pushed out with the deployment.

One would think.

I actually hate the push fucitonality - it assumes too much about the availability of the machines and doesn’t have an easy way to make sure the old AV was removed first, so I just built a custom install package and launched a script with elevated privladges using other tools (paid tools) that takes care of everything the way I need it to during the user login script… In the console, under admin → settings → setup there is a link to download the .exe installer which I saved to a network location and used with success to deploy wtih all settings needed to connect to the console… If you have a method of running as admin in your environment, you can just use that.

Ahhh, weak! I was hoping I could just tweak an INI or something and redeploy. I’ll look into what you speak of but if anyone knows how to fix the bug, let me know.

system · June 22, 2012, 10:46am

My download doesn’t work. In fact, I think the directory in which is resides doesn’t even have the file to download. It’s as if it was never generated.

system · June 22, 2012, 10:47am

The only reason I added both to my GPO is because when I deployed the client package, the installer made both changes to my Windows firewall config. I merely mimicked what the installer did.

lukas.hasik · June 22, 2012, 11:15am

HomeNet - how did you installed (deployed) the clients to your network? Did you use the “Unattended Deployment” job or the avast_managed.exe for email deployment?

system · June 22, 2012, 11:19am

I did the unattended install.

Avosec-UK · June 22, 2012, 11:30am

It would be a lot easier if we can see the avastNet.log located in:
“C:\ProgramData\AVAST Software\Avast\log” or “C:\Documents and Settings\All Users\Application Data\AVAST Software\Avast\log”

system · June 22, 2012, 11:36am

That path doesn’t exist on my server. The best I have is C:\ProgramData\AVAST Software\Administration Console\Logs and it has the following logs:

aswRInst.log
avast.sbc.manager_120622065224.log
avast.sbc.service.installer_120622065235.log
Avast.Sbc.Service_120622065328.log
avast.sbc.websitehost.installer_120622065322.log
avast.sbc.websitehost_120622065324.log
mirror.log
status.txt

Avosec-UK · June 22, 2012, 11:37am

Sorry I needed to clarify: you should look for this file on the client machines.

system · June 22, 2012, 11:52am


06/21/2012, 15:33:57    avast! NetService identified as prom-6
06/21/2012, 15:33:57    LoginRequest in Reconnected callback
06/21/2012, 15:33:58    LoginResponse arrived (result = TRUE)! {F9017821-35C1-4B9E-8130-ABABA47C67FE}
06/21/2012, 15:33:58    ScheduleBootTimeScan failed with error code = 1168
06/21/2012, 15:35:00    ScheduleBootTimeScan failed with error code = 1168
06/21/2012, 15:38:48    LoginRequest in Reconnected callback
06/21/2012, 15:38:49    LoginResponse arrived (result = TRUE)! {F9017821-35C1-4B9E-8130-ABABA47C67FE}
06/21/2012, 15:38:49    ScheduleBootTimeScan failed with error code = 1168
06/21/2012, 15:39:06    LoginRequest in Reconnected callback
06/21/2012, 15:39:06    LoginResponse arrived (result = TRUE)! {F9017821-35C1-4B9E-8130-ABABA47C67FE}
06/21/2012, 15:39:07    ScheduleBootTimeScan failed with error code = 1168
06/22/2012, 04:02:09    ScheduleBootTimeScan failed with error code = 1168
06/22/2012, 05:34:25    ScheduleBootTimeScan failed with error code = 1168
06/22/2012, 06:16:21    ScheduleBootTimeScan failed with error code = 1168
06/22/2012, 06:39:20    LoginRequest in Reconnected callback

system · June 22, 2012, 12:14pm

I have exactly the same problem as mentioned. My avastNet.log also looks the same.
I also used the ‘unattended deployment’ and tested it on Windows 7 and Windows Vista.
Both are encountering the same problem.

Avosec-UK · June 22, 2012, 12:17pm

Do you see any entries in the avast! Administration Console > ADMIN > Computer login audit trail?

system · June 22, 2012, 12:20pm

Some of my clients were not connecting to the console - nannunannu comment to change the “fqdn to the ip address of the server” worked. However, some machines connected fine using the FQDN and some needed IP. Is this bug or suggesting that my DNS has gone wrong somewhere?

system · June 22, 2012, 12:29pm

Here’s something…

“%programdata%\AVAST Software\Avast\avast5.ini”

After doing my little aforementioned trick, where I deploy the client software, change the settings in the GUI so it actually points to the server and then restart the service, I noticed my avast5.ini is different than others across the network. My file has the server’s FQDN whereas the other PC’s file does not. There has to be an issue with the deployment package…

My file:

[Common]
PropertyCommunity=1
SBCServerName=h1p-asoac1.homenet.local
SBCServerPort=25322

The other file:

[Common]
PropertyCommunity=0
SBCServerName=
SBCServerPort=25322

system · June 22, 2012, 12:31pm

I only see entries from the few PCs that I’ve done my little setting change in the GUI for. Other than that, nothing else seems to be checking in.

No connectivity between clients & SOA after successful deployment

Announcements