A.1 Port number list
This section describes the port numbers used by JP1/IT Desktop Management 2.
JP1/IT Desktop Management 2 - Manager port number list
- Management server
-
Port number for management server
Connection direction
Connected to [port number]
Protocol
Use
31080
Administrator's computer [ephemeral]
TCP
Used for communication from an administrator's computer to a management server when the operation window is referenced or used.
This port number is also used for communication from Remote Installation Manager or Packager installed on the administrator's computer to a management server.
31000
Agent or relay system [ephemeral]
TCP
Used for communication from an agent or relay system to a management server
Ephemeral
agent or relay system [31001]
TCP
Used for communication from a management server to an agent or relay system during distribution using Remote Installation Manager
31006 to 31009, 31011, 31012
None
None
TCP
Used for JP1/IT Desktop Management 2 internal processing
31010
-
Remote Installation Manager [ephemeral]
-
Asset Console (jamTakeITDM2Info.exe) [ephemeral]
TCP
Used for communication from Remote Installation Manager or Asset Console to a management server, or internal processing
Ephemeral
Agent or relay system [31014]
TCP
Used for communication from a management server to an agent or relay system to distribute jobs by multicasting
31015
Agent or relay system [ephemeral]
TCP
Used for communication from an agent or relay system to a management server for requesting retransmission during multicast distribution
31021
-
Remote Installation Manager [ephemeral]
-
Agent [ephemeral]
-
Relay system [ephemeral]
-
Packager [ephemeral]
TCP
Used for communication from Remote Installation Manager, agent, relay system, and Packager to a management server during distribution using Remote Installation Manager
Ephemeral
Agent [16992]
TCP
Used for controlling the power source of a computer that uses AMT
Each port number is set as a default when the product is provided. If the port numbers shown in the table are already used in the system environment you are using, in the setup, change them to port numbers that are not used.
If a management server controls port numbers by using Windows Firewall, specify firewall settings to enable the above ports. Note that if you install JP1/IT Desktop Management 2 - Manager in an environment in which Windows Firewall is enabled, the ports are automatically set to pass through Windows Firewall (they are registered in the exception settings).
-
- Administrator's computer (Remote Installation Manager )
-
Port number for administrator's computer
Connection direction
Connected to [port number]
Protocol
Use
Ephemeral
Management server [31010 and 31021]
TCP
Used for communication from Remote Installation Manager to a management server during distribution using Remote Installation Manager
Ephemeral#
Management server [ephemeral#]
TCP
Used for Remote Installation Manager internal processing
#: The following describes how to fix the port numbers used for connecting the database to the agent.
- To fix the port number of the management server (connection destination):
-
-
Execute the stopservice command to stop the services on the management server.
-
Use a text editor to open the pdsys file stored in JP1/IT Desktop Management 2 - Manager-installation-folder\mgr\db\CONF.
-
Add set pd_service_port = port-number. For port-number, specify the port number you want to use.
Example: To specify 10000 as the port number, enter as follows:
set pd_service_port = 10000
-
Execute the startservice command to restart the services on the management server.
-
- To fix the port numbers of Remote Installation Manager (connection destination):
-
For receiving ports, the OS automatically assigns port numbers by default. Ten or more receiving ports are used.
-
Stop Remote Installation Manager and other applications for JP1/IT Desktop Management 2.
-
Use a text editor to open the HiRDB.ini file stored in Remote-Install-Manager-installation-folder\mgr\dbclt.
If Remote Install Manager and the management server are installed in the same computer, HiRDB.ini is stored in JP1/IT Desktop Management 2-Manager-installation-folder\mgr\db\CONF\emb.
-
For PDCLTRCVPORT=, specify the range of port numbers you want to use in the port-number-port-number format. Note that the range of port numbers is not set if you do not specify anything or specify 0 after PDCLTRCVPORT=, By default, the range of port numbers is not set.
Example: To specify 10000-10500 as the range of port numbers, enter as follows:
PDCLTRCVPORT=10000-10500
-
Start Remote Installation Manager and other applications for JP1/IT Desktop Management 2.
-
Each port number is set as a default when the product is provided. If the port numbers shown in the table are already used in the system environment you are using, in the setup, change them to unused port numbers.
If the administrator's server controls port numbers by using Windows Firewall, specify firewall settings to enable the above ports. Note that if you install Remote Install Manager in an environment in which Windows Firewall is enabled, the ports are automatically set to pass through Windows Firewall (they are registered in the exception settings).
Port number list for a relay system
Port number for relay system |
Connection direction |
Connected to [port number] |
Protocol |
Use |
---|---|---|---|---|
31001 |
Management server [ephemeral] |
TCP |
Used for communication from a management server to a relay system during distribution using Remote Installation Manager |
|
31002 |
Agent [ephemeral] |
TCP |
Used for communication from an agent to a relay system during distribution using Remote Installation Manager |
|
31014 |
Management server [ephemeral] |
TCP |
Used for communication from a management server to a relay system to distribute jobs by multicasting |
|
31015 |
Agent [ephemeral] |
TCP |
Used for communication from an agent to a relay system for requesting retransmission during multicast distribution |
|
Ephemeral |
Management server [31021] |
TCP |
Used for communication from a relay system to a management server during distribution using Remote Installation Manager |
|
Ephemeral |
Agent [16992] |
TCP |
Used for controlling the power source of a computer that uses AMT |
Port number list for a controller and remote control agent
Controller or remote control agent [port number] |
Connection direction |
Connected server [port number] |
Protocol |
Use |
---|---|---|---|---|
Remote control agent [31016] |
Controller [ephemeral] |
TCP |
Used for window operation from a controller to a remote control agent |
|
Remote control agent [31017] |
Controller [ephemeral] |
TCP |
Used for transferring files from a controller to a remote control agent |
|
Remote control agent or controller [31018] (when used as a chat server) |
Remote control agent or controller [ephemeral] |
TCP |
Used for chat |
|
Remote control agent [ephemeral] |
Controller [31019] |
TCP |
Used for requesting a remote connection from a remote control agent to a controller |
|
Remote control agent [ephemeral] |
Controller [31020] |
TCP |
Used for callback file transfer from a remote control agent to a controller |
If a computer with a controller installed or a computer that is remotely controlled controls port numbers by using Windows Firewall, specify firewall settings to enable the above ports. Note that if a controller and remote control agent are installed in an environment in which Windows Firewall is enabled, the ports are automatically set to pass through Windows Firewall (they are registered in the exception settings).
Each port number is set as a default when the product is provided. If the port numbers shown in the table are already used in the system environment you are using, follow the steps below to change them to port numbers that are not used.
-
Port number for a controller
Specify port numbers in the Options dialog box of the controller.
-
Port number for a remote controller agent
Specify port numbers in the Remote control settings view used for agent configuration.
-
Port number for the chat functionality
In the Chat window, select Options, and in the displayed dialog box, in the Connect tab, specify the port numbers.
JP1/IT Desktop Management 2 - Agent port number list
Agent port number |
Connection direction |
Connected server [port number] |
Protocol |
Use |
---|---|---|---|---|
31001 |
Management server [ephemeral] |
TCP |
Used for communication from a management server to the agent |
|
16992 |
Management server [ephemeral] |
TCP |
Used for controlling the power source of a computer that uses AMT |
|
Ephemeral |
Relay system [31002] |
TCP |
Used for communication from an agent to a relay system during distribution using Remote Installation Manager |
|
31014 |
Management server or relay system [ephemeral] |
TCP |
Used for communication from a management server or relay system to an agent to distribute jobs by multicasting |
|
Ephemeral |
Management server or relay system [31015] |
TCP |
Used for communication from an agent to a management server or relay system for requesting retransmission during multicast distribution |
|
Ephemeral |
Management server [31021] |
TCP |
Used for communication from an agent to a management server system during distribution using Remote Installation Manager |
Each port number is set as a default when the product is provided. If the port numbers shown in the table are already used in the system environment you are using, when setting up a management server, change them to port numbers that are not used.
If a computer with an agent installed controls port numbers by using Windows Firewall, specify firewall settings to enable the above ports. Note that if an agent is installed in an environment in which Windows Firewall is enabled, the ports are automatically set to pass through Windows Firewall (they are registered in the exception settings).
If networks between JP1/IT Desktop Management 2 - Manager and JP1/IT Desktop Management 2 - Agent control ports by using Windows Firewall, specify firewall settings to enable the ports in the above table.
Port numbers for agentless devices
For agentless devices, the port numbers for Windows administrative shares or SNMP are used depending on the authentication status of the devices.