1760329 - SAP in NAT (Network Address Translation) environment

1. login via SAPgui with or without load distribution fails in NAT environment
    
2. RFC connection with or without load distribution fails in NAT environment
   For this scenario, it is possible to observe that the RFC Gateway tries to connect to the external NAT IP address whenever the issue is simulated.
   For example:
   
   

   [date and time]
   ***LOG Q0I=> NiPConnect2: [external NAT IP]:3300: connect (111: Connection refused) [/bas/785_REL/src/base/ni/nixxi.cpp 3506]
   *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 366/sock 48
   (SI_ECONN_REFUSE/111; I4; ST; [external NAT IP]:3300) [nixxi.cpp 3506]
   GwTraceHdlInfo: hdl 366

   HANDLE = 366
   TIME = [date and time]
   SOCKET = 48
   STAT = NI_CONN_WAIT
   TYPE = STREAM IPv4
   OUT = 0 messages 0 bytes
   IN = 0 messages 0 bytes
   LOCAL = [local address:port]
   REMOTE = -
   OPTIONS =
   type = CLIENT
   net_stat = CONNECT_TO_REM_GW_PENDING
   hostaddr = [external NAT IP]
   accpt_hostaddr = ::
   opcode = NORMAL_CLIENT
   conn opcode = REMOTE_GATEWAY
   conn vers = 2
   index = 1875
   data = 561edbeac790
   ext_info = 561edbedb960
   offset = 0
   rest_len = 64
   snc_forced = 0
   ssl = 0
   remote gateway infos:
   hostaddr = [external NAT IP]
   service = sapgw00
   tpname = sapdp00

3. remote logon between SAP systems fails in NAT environment

• ABAP Platform based system
• SAP NetWeaver based system

KBA , BC-NET , Obsolete - Formerly used for network tests , BC-MID-RFC , RFC , BC-CST-LG , Logon group based load balancing , BC-CCM-CNF-GRP , Workload Balancing and Group Management , BC-CST , Client/Server Technology , Problem