Re: [logs] Syslog client alternatives for NT

From: Tina Bird (
Date: Fri Nov 09 2001 - 11:59:59 PST

  • Next message: Cedar Hannan: "[logs] Converting log messages to XML format."

    My very favorite windows-to-syslog tool is
    Event Reporter:
    It's very configurable: you can set facilities and
    levels independently for each of the Windows NT
    and 2000 log sources, and it's got filtering capability
    that allows you to either only forward specific events
    that you care about, or to drop messages that you
    know you don't care about.  Very very helpful in a 
    large installation.
    You'll also want to be careful with BackLog; it's not
    supported yet on Win2k, and it creates some really
    peculiar errors -- I've reported them to Intersect
    Alliance, but they've not yet had time to address the
    More information and auditing advice on Windows at
    cheers -- Tina "I'm not a Windows expert" Bird
    On Fri, 9 Nov 2001, Frank Solomon wrote:
    > Date: Fri, 09 Nov 2001 16:39:06 -0500
    > From: Frank Solomon <sysfrankat_private>
    > To: loganalysisat_private
    > Subject: [logs] Syslog client alternatives for NT
    > Greetings:
    > We're currently working on developing a central syslog strategy.
    > Unix boxes seem to be very little problem.  We've got every kind there is. . .
    > We think we might be able to figure out how to trim out the garbage from 
    > our firewall boxes; although this hasn't been proven yet.
    > We might even be able to integrate our Cisco IDS stuff, if we can ever get 
    > that working. . .we're not sure.
    > But we're curious how others have solved the centralization of logs from 
    > other kinds of systems.  Specifically, Windows2000 or NT Servers, Novell 
    > Servers running in the NDS environment, and IBM Mainframes running MVS.
    > Right now we're experimenting with some free syslog client software called 
    > Backlog for NT.  But, it seems kind of poor in that it doesn't set the 
    > Facility or Priority of the log messages dynamically based on the content 
    > of the NT Event log message.  What's better?  Free or otherwise.
    > We're at a bit of a loss on Netware; it looks like the "syslog" it has 
    > doesn't log remotely?  Or does it?  Also, apparently a lot of the data gets 
    > squirrelled away in the NDS (directory).  Is there something that can 
    > forward this stuff in real time to a syslog daemon somewhere?  What are 
    > others doing?
    > The mainframe guys laughed at me when I suggested we might want them to 
    > forward logs to a central server.  MVS when it impersonates Unix does have 
    > a syslog facility.  But, it doesn't look like much useful stuff comes out 
    > of it.  Is there something that makes the console log available via 
    > syslog?  What about ACF2 logs?  Any hope here?  Once again, what are others 
    > doing?
    > Certainly, we could buy some big expensive package from Pentasafe or IBM; 
    > but, we'd like to avoid that if we could, and work things into a syslog 
    > environment.
    > Thanks in advance,
    > Frank
    > *****************************************
    > Frank Solomon
    > University of Kentucky
    > A good mechanic only needs two tools:  Duct tape and WD40.
    > WD40 to make things go; and duct tape to make them stop.
    > --unknown
    > *****************************************
    > ---------------------------------------------------------------------
    > To unsubscribe, e-mail: loganalysis-unsubscribeat_private
    > For additional commands, e-mail: loganalysis-helpat_private
    "I was being patient, but it took too long." - 
                                    Anya, "Buffy the Vampire Slayer"
    Log Analysis:
    To unsubscribe, e-mail: loganalysis-unsubscribeat_private
    For additional commands, e-mail: loganalysis-helpat_private

    This archive was generated by hypermail 2b30 : Fri Nov 09 2001 - 14:33:34 PST