Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. NetXMS list of default ports

NetXMS list of default ports

Scheduled Pinned Locked Moved Support
6 Posts 3 Posters 54.0k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R
    R
    ricktendo
    wrote on last edited by
    #1

    Is there a list of default ports/protocols used by and broken down by the different NetXMS packages?

    I want to set up NetXMS on AWS and want to create a Security Group that is more secure than All Traffic>All Protocol>All Ports>0.0.0.0/0

    Thank you

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi,

      tcp/4700: server -> agent
      tcp/4701: client (gui or integration tools) -> server
      tcp/4747: mobile agent -> server

      Best regards,
      Victor

      1 Reply Last reply
      0
      • F
        F
        fINT
        wrote on last edited by
        #3

        Good day.
        Is it possible to change tcp/4700: server -> agent port?
        If possible, how?
        Didn't find any parameters in Configuration - Server configuration in Web Console. NetXMS version 2.2.12

        1 Reply Last reply
        0
        • V
          V
          Victor Kirhenshtein
          wrote on last edited by
          #4

          Hi,

          you can only change it individually for each node. On agent side you have to add

          ListenPort = nnn

          to nxagentd.conf and on server side you should enter same port number in node properties Communication / Agent.

          Best regards,
          Victor

          1 Reply Last reply
          0
          • F
            F
            fINT
            wrote on last edited by
            #5

            Ok, but how "server understand" what port to scan, during Active Network Discovery process?

            1 Reply Last reply
            0
            • V
              V
              Victor Kirhenshtein
              wrote on last edited by
              #6

              No, server only tries to connect to port 4700 during discovery. I've registered feature request for providing list of custom agent ports for discovery: https://track.radensolutions.com/issue/NX-1560

              Best regards,
              Victor

              1 Reply Last reply
              0

              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

              With your input, this post could be even better 💗

              Register Login
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              Powered by NodeBB Contributors
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Users
              • Groups