Using my ClamAV service, it tries to ping clamd regularly to make sure it is still running. It uses TCP/IP to 127.0.0.1 with the default port to do this. If you are running a firewall that blocks access to the clamd TCP port, have disabled it's listening on 127.0.0.1, or have changed the port number, then you can't use it with my service program.
Bret > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Matthias Karl > Sent: Sunday, October 28, 2007 4:27 AM > To: [email protected] > Subject: [clamav-win32] Info in Eventlog > > Hi > > I keep getting the following message in the Eventlog. What > does it mean and where is it not able to connect to? > > Type: Information > User: N/A > Source: ClamAV for Windows > Category: None > Event ID: 0 > > SocketException: System.Net.Sockets.SocketException: No > connection could be made because the target machine actively > refused it > at System.Net.Sockets.TcpClient.Connect(String hostname, > Int32 port) > at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) > at ClamDaemonService.Service1.tcpsend(String message) > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > >
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32
