AVG Network Version 2

[DanielUK]

Hi,

Does anyone have the AVG 7 network version running successfully? I'm having a dog of a time trying to get it to work and communicate with the AVG tech support at the same time.

I have a small network of win2k PC's and a win2k Server. The AVG TCP server is installed on the server itself and the AVGADMIN program is on my own PC. All the workstations connect fine to the TCP server and I can use AVG admin to remotely schedule tasks and check/alter each workstations configuration remotely -everything functions in that respect.

What I can't get any of the workstations to do is update REMOTELY using AVGADMIN regardless of whether I request a directory update from a publicly available directory on the server (with the update files in), a tcp update or even an update from the AVG site. I can though, go to each workstation and get it to update from the publicly available folder on the server or update from the AVG site.

Anyone set this up before and had simliar kinds of problems? The manual isn't the best in the world at explaining things.

Thanks

Dan

 

[Grenage]

Greetings.

We use AVG Network version here, everything works fine with the exception of the remote update.

I appears to work on all of the win9x machines but only on a few of the win2k machines. I have been unable to discover why although I have not dedicated too much time to it as our machines update automatically.

The message/command is simply not aknowledged by the client machine according to the AVGADMIN log.

Russell.

 

[DanielUK]

Thanks, and I thought I was going mad! This is one of the reasons we purchased this version in the first place so we could centrally manage the updates i.e. one download to a publicly available directory from which the workstations update from. So I guess each of your workstations are scheduled to download from the AVG website? I think I may have to resort to this if I can't get any further on this soon.

Thanks

Dan

 

[Grenage]

I'll explain how I set ours up:

AVG TCP Server is installed on a server.

avginetl.exe on the server is scheduled to run twice a day; basically this creates a mirror of the Grisoft updates on the server.

The AVG TCP Server scipt was configured with our settings.
The clients were installed with the "Communications Library".

Using AVG ADMIN I set the default workstation to use "

http://localupdateserver:4156?dbq".

This means that when the clients search for an update on the internet they are actually looking at your local server rather than using "

http://grisoft.com".

Using AVGADMIN I gave the default workstation 2 schedules for updating via the internet (Morning and Afternoon).

All of the workstations update perfectly using this method (for us at least) and so we have never had the need to issue a manual update. If a machine is turned on and it has missed a scheduled update it will do it then.

If you are still having troubles post back and I'll help where I can, I did find the Grisoft support to be very 'on the ball'.

Russell.

 

[DanielUK]

Thanks Russell, I've not managed to get a scheduled update from either directory or AVG TCP Server to work yet.

You couldn't do me a favour and look at the configuration screen of a working client within AVG Admin? I'm not too sure of the settings for Internet Connection and Updates. More to the point:

- should

http://localupdateserver:4156?dbq

be specified as the Address in the Internet connection or left as the Grisoft web address?
- should updates be set to Incremental if I am using TCP server?
-on your scheduled update is it simple classed as an update (as opposed to update from directory?)

All my clients refuse to update uing TCP Server even though remote administration on the clients pass all the "tests". I do have ZoneAlarm firewall but it doesn't work regardless of me having it on or off. Anything AVG related has been given access anyhow. I'm just miondful that I may not be specifying the

http://localupdateserver:4156?dbq

in the right places.

Thanks again,

Dan

 

[Grenage]

Okay here are our settings for the DEFAULT WORKSTATION (all workstations use this when created).

License details: That you have.
Resident Shield: "Yes" to all except "Check all files" and "skip files without extension".

Integrity database: all defaulted to C:\AVG7*.DAT.
Scan Logs: Maximum log count = 1000 and deleted after 60 days.
Virus Vault: Yes, 20, 10, No, 2000, 90 (In that order).
Allowed: Nothing set here.
Internet Connection: as follows below:

Server:

http://localserver

address:

http://localserver:4156?dbq

Active server: 0
Use Proxy: 0
Proxy Server:
Port: 8080

The rest of the internet connection properties are either "No" or left blank.

