Showing posts with label Linux. Show all posts
Showing posts with label Linux. Show all posts

Windows Event log to syslog converters

windows SyslogServer

syslog is a standard for forwarding log messages in an IP network. We can send device /server logs to the sys log server. so that we can use Syslog server as a central log repository system, commonly we use syslog servers to monitor the networking devices, I was just thinking about the consolidation of windows event logs to a syslog server. because we don’t check our event logs regularly in windows servers . It will be more useful if there is a single window to monitor or filter the logs from deferent servers.

How to send logs from a windows server?

By default there are no options in windows servers we have to use some third party applications to communicate with syslog server. Following are the list of some application which can convert event logs to a syslog message.

 

Event Reporter

EventReporter processes the NT Event Logs, parses them and forwards the results via Syslog protocol to a central Syslog server. It runs on all flavors of Windows Servers and Workstations starting from old-fashined NT up to Server 2008 and Windows Vista.

Ntsyslog

This program runs as a service under Windows NT based operating systems. It formats all System, Security, and Application events into a single line and sends them to a syslog(3) host.

Evtsys

The Eventlog to Syslog utility is a program that runs on Microsoft Windows NT, 2000, or 2003 server, monitoring eventlog messages. When a new message appears in the eventlog, it is read, formatted, and forwarded to a UNIX syslog server. Depending on the facility and priority of the message and the configuration of the syslog server, the message will be logged to a message file or displayed on the console. The most useful situation is to log ERROR or WARNING messages on a console that will alert the administrative staff when unusual conditions exist on the Windows server. The console ought to be one that the administrative staff monitor regularly.

Snare

Snare for Windows is a Windows NT, Windows 2000, Windows XP, and Windows 2003 compatible service that interacts with the underlying Windows Eventlog subsystem to facilitate remote, real-time transfer of event log information.
Event logs from the Security, Application and System logs, as well as the new DNS, File Replication Service, and Active Directory logs are supported. Log data is converted to text format, and delivered to a remote Snare Server, or to a remote Syslog server with configurable and dynamic facility and priority settings.

 

Monitor Ware Agent

It's pure event log functionality is the same, but is also support many more data sources, providing a complete monitoring solution for Windows machines. Most importantly, it can also read, process and forward text log files (including special handling for IIS logs). This permits, for example, the transmission of DHCP server log records. Other log sources include database tables, serial ports, port probes and many more things.

Winlogd

Winlogd is a syslog client for Windows that allows the Event Log to talk to syslog. It runs as a Service monitoring the Windows Event Log and forwarding the messages to a syslog server. Configuration is made via editing registry settings.

My low cost NAS with 1 TB Storage


We are dumping lot of old PIII computers, They are not capable to run windows OS. It will be dead slow with windows. ( PIII 500 Mhz + 128 MB RAM + 10GB HDD ), I planed to utilize them So I searched for some good solutions At last I find a project with freenas. That is why I converted them to A NAS Box, Once I Created a NAS with 80 GB HDD, It was working fine for last 6 Months, Now my requirements are high. I need speed in disk read ( so this time i used SATA instead Of IDE ), and Large Disk Space 1 TB ( 1024 GB ) So I use a P4 PC ( PIII Wont support this much )

FreeNAS is a minimal FreeBSD distribution that provides NAS (network-attached storage) services: CIFS (Samba), FTP, NFS, RSYNC, local user authentication, and software RAID. It may be booted and run from compact flash or CD-ROM. It also features a full Web-based configuration interface. It's an open source project published under the BSD license. The software is popular enough to have gotten more than 20,000 downloads last month.

Download : FreeNAS Setup and User Guide

Download : Freenas

I have created my NAS with freenas. I used a P4 PC for the SATA support, 256 MB RAM, and 2 x 500 GB HDDs, I downloaded the iso file from http://www.freenas.org/. burned it to a CD Installation is very simple than a windows installation. Installed both 500 Gb HDD in that pc. And installed that OS to one HDD. Its take only 64 MB partition and for the Freenas OS partition. I configured the ip address of our network. Other works are done by the help of web GUI.

We can login to server by entering the ip address ( Eg : http://192.168.0.1/ )

Default User name : Admin

Default User password : freenas

I changed my gateway, DNS etc .. then formatted second HDD, I am using UFS partition for the data partitions. Its giving me more perfomence. Using web GUI mounted both partitions. Here I enabled Samba, FTP and ISCSI, We can add this Nas box to our domain for authentication If you don’t have a domain setup, you can create users and groups locally. It support Software raid. If you finished your freenas installation take a backup of the configuration.


Here I attached some of the images of my FTP Server.









Get updates via Email :