DSXchange

Hi -- I'm hoping I'm just overlooking something, but I'm unable to connect my Win clients to our new v11.3.1 instance running on AIX 7.1

Here's the error message I get when attempting to connect my 11.3.1.2 Win Admin client to the AIX server. (I have masked our server name with "<server name here>" in this post).

Failed to authenticate the current user against the selected Services Tier

Could not connect to server [<server name here>] on port [9080].[<server name here>]:[9080]is not reachable. Ensure that the server [<server name here>] can be resolved and that communication on port [9080] between this machine and the server is not blocked


For kicks, I tried connecting my v9.1.0 Admin client to this server, and received the following error -- presumably because the versions don't align, but it's interesting that it's not complaining about port 9080.

Error message:
Failed to authenticate the current user against the selected Services Tier

http://<server name here>:9080/RegistrationServlet/registration?com.ascential.acs.registration.ASBBindingType=EJB&TIMEOUT=-1

Exception type: javax/security/auth/login/LoginException
Exception message: http://<server name here>:9080/RegistrationServlet/registration?com.ascential.acs.registration.ASBBindingType=EJB&TIMEOUT=-1
Exception stack trace:
javax.security.auth.login.LoginException: http://<server name here>:9080/RegistrationServlet/registration?com.ascential.acs.registration.ASBBindingType=EJB&TIMEOUT=-1
at com.ascential.acs.security.auth.client.AuthenticationService.getLoginException(AuthenticationService.java:987)
at com.ascential.acs.security.auth.client.AuthenticationService.doLogin(AuthenticationService.java:355)
Caused by: com.ascential.acs.registration.client.RegistrationContextManagerException: Caught an unexpected exception.
at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:76)
at com.ascential.acs.security.auth.client.AuthenticationService.doLogin(AuthenticationService.java:349)
Caused by: com.ascential.acs.registration.client.RegistrationHelperException: Caught an unexpected exception.
at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties(RegistrationHelper.java:721)
at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties(RegistrationHelper.java:588)
at com.ascential.acs.registration.client.RegistrationHelper.getBindingConfigProperties(RegistrationHelper.java:567)
at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:173)
at com.ascential.acs.registration.client.RegistrationContextManager.setContext(RegistrationContextManager.java:73)
... 1 more
Caused by: java.io.FileNotFoundException: http://<server name here>:9080/RegistrationServlet/registration?com.ascential.acs.registration.ASBBindingType=EJB&TIMEOUT=-1
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1434)
at com.ascential.acs.registration.client.ConnectionHelper.connect(ConnectionHelper.java:163)
at com.ascential.acs.registration.client.RegistrationHelper.getBindingProperties(RegistrationHelper.java:677)

After doing some research online, and in these forums -- I have verified the following:

My hosts file entry: IP address, short server name, long server name
dsprc is running: netstat -a | grep dsprc
Tried telnet to the server, port 31538 -- no error message
Able to log in to the IIS Admin Console (https://<server name here>:9443/ibm/iis/launchpad/)
My C:\IBM\InformationServer11\ASBNode\eclipse\plugins\com.ibm.iis.client\registered-servers.xml file is empty, but as I understand it, that will get populated after the first successful login?

I am wondering though if my Win client version (11.3.1.2) is too high for the server version (11.3.1)?

Thanks in advance!

try 9445

Same result ... unfortunately ... we accepted (most) defaults during installation, v11 still defaults to port 9080?

Could not connect to server <server name here> on port [9445].<server name here>:[9445]is not reachable. Ensure that the server [<server name here>] can be resolved and that communication on port [9445] between this machine and the server is not blocked

I also forgot to mention earlier that I checked WAS and confirmed that port 9080 has been identified as WC_defaulthost (9043 as WC_adminhost_secure) ... these settings land here during the install process, I suspect?

Port Name Port
BOOTSTRAP_ADDRESS 2825
SOAP_CONNECTOR_ADDRESS 8881
ORB_LISTENER_ADDRESS 9105
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS 9401
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS 9403
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS 9402
WC_adminhost 9060
WC_defaulthost 9080
DCS_UNICAST_ADDRESS 9353
WC_adminhost_secure 9043
WC_defaulthost_secure 9443

v11 defaults to the secure port 9443. Have you tried specifying port 9443?

qt_ky ... now I'm embarrassed I didn't notice that earlier! Even when accessing the IIS Console via the Launch Pad, I didn't catch on that my URL containing :9080 was being changed to :9443 when I logged in. And of course, all of the links on that page are :9443.

https://www-01.ibm.com/support/knowledg ... -1&lang=en

You hit it right on the head though, I'm using :9443 when accessing the Admin client on my Windows machine, and all's well.

Thanks so much for helping me see what I was missing!

qt_ky ... now I'm embarrassed I didn't notice that earlier! Even when accessing the IIS Console via the Launch Pad, I didn't catch on that my URL containing :9080 was being changed to :9443 when I logged in. And of course, all of the links on that page are :9443.

https://www-01.ibm.com/support/knowledg ... -1&lang=en

You hit it right on the head though, I'm using :9443 when accessing the Admin client on my Windows machine, and all's well.

Thanks so much for helping me see what I was missing!

Great! Glad to help.

One of the changes for version 11 was the use of HTTPS for connections.