Communication problem after reboot in Windows NT 4.0 SP6

[zed]

After restarting Windows, the service will be started, but it refuses connections from Nagios. In Task-Manager i can see the process nsclient++.exe but it uses only a small amount of memory (below 1M). With filelogger.dll and debug=1 enabled have got nothing in log. If i start the service again after restart it funtcions normally until next restart of computer. The problem happens at every restart on all of my NT comps. also it's reproducable.

Client Version: 0.3.6 RC7

Config: [modules] FileLogger.dll CheckSystem.dll CheckDisk.dll NSClientListener.dll NRPEListener.dll

[log] debug=1

[Settings] password=xxxxx use_file=1

[NSClient] allowed_hosts=xx.xx.xx.xx port=12489 socket_timeout=30

[NRPE] port=5666 command_timeout=60 allow_arguments=1 use_ssl=0 allowed_hosts=xx.xx.xx.xx script_dir=scripts\ performace_data 1

[Check System] CPUBufferSize=300s CheckResolution?=100

[NRPE Handlers] nrpe_CheckService=inject checkServiceState CheckAll? exclude=McAfeeFramework? exclude=McShield? exclude=wscsvc exclude=srservice

[NRPE Client Handlers] check_other=-H 192.168.0.1 -p 5666 -c remote_command -a arguments

[zed]

As a workaround for this problem i have set a new REG_MULTI_SZ value called DependOnService? under HKLM/SYSTEM/Services/nsclientpp with the value LanManWorkStation?.

After rebooting the Nsclient++ service waits until the Workstation service is up with this extra setting.

[gjfrater]

We are experiencing this same problem with our Windows 2000 servers running 0.3.6.444 (RC6). It does not seem to be a problem for our Windows 2003 boxes.

[gjfrater]

Replying to gjfrater:

We are experiencing this same problem with our Windows 2000 servers running 0.3.6.444 (RC6). It does not seem to be a problem for our Windows 2003 boxes.