This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

QC ARS Synch PROD to LAB behind FW

Hi,

 

I need to synch AD information (Users) between PROD domain and LAB domain using QC and ARS as I have Extended Attributes to synch. I have specified a static port for the "Aelita Enterprise Administration Service" and have added TCP port 135 and the new static port to the FW. I am able to create a QC Connection if I specify the connection to "Administration Service on specified computer" but if I use "Any Administration Service of the same configuration" it fails.

 

Using the first option doesn't show me any of the OUs in the scope settings.

 

I found an older post asking the same question but the wiki page the answer points to is no longer available.

 

ARS version is 6.9 and QC is 5.4

 

Are there any additional ports I need to get opened?

 

Thanks,

Justin

Parents
  • To your point:
    "I am able to create a QC Connection if I specify the connection to "Administration Service on specified computer" but if I use "Any Administration Service of the same configuration" it fails."

    The "Any..." option relies on service connection points (SCP) published by the ARS services at startup. These are normally published in the System container of the domain where the ARS services reside.

    If QC does not reside in the same domain then it will not be able to see the ARS SCPs. If you really want to use this option, you could try to publish "replicas" of the SCPs in the System container of the domain where QC resides however ARS will not be able to update their state (for example, if a service gets shut down) so your "fault tolerance" won't really be valid.

Reply
  • To your point:
    "I am able to create a QC Connection if I specify the connection to "Administration Service on specified computer" but if I use "Any Administration Service of the same configuration" it fails."

    The "Any..." option relies on service connection points (SCP) published by the ARS services at startup. These are normally published in the System container of the domain where the ARS services reside.

    If QC does not reside in the same domain then it will not be able to see the ARS SCPs. If you really want to use this option, you could try to publish "replicas" of the SCPs in the System container of the domain where QC resides however ARS will not be able to update their state (for example, if a service gets shut down) so your "fault tolerance" won't really be valid.

Children
No Data