This plugin requires the linux implementation of wmic eg fro

[bosecorp]

that command does not exist

[cmerchant]

You need to install nmap on that machine.

Code: Select all

yum install nmap

[bosecorp]

PORT STATE SERVICE
22/tcp closed ssh
53/tcp open domain
80/tcp closed http
88/tcp open kerberos-sec
135/tcp open msrpc
161/tcp closed snmp
443/tcp closed https

[jdalrymple]

I've noticed your debugging errors are similar to those some other folks have gotten when they had special characters in their passwords.

It doesn't follow that could be the problem since it works from one host - but nonetheless a lot about this problem doesn't make sense so it's worth asking, are there any special characters in your password? Are you using the same credentials when testing from both the job and the worker server?

[bosecorp]

it does not have special characters and yes, I am using the same username and password

[cmerchant]

per tgriep:

From your worker server and the Nagios XI server, try running the following to see if they can access the ports on the Domain Controller.
Post the output from both systems.

Code: Select all
nmap <IPoftheDomainController>

Can you log on as root from your "JOB server" aka Nagios XI server, enter the following command, and provide us with an unedited copy of the output (including cmd prompt):

Code: Select all

nmap <IPoftheDomainController> 

Can you log on as root from your "worker server" aka gearman, enter the following command, and provide us with an unedited copy of the output (including cmd prompt). That would be most helpful in allowing us to help you determine what the problem might be. Thanks.

Code: Select all

nmap <IPoftheDomainController> 

[bosecorp]

I checked my firewall and nothing seems to be being blocked


PORT STATE SERVICE
42/tcp open nameserver
53/tcp open domain
88/tcp open kerberos-sec
111/tcp open rpcbind
135/tcp open msrpc
139/tcp open netbios-ssn
389/tcp open ldap
427/tcp open svrloc
445/tcp open microsoft-ds
464/tcp open kpasswd5
593/tcp open http-rpc-epmap
636/tcp open ldapssl
1801/tcp open msmq
2103/tcp open zephyr-clt
2105/tcp open eklogin
2107/tcp open msmq-mgmt
2701/tcp open sms-rcinfo
3268/tcp open globalcatLDAP
3269/tcp open globalcatLDAPssl
3389/tcp open ms-term-serv
5988/tcp open wbem-http
5989/tcp open wbem-https
7937/tcp open nsrexecd
7938/tcp open lgtomapper
8080/tcp open http-proxy
8192/tcp open sophos
8193/tcp open sophos
8194/tcp open sophos
49152/tcp open unknown
49153/tcp open unknown
49154/tcp open unknown
49158/tcp open unknown
49159/tcp open unknown
49160/tcp open unknown

[cmerchant]

You listed the output of only one server. Is this output from the job server or the worker? And how is that not the same as this:

PORT STATE SERVICE
22/tcp closed ssh
53/tcp open domain
80/tcp closed http
88/tcp open kerberos-sec
135/tcp open msrpc
161/tcp closed snmp
443/tcp closed https

[bosecorp]

the last one was the JOB server

[jdalrymple]

The only place we are concerned with connectivity is the worker server. Can you verify that the worker server has similar access to your LDAP/AD server?