Trusted RFC and Remote logon not possible due to Nat'd IP addresses

[Former Member]

Hi,

We are trying to connect our SolMan 4 to our cusotmers ECC 6 and BI7 systems, the systems are off site and the IP addresses for the customers systems are nat'd when they come in and go out from our Network.

The problem we get is that we cannot set up Trusted systems or Remote Logon to these systems due to issues with the Nating of the IP adresses. We can set up all standard RFC's after adding the the appropriate addresses into the hosts file and they work fine. But the trusted RFC does not set up properly and the BACK rfc from the satelite system does not get set up properly. What appears to happen is that when you try to start a remote session SAP goes to the satelite system and finds the Instance Name and the local IP address rather than the NAT'd IP address and try's to open a session from there. I found this by going into the trusted RFC in SM59 and then going to Extra's, System Information, Target System, this then tells me the Target System information, where it shows the System ID and IP address (which is the incorrect IP address).

Anyone know how we can get the system to try to have the correct IP adress in the target system information so that we can get Remote Logon's to work??

Cheers

[Paul_Babier]

Hello Carl,

Why don't you open an SAP support message under the component xx-ser-net-htl?

This group will be able to 1) Tell you if NAT to RFC is possible, and if it is, they can assist you in the configuration.

Hope this was helpful.

Regards,

Paul

[Former Member]

Hello,

as a dirty workaround, you could add in host file of the target host :

source_ip target_ip

As the source ip should be the private IP forwarded by the RFC connection (activate trace export in source system and check

trace in the target gateway thru smgw...)

That's why it is not working.

Regards

[Former Member]

I have the same problem, if this was solved can someone post the solution.

[Former Member]

Are the systems on the same domain? If not, do the domains trust each other?

What is Nating?

[Former Member]

They are on 2 different domains, but I'm not sure about the trust relationship netwen the domains.

The Nating is Network Address Translation, and allows traffic to travel between two networks through a router. The satellite system has 2 IP addresses. An internal IP for where the system is installed e.g. 192.168.1.1, and a translated IP that we have to use to connect to it across the networks e.g. 172.168.50.50. The Solution Manager has the same confiuration but in reverse. So when we try to instigate a remote session the session goes from 192.168.1.1 to the 172.168.50.50 address and then tries to come back, it interegates the Satellite system to find the instance names and links that to the IP address, only problem is it picks up the un-nat'd or local IP address and then try's to open a remote session on the local address rather than across the network on the nat'd IP address. Does that make sense???

Thanks

Carl

[Former Member]

Hi Carl,

Based on your explanation about Nating,, how will the RFC determine to connect to Solmans internal IP after it has been directed to the IP for the Router connection.

I feel it is like configuring a jump of RFCs from one IP to another in a single chain.

Can this be done ?? I mean we have to specify an IP in the RFC connection right.. so how will the automatic jumping of IPs be done.

Sorry not answering the question but its very interesting and wanted to know.

Also went trough note # 148832, might help.

Regards,

Kaustubh.

Edited by: Kaustubh Krishna on Aug 13, 2009 12:17 PM

[Former Member]

This probably doesn't answer your question, but do they have a SAProuter system that you can go through?

Just wondering.

J. Haynes

[Former Member]

No a SAProuter has not been used. The problem is that the system has 2 different IP addresses and when the rfc comes back to us it is trying to use the internal only IP address rather than the one that can get across the 2 networks.

Thanks

Carl.