|
if you leave everything blank it won't see
anything.
You must at least check something for the TYPE of entry
(warning - stop - ...)
And then you will get a down each time something new gets
in the eventlog of that type.
Dirk. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Sweetman Sent: Wednesday, July 27, 2005 12:45 AM To: [email protected] Subject: RE: [SA-list] eventlog check w/ firewall enabled. Just to make sure I understand how the
external EventLog checker works. I want to be notified for any/all Warnings
& Errors, so I just check those boxes and leave everything else blank,
yes? Or do I need to put a wildcard character into the Source, Event ID,
etc… boxes?? Thanks, -bill From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Dirk Bulinckx it used Netbios to
access the system. Netbios uses TCP/UDP 137-139 Dirk. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of I’m
trying out the new (beta) eventlog checker. I’m trying to check a Win 2003
server (SP1) with the firewall installed. I saw UPD port 137 being dropped
in the pfirewall.log file, so I opened this port, and I still receive the
following error in Servers Alive. ERR: Unable to connect to
host.(7) What
port(s) need to be open in order to perform the eventlog
check? Thanks, Bill |
- [SA-list] eventlog check w/ firewall enabled. Bill Sweetman
- RE: [SA-list] eventlog check w/ firewall enabled. Dirk Bulinckx
- RE: [SA-list] eventlog check w/ firewall enabled. Bill Sweetman
- RE: [SA-list] eventlog check w/ firewall enable... Dirk Bulinckx