Updates:
Use incremental updates: Yes
Krnl.update.complete_only: No
Perform update: 1
Restart afer update: 0
Show update progress: No
Terminate Processes: yes

Remote Administration:
DataCenter file:

http://localserver:4156?dbq

Port for notifications: 6051

 

[DanielUK]

Thanks a lot Russell that's verified a couple of things. I've allowed http request logging and tried to do a manual update from a workstation which returns with a server error and that the control file is damaged. The http log says: "192.168.0.9 - - [27/Apr/2004:11:09:28 GMT] "GET /avg7info.ctf HTTP/1.1" 404" so I gather it's not looking in the right place as the control file is sitting in my update directory on the server. The only thing I have left to verify is the avgtcpsv.ini file on the server. Have you left yours as is (default)? the only thing I have changed (aprt from the License parameter) is the following:

# Limited HTTP support for local updates
#
# AVG TCP Server provides basic support for the HTTP GET command to support
# updates over HTTP in local network. The following options control
# this behavior.

# If set, the GET command support is active. This path defines the
# local directory where update files are stored. Only files in this
# directory are made available using the GET command
# By default, this is set to empty string and thus the GET command support
# is not available
LocalHttpServerRoot=c:\Public\AVG

which is local to the fileserver the TCP Server runs on.

Thanks again,

Dan

 

[Grenage]

the control file is damaged

Right I can help you here, when I had this error it meant that the AVG TCP Server configuration file not properly configured.

I will follow this post with a copy of my configuration file, and mark the sections I changed in bold.

 

[Grenage]

# AVG TCP Server configuration file
#
# Lines beginning with # and empty lines are ignored
#
# Specifies the port that will AVG TCP Server use for incoming connections
# Default value is 4156
# If basic GET command support is active (see bottom of this config file),
# the HTTP server uses this port for updates, too.
# Remove the # character from the beginning of next line to listen on port 80
#Port=80

# Specifies local address that the AVG TCP Server will use for incoming
# conections. Default value is empty, meaning any local address
# If the specified name resolves to more than one address then first
# available address is used (the server tries each of them)
#LocalAddr=localhost

# Full path to the database file. For relative paths, current directory
# is the AVG TCP server executable directory
# Default value is AVGDB.FDB - i.e. the database file is stored in the same
# directory as the executable file
#Databasepath=c:\avg7datacenter\avgdb.fdb

# If set to 1, more verbose (diagnostic) output is produced.
# Default value is 0, producing no excessive diagnostic output
#Verbose=1

# License number. If not specified or if invalid license number is
# used, the server will operate in "unregistered" mode

License=**-******-**-****-*****
Paste your licence number in here, but leave off the last string segment (for security purposes).

# If set to 1, client calls to database server will be isolated and will
# not run concurrently. This will degrade performance, however, it will
# allow to use FireBird or Interbase server with its native client DLL
# Default value is 0, providing maximum performance with the built-in
# database engine
#IsolatedClients=1

# This parameter controls the transaction mode used when accessing
# Firebird SQL server. By default, AVG TCP Server uses the "concurrency"
# transaction mode. If FBConsTrans is set to 1, the more conservative
# "consistency" mode is used. Set only if the AVG TCP Server reports
# errors in SQL commands
#FBConsTrans=1

# Username and password that the clients will have to use in order to
# access the DataCenter. If these values are empty, clients don't have
# to authenticate. If the values are set, clients are obliged to use them
# By default no authentication is necessary
# It is recommended that if you change these parameters you use values
# different from the default ones
#Username=AVGUser
#Password=AVGPass

# Username and password for accessing the database engine itself. These would
# be hardly used for the embedded database engine but could come handy
# if AVG TCP Server connects to a standalone database server
#DBAUserName=SYSDBA
#DBAPassword=masterkey

#
# Clients connect to the server using the following connection string:
#

http://host

