SAP Knowledge Base Article - Preview

2815876 - DNS Caching leads to SAP Cloud Connector connection issues


Connection from SAP Cloud Connector(SCC) to SAP BTP Cloud Platform fails, upon checking SCC trace (ljs_Trace.log) it's perceived an IP address change according to below: send message of type 4 with size 4,680 over tunnel channel [id: 0x6149ab89, L:/ -]. Tunnel id: "account:///..."| #Unable to handshake with notification server$AnnotatedConnectException: Connection timed out:



SAP Cloud Connector(SCC) older than 2.12.


SAP BTP, Neo environment 1.0 ; SAP Connectivity service 2.0


Production, ABAP R/3, ERP, SRM, CRM, ERP, PPM, SEM, APO, XI, PI, PORTAL, Test, development, QA, KBA, On Premise, HANA Database, SAP Cloud Platform, Cloud Connector, xsodata, On-Premise, Access, large, datasets, AlwaysCompressed, DNS, IP, IP Addresses, IP address, hostname, host, change, deviate, new ip, proxy, SCC, BTP , KBA , BC-MID-SCC , SAP Cloud Connector On-Demand/On-Premise Connectivity , BC-NEO-CON , Neo to On-premise Connectivity service , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.