How do I access qlik tools link (console) outside of EC2 windows server?

[Robs56_]

I've been trying to access my enterprise manager and replicate console link from my local desktop, and it's not allowing me? 

[Heinvandenheuvel]

>>. trying to access my enterprise manager and replicate console link from my local desktop, and it's not allowing me? 

What error message?

What username is being used? Is that username allowed in at least as viewer, by its own name or  as member of an AD group? You may be able to check the <DATA>\LOGS\REPTSK.LOG file to see who is knocking!

On (replicate) Console got to [Server] and next  [User Permissions] to check.

note: When a replicate server is installed, the installers username is added as Admin and 4 AD groups with names like [DOMAIN]\AttunityReplicateAdmins  - was your username added?

Sometimes you need to tell your browser to 'run as different users' with shift-right-click. Select the installers username/pass ?

hth,

Hein

[Robs56_]

Hey thanks for your response, 

I m using the qlik replicate console in EC2 instance as admin, when I m trying to use the same link on my local desktop it's giving me an error this site can't be reached with DNS_PROBE_FINISHED_NXDOMAIN error.

Thank you.

[Heinvandenheuvel]

DNS_PROBE_FINISHED_NXDOMAIN indicates a generic Network configuration error  completely outside the control of Qlik Replicate/EM.  Be sure to escalate to you EC2 / network support team.

Can you even 'ping' the instance?

Hein

[mattdevdba · Accepted solution]

Check that the security group for the EC2 instance allows traffic from your source network to the required enterprise manager and replicate console ports.

[Robs56_]

Can you please guide me on what do you mean by "your source network to the required enterprise manager and replicate console ports" I have open ports HTTP 80 and HTTPS 443.

[mattdevdba]

First just to confirm the network setup.

The EC2 instance can be private or public facing. If it is public facing it should have an public IP address assigned to it. It would be in a public subnet. If it is private it won't be routable over the public internet but you may have a VPN or DirectConnect connection in place that allows your corporate network to communicate with the EC2 instance you are running in AWS. There are numerous ways the baseline connectivity between your local machine and the AWS account could be established. I'm assuming that all that kind of thing is in place at this point.

If you access the AWS console and select your EC2 instance and then select the security tab. It will list the security groups assigned to that instance. Once of those security groups will need to have inbound rules for the ports you are trying to access.

For example if your IP address is 192.168.1.10 the security group should have a source of at least 192.168.1.10/32 on the required ports.

[Robs56_]

Yes, it has the public IP address and security groups have HTTP and HTTPS ports 80 and 443 with source 0.0.0.0/0.

Now I m trying to connect an ec2 link which is https:///ec2-skiep62/attunityreplicate what inbound rule should I add to the security group? and with what type, portrange, etc. 

[mattdevdba]

That address does not resolve.

nslookup ec2-skiep62

Server: 192.168.1.1

Address: 192.168.1.1#53

** server can't find ec2-skiep62: NXDOMAIN

Try the public IP or the Public IPv4 DNS instead. In AWS it will be something like this.

 https:///ec2-12-34-56-78.us-west-2.compute.amazonaws.com/attunityreplicate or 

https://12.34.56.78/attunityreplicate 

[Robs56_]

Public IP = 

Check if there is a typo in ec2amaz-skpie62.

DNS_PROBE_FINISHED_NXDOMAIN

--------------------------------------

Public DNS =

This site can't be reached.

ec2-33-xxx-xxx-xx.us-west-2.compute.amazonaws.com took too long to respond.

Didn't work, Do I have to add any public-IP/32 port inbound rule? if yes with what type and protocol range?