Skip to Content
avatar image
Former Member

RFC fail to connect to CI from DI

Hi All,

During sm59 RFC test from the DIs to the CI, it failed. In t-code smgw, all entries which are connecting to the CI are stated as "connecting" instead of connected. When drill in to the entry, it stated that the connection is pointing to 192.168.0.1.

How come the IP address is connecting to LOCL ? Our service file, host file are all stating the correct IP. The connection is working fine all the while , only recently we discover this weird problem. Does anyone has any idea ?

Regard

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Feb 08, 2007 at 02:26 PM

    Dear Lauran,

    it is hard to tell what is really going on there. Sometimes there is a problem if the connection between two gateways gets into an inconsistent state. You can run transaction SMGW, the Goto, Remote Gatewas and delete the connection to the CI. If this does not help, you will have to check the entry in SM59 carefully (especially if there are gateway options set).

    Best Regards,

    Tim

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 08, 2007 at 04:27 PM

    Hello Lauren,

    First of all please ask your network team to check the entries in host files on both CI and DI.

    Next thing please check if you are able to do logon through SM51.

    Please let us know updates from your side.

    Regards.

    Ruchit.

    Add comment
    10|10000 characters needed characters exceeded