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

RMS client not reporting.

We have remote sites (10.0.0.0)  that cannot report back to the server (192.168.0.0.). The server has a NAT'd address to the 10.0.0.0 network via a firewall and WAN connection. Through the Enterprise Console the client deploys and it collects updates via a UNC path. However the Console remains ignorant of the client status  apparently due to the RMS not being able to talk back. I've found a few articles on setting up DMZ message relays however that isn't our setup and would be difficult to implement. I've tried amending the mrinit.conf to use the 10. address with no success.

Is there anyway to get the client to talk back via RMS or am I missing something?

:7839


This thread was automatically locked due to age.
Parents
  • The parent address in the report is correct, IOR port number is shown as 8192 and "Current parent address" is Not Available.

    Telnet to 10.x.x.x 8194 doesn't get a response, however telnet to 8192 gets some garbage back before disconnecting.

    Report generation time ( local time ) 12 January 2011 11:56:05
    Report generation time ( GMT ) 12 January 2011 11:56:05
    Computer name : mc 
    Windows domain : dddddd
    RMS router name : Not available 
    IOR port number : 8192
    SSLIOP port number : Not available 
    Parent addresses : 10.x.x.x,mc.ddddd.tld,mc
    Current parent address : Not available 
    RMS router type : endpoint 


    The Router logs show this:

    14.01.2011 07:11:48 02B8 E Failed to get certificate, retrying in 600 seconds
    14.01.2011 07:21:48 02B8 I Getting parent router IOR from 10.x.x.x:8192
    14.01.2011 07:21:48 02B8 I Getting a new router certificate...
    14.01.2011 07:22:34 02B8 E Router::GetCertificate: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO


    So something at least appears to be happening.

    :7875
Reply
  • The parent address in the report is correct, IOR port number is shown as 8192 and "Current parent address" is Not Available.

    Telnet to 10.x.x.x 8194 doesn't get a response, however telnet to 8192 gets some garbage back before disconnecting.

    Report generation time ( local time ) 12 January 2011 11:56:05
    Report generation time ( GMT ) 12 January 2011 11:56:05
    Computer name : mc 
    Windows domain : dddddd
    RMS router name : Not available 
    IOR port number : 8192
    SSLIOP port number : Not available 
    Parent addresses : 10.x.x.x,mc.ddddd.tld,mc
    Current parent address : Not available 
    RMS router type : endpoint 


    The Router logs show this:

    14.01.2011 07:11:48 02B8 E Failed to get certificate, retrying in 600 seconds
    14.01.2011 07:21:48 02B8 I Getting parent router IOR from 10.x.x.x:8192
    14.01.2011 07:21:48 02B8 I Getting a new router certificate...
    14.01.2011 07:22:34 02B8 E Router::GetCertificate: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
    OMG minor code (2), described as '*unknown description*', completed = NO


    So something at least appears to be happening.

    :7875
Children
No Data