[ort]?dbq[=dbpath][?username[?password]]
# Sqaure brackets [ ] denote optional values.
# dbpath, username and password may not be supported by the server (i.e. will be ignored)
# Default value for port is 4156
#

# AVG TCP Server status can be also checked using web browser
# By default, requesting root default document will return the server
# status (i.e.

http://address:port/

). The following parameter can be used
# to change the URL to be used for querying the status.
# Default value / corresponds to the default root document
# If the string is empty, status display functionality is disabled
# Examples:
# The following value will change the URL for server statistics
# to

http://address:port/status.html

#WebUIURL=/status.html
# The following setting will disable the status display functionality
#WebUIURL=

#
# Limited HTTP support for local updates
#
# AVG TCP Server provides basic support for the HTTP GET command to support
# updates over HTTP in local network. The following options control
# this behavior.

# If set, the GET command support is active. This path defines the
# local directory where update files are stored. Only files in this
# directory are made available using the GET command
# By default, this is set to empty string and thus the GET command support
# is not available
LocalHttpServerRoot=c:\AV
Here I define the location of the update files, C:\AV is where AVGINTEL.exe mirrors the grisoft updates to on my network

# The following option defines path that the clients should use for
# requesting the update files. If empty, root directory is used.
# This path in HTTP request maps to the local directory defined by
# by LocalHttpServerRoot option.
# For example, if:
# LocalHttpServerRoot=c:\inetpub and
# HttpServerRoot=/avgupdate
# then requests for

http://server:4156/avgupdate/avg7info.ctf

# will provide file c:\inetpub\avg7info.ctf (suppose it exists)
# Please note the port number used in example above!
# Web support uses the same port as the DataCenter support, therefore
# the port number for updates is specified using the Port parameter
# (see above) - and the default value is 4156.
#HttpServerRoot=/avgupdate

# By default the AVG TCP Server does not log HTTP requests. If the following
# option is used then all HTTP GET requests are logged in the "Apache
# Server Combined log file format" into the file specified.
#HttpLogPath=c:\Logs\avgtcp_http.log

 

[DanielUK]

Thanks again Russell! It looks remarkably like mine:

# AVG TCP Server configuration file
#
# Lines beginning with # and empty lines are ignored
#
# Specifies the port that will AVG TCP Server use for incoming connections
# Default value is 4156
# If basic GET command support is active (see bottom of this config file),
# the HTTP server uses this port for updates, too.
# Remove the # character from the beginning of next line to listen on port 80
#Port=80

# Specifies local address that the AVG TCP Server will use for incoming
# conections. Default value is empty, meaning any local address
# If the specified name resolves to more than one address then first
# available address is used (the server tries each of them)
#LocalAddr=localhost

# Full path to the database file. For relative paths, current directory
# is the AVG TCP server executable directory
# Default value is AVGDB.FDB - i.e. the database file is stored in the same
# directory as the executable file
#Databasepath=c:\avg7datacenter\avgdb.fdb

# If set to 1, more verbose (diagnostic) output is produced.
# Default value is 0, producing no excessive diagnostic output
#Verbose=1

# License number. If not specified or if invalid license number is
# used, the server will operate in "unregistered" mode
License=**etc**

# If set to 1, client calls to database server will be isolated and will
# not run concurrently. This will degrade performance, however, it will
# allow to use FireBird or Interbase server with its native client DLL
# Default value is 0, providing maximum performance with the built-in
# database engine
#IsolatedClients=1

# This parameter controls the transaction mode used when accessing
# Firebird SQL server. By default, AVG TCP Server uses the "concurrency"
# transaction mode. If FBConsTrans is set to 1, the more conservative
# "consistency" mode is used. Set only if the AVG TCP Server reports
# errors in SQL commands
#FBConsTrans=1

# Username and password that the clients will have to use in order to
# access the DataCenter. If these values are empty, clients don't have
# to authenticate. If the values are set, clients are obliged to use them
# By default no authentication is necessary
# It is recommended that if you change these parameters you use values
# different from the default ones
#Username=AVGUser
#Password=AVGPass

