Troubleshooting
Problem
This document provides information on which TCP/IP ports are required to have access when using IBM i Access Client Solutions.
Resolving The Problem
The following table lists the ports that IBM i Access and related functions use for communication with the IBM i OS System:
If any of the above ports are restricted by using a firewall or any other mechanism, IBM i Access or related functions might fail to operate. For assistance with configuring ports or working with a firewall beyond the above information, contact the firewall provider or obtain a consulting agreement.
PC Function
|
Server Name
|
Port Non-SSL | Port SSL | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If any of the above ports are restricted by using a firewall or any other mechanism, IBM i Access or related functions might fail to operate. For assistance with configuring ports or working with a firewall beyond the above information, contact the firewall provider or obtain a consulting agreement.
Note:
The following ports are common to most IBM i Access Client products such as ODBC, Telnet, and other specific functions:
Port 449 is used to look up service by name and return the port number.
Ports 8470 and 9470(TLS/SSL) are used for host code page translation tables and licensing functions.
Ports 8475 and 9475(TLS/SSL) are used to check for application administration restrictions.
Ports 8476 and 9476(TLS/SSL) are used for checking signon verification to authenticate.
depending on your needs you may only need the above ports and the port(s) for your function/application.
For the ports used by the Console, see document N1015344, IBM iSeries Port Assignments with Operations Console.
For the ports used by the Console, see document N1015344, IBM iSeries Port Assignments with Operations Console.
For a list of currently listening IPv4 daemons on the IBM i, run the following SQL statement:
SELECT LOCAL_PORT, LOCAL_PORT_NAME, BIND_USER, IDLE_TIME
FROM QSYS2.NETSTAT_INFO
where LOCAL_ADDRESS = '0.0.0.0';
Other options are the CL command NETSTAT OPTION(*CNN) or to review the output from WRKSRVTBLE OUTPUT(*PRINT).
Related Information
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CMAAA2","label":"Communications-\u003ETCP"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Historical Number
13642023
Was this topic helpful?
Document Information
Modified date:
04 December 2023
UID
nas8N1019667