Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 3 subscribers
  • Views 1707 views
  • Users 0 members are here
Options
Suggested
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

Endpoint not showing in SEC

Paul Rivenet

Hello,

 

I'm trying to setup a SEC with a Relay Server.

The Relay Server is accessible throught a domain name.

The problem is, when I install an Endpoint (MRinit.conf pointing at the domain name), the Endpoint doesn't show up in the console.

At some point, and I don't really know why, it showed up, but is now unavailable.

Can't someone please help me setting this up ?

I think I have troubles understanding the proper configuration to make this works.

 

Thanks for your help.



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to Paul Rivenet

    Hello Paul Rivenet,

    so what are the Parent addresses in the Network Communications Report of the endpoint (an FQDN that resolves to the relay's public or NATted IP, if I understand correctly) and the relay (if you sanitize them please use unambiguous placeholders)? Guess the Actual parent address is blank for the endpoint and on the relay SEC's name or IP?

    Does the relay return the FQDN in the IOR string or perhaps its internal IP?

    Christian

Children
  • 0 in reply to QC

    The ReportData.xml for the endpoint show this :

    <SSLIOP_port>8194</SSLIOP_port>
    <parent_addresses>
    antivirus.XX.fr
    </parent_addresses>
    <actual_parent>
    antivirus.XX.fr
    </actual_parent>
    <router_type>
    endpoint
    </router_type>

     

    The ReportData.xml for the Relay :

    <SSLIOP_port>8194</SSLIOP_port>
    <parent_addresses>
    192.168.20.45
    </parent_addresses>
    <actual_parent>

    <string msg='not available' />
    </actual_parent>
    <router_type>
    endpoint
    </router_type>

     

    On the Relay, the IOR is the FQDN

     

    Thanks

  • 0 in reply to Paul Rivenet

    Hello Paul,

    the endpoint could contact the relay but the relay thinks it's an endpoint (which would not prevent it from forwarding messages though) and - that's the issue -  it could not contact SEC.

    Christian

Unfiltered HTML