# Username and password for accessing the database engine itself. These would
# be hardly used for the embedded database engine but could come handy
# if AVG TCP Server connects to a standalone database server
#DBAUserName=SYSDBA
#DBAPassword=masterkey

#
# Clients connect to the server using the following connection string:
#

http://host

[ort]?dbq[=dbpath][?username[?password]]
# Sqaure brackets [ ] denote optional values.
# dbpath, username and password may not be supported by the server (i.e. will be ignored)
# Default value for port is 4156
#

# AVG TCP Server status can be also checked using web browser
# By default, requesting root default document will return the server
# status (i.e.

http://address:port/

). The following parameter can be used
# to change the URL to be used for querying the status.
# Default value / corresponds to the default root document
# If the string is empty, status display functionality is disabled
# Examples:
# The following value will change the URL for server statistics
# to

http://address:port/status.html

#WebUIURL=/status.html
# The following setting will disable the status display functionality
#WebUIURL=

#
# Limited HTTP support for local updates
#
# AVG TCP Server provides basic support for the HTTP GET command to support
# updates over HTTP in local network. The following options control
# this behavior.

# If set, the GET command support is active. This path defines the
# local directory where update files are stored. Only files in this
# directory are made available using the GET command
# By default, this is set to empty string and thus the GET command support
# is not available
LocalHttpServerRoot=c:\Public\AVG

# The following option defines path that the clients should use for
# requesting the update files. If empty, root directory is used.
# This path in HTTP request maps to the local directory defined by
# by LocalHttpServerRoot option.
# For example, if:
# LocalHttpServerRoot=c:\inetpub and
# HttpServerRoot=/avgupdate
# then requests for

http://server:4156/avgupdate/avg7info.ctf

# will provide file c:\inetpub\avg7info.ctf (suppose it exists)
# Please note the port number used in example above!
# Web support uses the same port as the DataCenter support, therefore
# the port number for updates is specified using the Port parameter
# (see above) - and the default value is 4156.
#HttpServerRoot=/avgupdate

# By default the AVG TCP Server does not log HTTP requests. If the following
# option is used then all HTTP GET requests are logged in the "Apache
# Server Combined log file format" into the file specified.
HttpLogPath=c:\Logs\avgtcp_http.log

c:\Public\AVG is a local directory on our server where I get a batch file and wget on my AVGIADMIN client to download to D:\AVG where "Public" on the server is mapped as the "D:" drive. It downloads the updates fine but I'm hardpressed to see where I'm going wrong. I'm going round in circles with the AVG staff, probably because I keep getting replies from different people.

Thanks

Dan

 

[Grenage]

Aye I can see nothing wrong with that.

Does the log file "Avg7.log" reveal any clues at all? It is usually stored in the "all users\application data\grisoft\Avg7Data" folder.

Russell.

 

[DanielUK]

Not really any clues there AFAICS. AVG have just told me to use

http://localserver:4156

(i.e. remove the ?dbq). I'm going to give that a try but am wondering why yours should work in that format and not mine??

Thanks

Dan

 

[DanielUK]

More specifically they wrote:

The URL address from which it checks for update has to be
"

http://localserver:4156"

without quotes. Now it should find the control file avg7info.ctf and everything should work correctly.

This makes it different to your config which I find strange! Going to give it a go now.

Thanks

Dan

 

[DanielUK]

Nope, no cigar -same error. I've tried now to use both

http://localserver:4156

and

http://localserver:4156?dbq.

Thanks

Dan

 

[Grenage]

They told me the same thing when I was troubleshooting the issue I must admit, I had no luck with that either.

Just to check, is "avg7info.ctf" definately present in "c:\Public\AVG" on the AVG TCP Server?

 

[DanielUK]

Hi Russell, I think I've cracked it. I finally got the "update from directory" to work but it required setting the schedule on each workstation (logged in as a user) manually. Anyway, thanks for all your help, fingers crossed it will be OK now!

Thanks

Dan