Date: Mon, 17 Apr 2000 18:47:05 +0200

Franz,

I am using v2.0. I have a license, and It has not expired.

To make it simple, I have removed all rules from the system, and am only

requesting for it to log all incoming messages to the NT event log. I =

am

running NT 4.0 w/ sp5.

For some reason I am just not getting anything. I am going to attempt =

to

re-install the Service Pack, and see if that helps, and then I guess I =

will

have to look into the Cisco configs. I don't think that I am blocking =

any

ports or packets in my building routing

Thanks for the quick response!

Jay

"Franz Krainer" <franzk@netal.com> wrote in message

news:3A25DBCDF73F2245957BD0B041BEDAF001056D@is1.netal.com...

> Hello Jay,

>

> which version of SL4NT are you using. If you use v2.0, it may be that =

the

> 60-days evaluation license expired. Check the Application Event Log =

for

any

> warnings and error generated by SL4NT.

>

> SL4NT, like any other syslog daemon, will by default listen on =

UDP/514.

>

> Franz

>

>

> "Jay P Ross" <jross@pdl.com> wrote in message

> news:3A25DBCDF73F2245957BD0B041BEDAF0010567@is1.netal.com...

> > Anybody,

> >

> > For some reason all of my logging has stopped. I log events from =

Cisco

> > Routers, from Printers, and a myriad of other network equipment.

> >

> > After two major events, logging has ceased. First, I added a router

> between

> > the two buildings that I manage, secondly, I changed the IP of the

syslog

> > server.

> >

> > I have gone through and checked that all of my equipment points to =

the

new

> > system for logging... but I still get nothing.

> >

> > I need to check and see if the new router is responsible. Does =

anybody

> know

> > what port the syslog service runs on?

> >

> > Thanks,

> >

> > Jay

> >

>