Port 139 Significance

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
vishal313
Posts: 50
Joined: Wed Dec 18, 2019 10:23 pm

Port 139 Significance

Post by vishal313 »

Hi All,

We are in process of monitoring Windows servers from Nagios XI using WMI. We have enabled the TCP ports 135, 445 on the remote nodes, but not 139. Will it impact the addition of Windows server in Nagios XI console. Need to know the significance of TCP port 139. Also, please share the information if any additional firewall ports need to be enabled for adding the Windows server in Nagios XI for monitoring.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Port 139 Significance

Post by scottwilkerson »

Port 139 is usually used for CIFS file shares, and as far as I am aware it is not required for Nagios monitoring

Here is our WMI setup guide (no reference to port 139)
https://assets.nagios.com/downloads/nag ... ios-XI.pdf
Former Nagios employee
Creator:
ahumandesign.com
enneagrams.com
vishal313
Posts: 50
Joined: Wed Dec 18, 2019 10:23 pm

Re: Port 139 Significance

Post by vishal313 »

Hi Scott,

Thank you for the information shared. We have followed the document in order to set the permissions and also the firewall ports but we still are getting a timeout issue when we are trying to fetch the value for cpu(checkcpu) and memory(checkmem) for Windows servers(2008 R2, 2012, 2016) via a command line.
How can we troubleshoot in this scenario. We have tried to telnet the server from Nagios server on 135, 445 and they are connecting.
We also tried to increase the timeout to 120 seconds, but still the output timesout.

Please help.

Regards
Vishal Dhote
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: Port 139 Significance

Post by tgriep »

Test to see if WMI is enabled on the windows system. Login to the Windows system.

Code: Select all

    Launch the wbemtest program.
    Click Connect...
    Change root\default to root\cimv2, then click Connect.
    Click Query...
    Enter Select * from Win32_Product, then click Apply.
This should return a list of products. If it does, then WMI is probably fine, and something is up with WMIC. If the above did not work, try the following at a Command Prompt:

Code: Select all

regsvr32 wbemdisp.dll
then run the wbemtest query again. It has to return something.


Another test is to run the following command from the Nagios server to query the Windows server for the same information as above.
Replace domain, username, <password> and <IP Address> with valid data.

Code: Select all

wmic -U <domain/username>%<password> //<IP Address> "Select * from Win32_ComputerSystem" -d
If should output debug information if it fails and post that here.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked