Privacy Policy

Guest
  • Guest
  • Guest Topic Starter
1999-05-29T00:12:00Z
Date parsed: 5/29/1999 12:12:00 AM

Date: Fri, 28 May 1999 23:12:00 +0200

Chris,

0.0.0.0:514 means that a program is listening on ALL ip-addresses/514. =

You

must still have another syslog daemon running...

Franz

Chris Berthaut <cberthaut@hibernia.com> wrote in message

news:C1CEE8E342DDD111A5720020AFE7798F15C0CF@is1.netal.com...

> I've done that and see TCP port 0.0.0.0:514 listening and UDP port

> 0.0.0.0:514. No port 514 on my local IP address. But still cannot =

start

the

> service, get "An error occurred in binding a socket to

10.16.62.40:514/UDP.

> WinSockets Error: 10048" in the application event log. Any ideas???

> I had installed another syslogd, but uninstalled it when it wouldn't =

work

> for me either. Don't see any remnants of it on the machine.

> thanks!

> cb

> cberthaut@hibernia.com

>

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

> news:C1CEE8E342DDD111A5720020AFE7798F1573A6@is1.netal.com...

> > Gary,

> >

> > execute the command "netstat -a -n >ports.txt" and then send me the

file.

> > This file will contain all ports in use.

> >

> > Franz

> >

> >

> > Gary King wrote in message ...

> > >Hi Franz,

> > >I have a Network management program CiscoWorks 2000 running on this

> > machine.

> > >I'm not aware of this program having any syslogging capabilities. =

Any

> > other

> > >ideas to debug this problem ?

> > > Thanks

> > >

> > >

> >

>