Michael,
I'm just throwing my two cents in here... in my experience header checksums
that Wireshark picks up as being 000 instead of the correct value is usually
because of TCP offload in the NIC... it's usually TOE doing its job, and
you're not seeing the checksum being computed because the
09:21 AM -
From:
Michael Barrett/MGIC
To:
ossec-list@googlegroups.com
Date:
05/03/2010 03:26 PM
Subject:
Re: [ossec-list] Having problem with
install on 64bit system
I ran a wireshark, does this header
checksum error mean anything?
DST = ossec server
Does this error help determine
|
--|
|
| Subject: |
|
--|
|Re: [ossec-list] Having problem with install on 64bit system
: |
|
--|
|Re: [ossec-list] Having problem with install on 64bit system
: |
|
--|
|Re: [ossec-list] Having problem with install on 64bit system
From: Michael Barrett michael_barr...@mgic.com
To: ossec-list@googlegroups.com
Sent: Tue, April 27, 2010 1:37:44 PM
Subject: Re: [ossec-list] Having problem with install on 64bit system
Also the manage agent UI doesn't work, I don't know if that helps or hurts
|
--|
|
| Subject: |
|
--|
|Re: [ossec-list] Having problem with install on 64bit system
Hi Michael,
Do you get any errors on the manager's ossec.log file? Check there as well..
thanks,
--
Daniel B. Cid
dcid ( at ) ossec.net
On Thu, Apr 22, 2010 at 11:05 AM, Michael Barrett
michael_barr...@mgic.com wrote:
I am having an issue with one of my systems. This is OSSEC Windows version
I am having an issue with one of my systems. This is OSSEC Windows version
2.2 on Windows Sever 2003 64bit
I have tried the install via the setup program as well as copying the files
from another server and updating the client.keys file and manually creating
the service.
I also tried to remove
