General discussion

Locked

Netware to report to Syslog server?

By mhindt ·
We run a heterogeneous network made up of NT, Netware and Linux + various print servers. I want to have all the servers send their logs to a hardened Linux Syslog server. There to be analyzed by a script with any unusual events emailed to the Netware administrator and myself. I have been able to get all but the Netware servers to do this. I have found a syslogd for Netware but it will only receive messages. I need something that will send the various Netware logs to the Linux box. If anyone has any perl scripts or netbasic scripts that I could invoke with Netware's cron or if you know of a program that will forward the logs I would appreciate the information. Thanks in advance

This conversation is currently closed to new comments.

12 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Netware to report to Syslog server?

by TechDictator In reply to Netware to report to Sysl ...

Doesn't look like it's possible. There is a syslogd nlm that receives, but not one that sends. SNMP traps is still an option.

Collapse -

Netware to report to Syslog server?

by mhindt In reply to Netware to report to Sysl ...

Thanks for the SNMP trap suggestion but I do not wish to add any more services to the linux box.

Collapse -

Netware to report to Syslog server?

by estebandelatorre In reply to Netware to report to Sysl ...

Netware won't be able to send the log files to some other point on the network.
What you need to do is perform a task inside the linux box (nw client for linux necesarry) in order to make linux to retrieve the files from the Nw box, via a file system copy nw to linux.

Collapse -

Netware to report to Syslog server?

by mhindt In reply to Netware to report to Sysl ...

Thanks for the info but this box must have the minimum of services/deamonds/moduals on it. Currently it has a firewall on it that prevents any incomming traffic except for SSH and syslog. It also prevents all outgoing except smtp. I do not wish to add any two way comunication except for the ssh (on a non-standard port). This will help prevent the discovery of the system incase of a network break-in. I would be willing to open a port for one-way incoming traffic but as the netware client requires a two way comunication it is not my ideal solution.

Collapse -

Netware to report to Syslog server?

by mhindt In reply to Netware to report to Sysl ...

Point value changed by question poster.

Collapse -

Netware to report to Syslog server?

by maxwell edison In reply to Netware to report to Sysl ...

You can have Linux emulate other operating systems, so that their respective clients can log into it. For example, you can configure Samba and have Windows clients log into it. You can configure NFS and connect it to other Linux or Unix machines. You can also configure it to act as a NetWare server, so that Windows machines running NetWare clients can access it. Clients would consider it another NetWare server and be able to do file and printer sharing. This is a good solution if you have a NetWare network and want to use a new linux server. Let?s see how to configure Linux to act as a NetWare server.

Follow this link for the whole scoop and related links:

http://librenix.com/?inode=197

(REMOVE SPACES from the pasted URL)

Maxwell

Collapse -

Netware to report to Syslog server?

by mhindt In reply to Netware to report to Sysl ...

Thank you for the info but this is very simular to answer #2 the Logfile server must be pratically invisible on the network to prevent it from being hack in case of a network break in. What I need is for the Netware box to be able to talk to it. Togive you an idea of how invisible I need the Linux Logfile sever to be, I have though about snipping the transmision wires on its network connection.

Collapse -

Netware to report to Syslog server?

by mhindt In reply to Netware to report to Sysl ...

Point value changed by question poster.
This is it all the TechPoints I own. I sincerly hope that someone can give me an aswer but I am begining to think that it is a wild goose chase with no clear answer advailible.

Collapse -

by marccouture In reply to Netware to report to Sysl ...

If you are using SSH, why not use SCP clients to securely copy your logs over to your Linux box?

There's a nice list of SCP clients available for most major platforms (not Netware though) here:

http://www.gweep.net/help/ssh.html

You should be able to use command-line ssh if you use OpenSSH on your Netware server.

On Windows, I like WinSCP, as it emulates the old, trusty Norton Commander-like two panel int4erface. You can find it here:

http://winscp.sourceforge.net/eng/

Good luck!

Collapse -

by dumptrash In reply to Netware to report to Sysl ...

This lookst like what you are after (at least in part...) http://www.novell.com/coolsolutions/tools/14780.html
==============================
NetWare File Server Activity Daemon (fadmn.nlm 2.00.a and fadmnexp.nlm 0.01.a)
Novell Cool Solutions: Cool Tool
In Brief

NetWare file server utilites allow you to view real-time file access events and write to log file or send to syslog daemons.
Vitals

Product Categories:
# NetWare
# Open Enterprise Server

Functional Categories:
# Server Utilities
# Workgroup

Updated: 27 Feb 2006
File Size: 20KB
License: Free
Download: /coolsolutions/tools/downloads/fadmn.zip
Home Page: http://www.lenik.ru/netwarends/fadmn/index.html
Publisher: Leonid F Krotov

Details

FADmn.nlm - Displays file activity on server. File activity log displayed on fadmn console screen.
fadmnexp.nlm - This module can write information given by fadmn.nlm to system console, wtite to log file, or send information to other network services by UDP (syslog, as example)

fadmn.nlm use:
load fadmn.nlm

fadmnexp.nlm use:
load fadmnexp.nlm [write_console]
[write_log [max ] [count ]]
[send_udp host [port ]] [bind ] [bindport ]

Parameters are:
write_console - OPTIONAL;
use this key for output to system console
write_log - OPTIONAL;
use this key for writing to log file
logfname - log file name (maybe full path to file)
max <logsize> - maximum log file size in MBytes (default: 600)
count <logcount> - maximum number of log files (default: 10)
send_udp - OPTIONAL;
use this key for sending info over UDP (syslog, as usual)
host <lhost> - target UDP host (dotted string format, or dns name)
port <lport> - target port on target host (decimal, default: 514)
bind <addr> - bind to local address before sending packets
bindport <port> - bind to local port before sending packets

Other tools at http://www.lenik.ru

Back to Software Forum
12 total posts (Page 1 of 2)   01 | 02   Next

Software Forums