Access cloud with client tools

[Former Member]

We have setup an BI 4.0 in cloud, opened ports from 6400 to 6500. Now when we try to access it with client tools, it gives 'Transport error: communication failure".

So modified the services to use the ports instead of auto assign and its the same, also updated the host file but no luck.

[repo_proxy 13] SessionFacade::openSessionLogon with user info has failed(Transport error: Communication failure.(FWM 00001)

(hr=#0x80042a01)

Any one has faced this issue?, please help.

[Former Member · Accepted solution]

Hi Kal,

You state that the system is in cloud and also that you updated the hosts file.

Could you clarify:

- are you accessing the system through FQDN (DNS), hostname or IP from the client?

- is there a NAT in front of the system?

- did you update the hosts file from the client or the server?

- the requestport have been assigned, did you also assign a hostname value?

- could you give us a quick summary of the ports setup for CMS (there should be two for that service), FRS Input and Output, as MDAS and APS?

Regards

[Former Member · Accepted solution]

I am accessing the system with hostname.

Yes, we do have a NAT in front of the system.

I changed the Request port and hostname value for CMS and now I am able to connect to the server with the client tools.

But when I try to import a universe then it is giving "File Repository Server Input is down".

So I changed the host file on both client and server but no luck.

CMS Port: 6400, 6401

Input FRS: 6404

Output FRS: 6405

APS: 6406

Thanks,

[Former Member · Accepted solution]

Beware that with a NAT involved in the front end, you cannot use IP configuration in the CMS and other services properties as it has been suggested. That leaves you with Hostname or FQDN configuration.

In the background, this is due to a double TCP/IP transaction of the CMS which picks whatever is set for the Hostname (see below) and send it to the client.

In a NATed env and setting an IP in the server, either the client would receive the wrong IP (internal one), or the CMS would not be able to bind to the IP (if configured with external IP).

Whatever your choice:

- the client need to resolve the hostname or FQDN as the external IP of your NAT

- the server need to resolve the hostname or FQDN as the internal one.

This being said, try and set the "hostname" value in the CMS, IFRS, OFRS and APS properties in the CMC > Servers

Hope this helps

[Former Member · Accepted solution]

Thanks Romain, that worked.

[Former Member]

Hi Kal

I had the same error, just add the ip and name servers in the cloud to the host file,and fix the problem.

Regards