Author Topic: No connectivity between clients & SOA after successful deployment  (Read 28943 times)

0 Members and 1 Guest are viewing this topic.

HomeNet

  • Guest
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
« Last Edit: June 21, 2012, 08:50:58 PM by HomeNet »

Offline spi

  • Poster
  • *
  • Posts: 514
  • 1st Services
Re: No connectivity between clients & SOA after successful deployment
« Reply #1 on: June 21, 2012, 08:11:42 PM »
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.
Windows 10 Pro 64-bit + avast Premium 11.1.2241
Network tools: Wireshark+CACE Pilot | Android Softphone + Grandstream UCM61xx | MI4i | Running Out of Time (1999)

HomeNet

  • Guest
Re: No connectivity between clients & SOA after successful deployment
« Reply #2 on: June 21, 2012, 08:55:08 PM »
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.

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.

nannunannu

  • Guest
Re: No connectivity between clients & SOA after successful deployment
« Reply #3 on: June 21, 2012, 09:28:49 PM »
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.

HomeNet

  • Guest
Re: No connectivity between clients & SOA after successful deployment
« Reply #4 on: June 21, 2012, 09:38:09 PM »
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.

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.

nannunannu

  • Guest
Re: No connectivity between clients & SOA after successful deployment
« Reply #5 on: June 21, 2012, 11:05:02 PM »
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.

HomeNet

  • Guest
Re: No connectivity between clients & SOA after successful deployment
« Reply #6 on: June 22, 2012, 12:23:47 PM »
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.

HomeNet

  • Guest
Re: No connectivity between clients & SOA after successful deployment
« Reply #7 on: June 22, 2012, 12:46:05 PM »
In the console, under admin -> settings -> setup there is a link to download the .exe installer...

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.
« Last Edit: June 22, 2012, 01:23:57 PM by HomeNet »

HomeNet

  • Guest
Re: No connectivity between clients & SOA after successful deployment
« Reply #8 on: June 22, 2012, 12:47:41 PM »
Also, I think you just need port 25322 TCP (not udp)...  I think.

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.

Offline lukas.hasik

  • Moderator
  • Advanced Poster
  • *
  • Posts: 940
  • Product manager of Avast Security for Windows
Re: No connectivity between clients & SOA after successful deployment
« Reply #9 on: June 22, 2012, 01:15:23 PM »
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?

Quality is also a feature.

HomeNet

  • Guest
Re: No connectivity between clients & SOA after successful deployment
« Reply #10 on: June 22, 2012, 01:19:01 PM »
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?

I did the unattended install.

Offline Avosec-UK

  • Avosec Technical Support
  • Avast Reseller
  • Sr. Member
  • *
  • Posts: 296
    • Avosec
Re: No connectivity between clients & SOA after successful deployment
« Reply #11 on: June 22, 2012, 01:30:46 PM »
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"


HomeNet

  • Guest
Re: No connectivity between clients & SOA after successful deployment
« Reply #12 on: June 22, 2012, 01:36:02 PM »
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"

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

Offline Avosec-UK

  • Avosec Technical Support
  • Avast Reseller
  • Sr. Member
  • *
  • Posts: 296
    • Avosec
Re: No connectivity between clients & SOA after successful deployment
« Reply #13 on: June 22, 2012, 01:37:49 PM »
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"

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
Sorry I needed to clarify: you should look for this file on the client machines.

HomeNet

  • Guest
Re: No connectivity between clients & SOA after successful deployment
« Reply #14 on: June 22, 2012, 01:52:43 PM »
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"

Code: [Select]
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