Subsystems do not start. Socket Connect Error

Problem

The subsystems cannot be started. A socket connect error is issued.

Solution

It should be checked whether it is possible to connect to the HostServers from the outside.

Check HostServer

To do this, issue the following command on a PC with IBM Access Client installed

CODE

C:\>cwbping 10.206.2.1

The generated log contains information about connection problems

CODE

BM i Access für Windows
Version 7  Release 1  Stufe 0
Programm zum Überprüfen von Verbindungen (64-Bit)
(C) Copyright IBM Corporation and Others 1984, 2010. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
  restricted by GSA ADP Schedule Contract with IBM Corp.
Licensed Materials - Property of IBM    

You can cancel the CWBPING request with the CTRL-C or CTRL-UNTBR key combination 
I - Connection to system 10.206.2.1 is checked...
I - connection to server application Central Client has been established successfully
I - connection to server application network file was established successfully
I - connection to server application network printing was established successfully
I - connection to server application data access was established successfully
I - connection to server application data queues was successfully established
I - connection to server application remote command was established successfully
I - connection to server application security was established successfully
F - CWBCO1003 - sockets error, connect() function returned 10060
F - CWBCO1048 - firewall blocking or timeout while trying to connect to IBM i
F - CWBCO1008 - unable to connect to server application DDM, function returned 10060

 
I - connection to server application Telnet was successfully established
W - CWBCO1015 - connection to system 10.206.2.1 checked, but warnings present

Check local connection

Enter the following command in a QSH session

CODE

java -cp /QIBM/ProdData/OS400/jt400/lib/jt400.jar utilities.JPing localhost

The results of the test are displayed on the console

CODE

Verifying connections to system localhost...                                 
                                                                             
Successfully connected to server application:  as-file                       
Successfully connected to server application:  as-netprt                     
Successfully connected to server application:  as-rmtcmd                     
Successfully connected to server application:  as-dtaq                       
Successfully connected to server application:  as-database                   
Successfully connected to server application:  as-ddm                        
Successfully connected to server application:  as-central                    
Successfully connected to server application:  as-signon                     
Connection verified

Solution

The reason may be an incorrect configuration of the local or remote DNS server, which resolves "localhost" to an incorrect IP address. Additionally, the DNS server search order may be configured to *REMOTE instead of *LOCAL.

Problem

Solution

Check HostServer

Check local connection

Solution

Related articles