On Thu, Jul 5, 2012 at 2:24 PM, Tom Goerger wrote:
> The error is coming from the client side. I've verified that the clamd
> instance on the server is up and running on the TCP port for the server
> address, rather than localhost, and running on the correct port. From the
> log file on the ser
Hi Tom,
NOTE: This forum uses bottom posting which means replying at the bottom
of the email.
On Tue, Jul 3, 2012 at 1:23 PM, Jim Preston wrote:
On 07/03/2012 11:02 AM, Tom Goerger wrote:
Hi,
I'm having problems setting up ClamAV to work in network mode. The way
I'm
envisioning things is
The error is coming from the client side. I've verified that the clamd
instance on the server is up and running on the TCP port for the server
address, rather than localhost, and running on the correct port. From the
log file on the server side, everything appears to be running correctly.
I've ve
On 07/03/2012 11:02 AM, Tom Goerger wrote:
Hi,
I'm having problems setting up ClamAV to work in network mode. The way I'm
envisioning things is I've got a machine running clamdscan on client, and
clamd running on server. I've got clamd.conf on client set up to point at
the IP and port of serve
Hi,
I'm having problems setting up ClamAV to work in network mode. The way I'm
envisioning things is I've got a machine running clamdscan on client, and
clamd running on server. I've got clamd.conf on client set up to point at
the IP and port of server like so:
# TCP port address.
# Default: no
