Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Sessl on Nov 4 at 12:10 PM Hello,
I'm sorry, I don't found an option to delete the duplicate post!
| | | ---------------Original Message---------------
From: Tobias P.
Sent: Tuesday, November 04, 2014 9:14 AM
Subject: RFC Connection - Partner Not Reached Via JCO 3.0
Hello,
Our customer is using a RFC tool, to upload files, start transactions, etc., now they get an update of this tool (from JCO 2.x to JCO 3.0) and we have some network problems.
The main reason of this error is because the SAP systems sends his internal IP address back to the RFC tool, and the tool want to connect to the dispatcher with the given internal IP address.
We tested it with the SAPRouter and without, the problem is the same.
1. The tool (client e.g. 10.10.20.1) connects to the SAP Gateway (e.g. 210.10.10.1) with the given external IP address, and/or with a SAPRouter string.
- this connection works
2. The tool want to start a transaction, so it calls the function "SYSTEM_PREPARE_ATTACH_GUI", SAP sends the internal IP address (e.g. 192.168.1.1) to the client and I get the SAPGUI security prompt to allow to start a SAPGUI, after that, the tool wants to connect to the dispatcher with the internal IP address of the SAP system, but this fails .. I know that this is right ..
I read also a few notes:
• 21151 - Multiple Network adapters in SAP Servers
• 148832 - IP address conversion with a firewall
• 555162 - Asynchronous RFCs with a dialog using a SAP router
• 1033987 - Remote login using NAT or SAP router fails
I set the parameter "gw/alternative_hostnames" with the external ip address.
In the "dev_rd" file I can see:
GwPrintMyHostAddr: my host addresses are :
1 : [210.10.10.1] hostname.domain.de (HOSTNAME)
2 : [127.0.0.1] hostname.domain.de (LOCALHOST)
3 : [192.168.1.1] hostname.domain.de (NILIST)
Full qualified hostname = hostname.domain.de
The connection:
SAP (internal e.g. 192.168.1.1.) > FW (external e.g. 210.10.10.1) > VPN > FW (e.g. 220.10.10.1) > SAPRouter (e.g. 10.10.10.1) > Client (e.g. 10.10.20.1)
The simplest way would be, if the gateway sends back the FQDN instead of the internal, but I don't know how and I still found no solution to this problem.
Thank you for any help!
Best regards,
Tobias |
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
