Ad Widget

Collapse

Monitoring if tcp 3389 is up

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Bdolnik
    Junior Member
    • Apr 2022
    • 7

    #16
    I have the same issue with the SQL port 1433.
    After intensive search I found the solution. By default Zabbix server blocks all the ports except some (22,80,433). To change the behavior in RH8 you need to grant it permission to the can_network by doing following:
    setsebool -P zabbix_can_network on
    Works like a charm after this !
    I also tried simple check on port 3389 (RDP) - works as well

    Comment

    • markuman
      Junior Member
      • Mar 2023
      • 5

      #17
      Code:
      <key>net.tcp.service[tcp,,3389]</key>​
      That works for me. However, I've noticed that the zabbix-server itself performs the check and not the zabbix agent 2 on the related windows host.

      Comment

      • cyber
        Senior Member
        Zabbix Certified SpecialistZabbix Certified Professional
        • Dec 2006
        • 4808

        #18
        Originally posted by markuman
        Code:
        <key>net.tcp.service[tcp,,3389]</key>​
        That works for me. However, I've noticed that the zabbix-server itself performs the check and not the zabbix agent 2 on the related windows host.
        It depends, what you have set as item type. "Simple check" or "Zabbix agent" . With simple check server/proxy will perform the check. This can sometimes be confusing, if same built-in key can be used differently.

        Comment

        • LenR
          Senior Member
          • Sep 2009
          • 1005

          #19
          Originally posted by cyber
          If simple check from server/proxy towards a host does not return anything, maybe you have some FW rules in place, which just do not allow you to connect to that port...
          net.tcp.service will always return 0 or 1. If it's not retuning anything, ensure that the polling config has had time to update. However, if it's 0 (not listening) it just means the Zabbix server can't connect, you're right, it could be blocked from Zabbix, but allowed elsewhere. Don't be lulled into a false sense of goodness :-)

          Comment

          • georgeMyName
            Junior Member
            • Oct 2020
            • 13

            #20
            Hi, I am in simmilar trouble. Change from Simple check to Zabbix agent helps for me. I am monitoring iis by agent.

            Comment

            • aletzonsantiago
              Junior Member
              • Jan 2025
              • 1

              #21
              Originally posted by cyber
              rdp is not in service list

              Closest you can do probably is specifying "tcp".
              net.tcp.service[tcp,,3389]
              Just in case you can specify IP there also. net.tcp.service[tcp,<insert your IP here>,3389]
              This works for me. Thanks!

              Comment

              Working...