Service monitoring on Japanese Windows 2000

[narendran.neelamegam at wipro.com]

NSClient++ Version : Nsclient++ 2.x
Os : Windows 2000 Service Pack 4
Nagios Version : 2.5
Attachment : services.msc on the Windows 2000 (Japanese) server.

define service{
        use                             check-service-availability
        name                            ZENworks Asset Management -
Collection Client
        service_description             ZENworks Asset Management -
Collection Client
        host_name                        1,2,3
        check_command                   check_nrpe_service!'TSCensus
Collection Client'
        contact_groups                  D1,M1
}

The above service check always returns critical "service
stopped"(Service is running fine).

Whereas the same configuration on the Windows 2000 (English) systems
return OK.

Is it something to do with the locale? 

Should I be running a newer version of NSClient++ ( All are production
systems, Hence unable to test with new version)
I thought this is only required for perf counters)?

Thanks and regards,

Naren
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Service_j.GIF
Type: image/gif
Size: 39520 bytes
Desc: Service_j.GIF
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080818/e1a34f94/attachment.gif>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null