This error is specificly for the case that Something is trying to access the NC_NEt port but not using the Check_nt protocol.
This other application can be anything either on the localhost or a remote host.
implementing Active_ip_accept_list may help in finding the source of the issue, or on a worst case tell you who the Source IP/Hostname of the non-complient connections.after turning on active_IP_Accept_list look for eventID: 4009 This assumes that the culprit is not on the localhost or on the Nagios Host.
naturally you could always implement a Packet sniffer or Network monitor to assist in locating the issue.
good Luck,
Tony
NC_NEt accepts Donations, visit www.montotech.com to make a donation via PayPal
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I am receiving several messages in the eventlog stating "Not Enough arguments". No other data is listed.
System is a Win2k3 32bit.
NC_Net Service Started :
Current Date: 12/5/2007 4:36:00 PM;
Version: NC_Net 4.1a 03/30/07;
Install Path: C:\windows\command\NC_Net\;
Command File Path: C:\windows\command\NC_Net\command\;
Script Path:C:\windows\command\NC_Net\script\;
PerfStat Config Path: C:\windows\command\NC_Net\config\;
Startup Config: C:\windows\command\NC_Net\config\startup.cfg;
Passive Config: C:\windows\command\NC_Net\config\passive.cfg;
Passive Check Log: C:\windows\command\NC_Net\config\passive.log;
IP_Accept_list: C:\windows\command\NC_Net\config\active_ip_accept_list.cfg;
Active_check: True;
Lock_active_config: False;
Port: 1248;
Active_ip_accept_list: False;
Verbose_logging: False;
Client_timeout: 20000;
Socket_timeout: 2000;
Passive_check: False;
Passive_alwayson:True;
Lock_passive_config: False;
Interval_passive: 5;
Interval_div_passive: 1;
Perfdata_format: 2;
Embedded_send_nsca: True;
Port_passive: 5667;
Host_passive: MANTIS;
Pass_passive: ;
Ip_passive: 127.0.0.1;
Encrip_passive: 1;
Passive_timeout:10;
External_send_nsca: False;
External_send_nsca_app: ;
External_send_nsca_ip: ;
External_send_nsca_port: 5667;
External_send_nsca_timeout: 10;
Cpu_single: False;
Cpu_max_interval: 60;
Cpu_times_per_min: 12;
Sampledelay: 15;
Evntlog_desc_trim: 100;
Regex_options: IgnoreCase, Multiline, IgnorePatternWhitespace;
Allow_run_scripts: True;
Script_timeout: 30;
Do_not_blaim_nc_net: False;
evntlog_input_trim: 1000;
trysleep: False;
error_value_on: True;
error_value_show_1: False;
Testrun: False;
Hostcheck: False;
HostcheckX: False;
Hostcheck_alwayson: True;
Hostcheck_port: 5667;
Hostcheck_portX: 5667;
Hostcheck_hostid: ****;
Hostcheck_hostidX: ****;
Hostcheck_pass: ;
Hostcheck_passX: ;
Hostcheck_ip: 127.0.0.1;
Hostcheck_ipX: 127.0.0.1;
Hostcheck_enc: 1;
Hostcheck_appX: ;
Hostcheck_timeout: 10;
Hostcheck_timeoutX: 10;
Hostcheck_interval: 5;
Hostcheck_interval_div: 1;
hi nate,
This error is specificly for the case that Something is trying to access the NC_NEt port but not using the Check_nt protocol.
This other application can be anything either on the localhost or a remote host.
implementing Active_ip_accept_list may help in finding the source of the issue, or on a worst case tell you who the Source IP/Hostname of the non-complient connections.after turning on active_IP_Accept_list look for eventID: 4009 This assumes that the culprit is not on the localhost or on the Nagios Host.
naturally you could always implement a Packet sniffer or Network monitor to assist in locating the issue.
good Luck,
Tony
NC_NEt accepts Donations, visit www.montotech.com to make a donation via PayPal