on 2007 Feb 08 11:47 AM
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
70 | |
10 | |
10 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.